foooorsyth

2 ay öncediscuss

Biggest killer of JetBrains IDEs has been simple: the “Switcher” now orders navigation destinations dynamically, whereas they used to be static. Destination keymap is not customizable. Ruins all of my muscle memory and makes me hate the IDE now. Someone at JetBrains please read this and make the Switcher destinations something I can customize in the keymap

foooorsyth

3 ay öncediscuss

The opposite, actually. Signal endlessly nags you to turn on notifications, and when you turn them on, previews and content are shown by default. You cannot opt out of the nags.

foooorsyth

4 ay öncediscuss

>The actual meaning of a "clean room implementation" is that it is derived from an API and not from an implementation

This is incorrect and thinking this can get you sued

https://en.wikipedia.org/wiki/Structure,_sequence_and_organi...

foooorsyth

5 ay öncediscuss

I wouldn’t take too much issue with the “cameras are enough” claim if cameras actually performed like eyes. Human eyes have high dynamic range and continuous autofocus performance that no camera can match. They also have lids with eyelashes that can dynamically block light and assist with aperture adjustment.

The appeal to human biology and argument against fusion between disparate sensors kinda falls flat when you’re building a world model by fusing feeds from cameras all around the car. Humans don’t have 8 eyes in a 360 array around their head. What they do have is two eyes (super cameras) on ~180 degree swiveling and ~180 degree tilting gimbal. With mics attached that help sense other vehicles via road noise. And equilibrioception, vibration detection, and more all in the same system, all fused. If someone were actually building this system to drive the car, the argument based on “how did you drive here today?” gets a lot stronger. One time I had some water blocking my ear and I drove myself to the hospital to get it fixed. That was a shockingly scary drive — your hearing is doing a lot of sensing while driving that you don’t value until it’s gone.

foooorsyth

5 ay öncediscuss

The reality that most encryption enthusiasts need to accept is that true E2EE where keys don’t leave on-device HSMs leads to terrible UX — your messages are bound to individual devices. You’re forced to do local backups. If you lose your phone, your important messages are gone. Lay users don’t like this and don’t want this, generally.

Everything regarding encrypted messaging is downstream of the reality that it’s better for UX for the app developer to own the keys. Once developers have the keys, they’re going to be compelled by governments to provide them when warrants are issued. Force and violence, not mathematical proofs, are the ultimate authority.

It’s fun to get into the “conspiratorial” discussions, like where the P-256 curve constants came from or whether the HSMs have backdoors. Ultimately, none of that stuff matters. Users don’t want their messages to go poof when their phone breaks, and governments will compel you to change whatever bulletproof architecture you have to better serve their warrants.

foooorsyth

8 ay öncediscuss

Had so many Boston cabs not show up for rides to the airport growing up. Uber was such a breath of fresh air…until it wasn’t anymore.

foooorsyth

2 yıl öncediscuss

Ah I missed that this thing is actually embedded. I thought they were just doing multiple implementations for shits and gigs.

Carry on, Google

foooorsyth

2 yıl öncediscuss

I can appreciate the pain of actually getting things through in a large (100k+ people) organization.

What do you consider the be the justification for three separate implementations of the same build config language? Genuine question. I am not doubting the need for the DSL itself.

foooorsyth

2 yıl öncediscuss

>There are three implementations (Go, Rust, Java)

There are so many people at Google just goofing around, lol. People just doing hobby stuff for $350k/year.

There is no justification to implement this custom dialect of Python for a build system that drives everyone crazy 3 times. Reminds me of when it was revealed that 400 people were working on Fuschia — a hobby OS that only shipped on a single smart home device.

foooorsyth

3 yıl öncediscuss

>At that point, all Beeper becomes is a service to turn a green bubble blue.

This is a bigger deal than encryption itself to most people using Beeper. Beeper requires you to divulge your Apple ID password to Beeper anyways, so arguing for security is quite strange. People literally just want blue bubbles on their Android — that’s the main appeal.

foooorsyth

3 yıl öncediscuss

>Turing awards are all theorists game, not engineers

Robert Metcalfe just won the award for Ethernet. Go scan through the list of Turing winners again. It is not just awarded to pure theorists. There’s a huge slant to academics who also found (or caused) massive commercial success, especially in recent years.

Bellard could get hit by a bus tomorrow and have

>the most important video tool ever

>the most important emulation tool ever

>the best text compression tool ever

…on his resume. And with those tools he’s not just wrapping algorithms cooked up by others, but also innovating on fundamental theory. VirtualBox and the Android emulator? That’s QEMU. Every video platform in existence? Thin wrappers to FFmpeg. Seems deserving to me, and certainly seems as or more impactful that many names on that winners list.

foooorsyth

3 yıl öncediscuss

He is simply one of the most important programmers alive today. He should win a Turing award in his lifetime.

foooorsyth

3 yıl öncediscuss

Yawn. It's classic FSF attitude, and it's a perfect microcosm of GPLv3's goals of preventing things like locked-down hardware in the scope of a software license. In this case, the commenter I replied to thinks it wrong that users of OSM's data product, which has copyleft clauses in the scope of the data only, should be able to sell a closed-source application using that data. Which is of course not the will of the data product creators (the only people that have a real say in this), and is just annoying rms cult dogma cut and paste. For the record, Magic Earth is far and away the best OSM-based non-big-tech mapping product. It absolutely blows away GPLv3 products like OSMAnd. So yeah, it's annoying hearing people clamoring for its source to be opened, or soft-shaming the authors for trying to earn a real living with their great product that's perfectly inline with the data provider's license.

foooorsyth

3 yıl öncediscuss

I’m not anti-GPL. I’m anti-FSF-fanatics-applying-GPL-dogma-to-non-GPL-projects. OSM doesn’t use the GPL or a GPL-like license for their data.

foooorsyth

3 yıl öncediscuss

Terrible analogy. Returning the shopping cart is expected behavior of user as expressed by the grocery store. Expected user behavior as expressed by OSM is that you can use the data as you please, even for profit, and if you alter the data, you need to share that data back. That’s it. YOUR desired behavior for users of OSM’s data (open sourcing any app that uses it) really has no bearing. You aren’t the licensor and you have no say. Why do you feel as though you should get to impose your dogma on OSM’s data product?

foooorsyth

3 yıl öncediscuss

They’re not violating the OSM data license. Why would it “not sit well” with you that they keep their client closed source and try to earn a real living?

>you can have a paid product but open source the project

And you’ll instantly create 10 competitors overnight. If you use the GPL, those competitors will just be Chinese or from some non-western jurisdiction that doesn’t care about GPL enforcement.

Man, rms followers are annoying. Stop trying to GPL the entire internet. Magic Earth is a great tool. A big part of why it’s great is probably because its authors were motivated by profit.

comments