Sounds like you're cherry picking both; I've seen plenty of garbage that costs money as well.

Could be a variable from somewhere else in the code. It should throw type error of some sort if it's not going to handle a float correctly

JavaScript alone is not a simple beast. It needs to be optimized to deal with modern JavaScript web apps so it needs JIT, it also needs sandboxing, and all of the standard web APIs it has to implement. All of this also needs to be robust. Browsers ingest the majority of what people see on the Internet and they have to handle every single edge case gracefully. Robust software is actually incredibly difficult and good error handling often adds a lot more code complexity. Security in a browser is also not easy, you're parsing a bunch of different untrusted HTML, CSS, and JavaScript. You're also executing untrusted code.

Then there is the monster that is CSS and layout. I can't imagine being the people that have to write code dealing with that it'd drive me crazy.

Then there are all of the image formats, HTML5 canvases, videos, PDFs, etc. These all have to be parsed safely and displayed correctly as well.

There is also the entire HTTP spec that I didn't even think to bring up. Yikes is that a monster too, you have to support all versions. Then there is all of that networking state and TLS + PKI.

There is likely so much that I'm still leaving out, like how all of this will also be cross platform and sometimes even cross architecture.

An equal amount of wasted energy is output defending a trillion dollar corporation that doesn't care about those defending them at all. Apple be fine. Let's just use our computers and move on with our lives; it doesn't have to be personal.

There are definitely good, non malicious reasons to have it as a separate app and that should actually be preferred. Off the top of my head:

• Separation of permissions - it only has the permissions it asks for instead of every permission messages has
• It can be disabled/removed without disabling messages
• it can be reused by other applications if that's a desirable feature

Some people might actually like this: thinking of women getting unsolicited dick picks in particular

As someone who has worked outside of the US on an "immigrant visa", I was paid normal wages and treated like a normal employee. I also could quit and look for any job I wanted. I don't know anything about H1B, but substandard treatment definitely shouldn't be expected just because you're an immigrant.

No. https://kamalaharris.com/issues/ this is not too far right. People need to stop just listening to sound bites and talking points. All of the socialist voters think we're going to just randomly have a socialist state one presidential cycle? Come on. I don't buy it. The real fact here is that people who considered themselves unaffected by Trump couldn't get off their high horse and try to help. You know what drags us more right? Trump winning and Republicans owning Congress.

I'm so sick of this; that wasn't her platform. People constantly saying that was her platform stopped people from actually looking at her platform. I'm so sick of Dems that think they can just not vote because they don't fall in love with their candidate. Politics is practical and the USA just shit the bed and it will have a real impact on the world. All of the Dems or left leaning people who didn't vote are complicit.

This doesn't seem to be a Rust problem, but a modern development trend appearing in a Rust tool shipped with Cargo. The issue appears to be the way things are versioned and (reading between the lines maybe?) vendoring and/or lockfiles. Lockfiles exist in a lot of modern languages and package managers: Go has go.sum, Rust has Cargo which has Cargo.lock, Python has pip which gives a few different ways to pin versions, JavaScript has npm and yarn with lock files. I'm sure there are tons of others. I'm actually surprised this doesn't happen all the time with newer projects. Maybe it does actually and this instance just gains traction because people get to say "look Rust bad Debian doesn't like it".

This seems like a big issue if you want your code to be packaged by Debian, and it doesn't seem easy to resolve if you also want to use the modern packaging tools. I'm not actually sure how they resolve this? There are real benefits to pinning versions, but there are also real benefits to Debian's model (of controlling all the dependencies themselves, to some extent Debian is a lockfile implemented on the OS level). Seems like a tough problem and seems like it'll end up with a lot of newer tools just not being available in Debian (by that I mean just not packaged by Debian, they'll likely all run fine on Debian).

Async features in almost all popular languages are a single thread running an event loop (Go being an exception there I believe). Multi threading is still quite difficult to get right if the task isn't trivially parallelizable.

I hate getting into these discussions.

This is Arnaud Petit and Stéphanie Bodet, two professional climbers with far more experience than you. They are doing the second ascent of a 900 meter 8a on Angel Falls (Rainbow Jambaia, 31 pitches) which is about the same height as El Capitan in Yosemite National Park. Here is a story about it. You almost never plan to climb routes this long in a single day, especially not on the second ascent. They most definitely planned to sleep on the wall and brought the proper equipment. This is called big wall climbing

Just be happy for people doing what they love and do what you love: your life will be better. We're all motivated by different things.

They're just having fun