On the other hand, lots of software is written for STM devices so spending a couple of bucks more for their parts will save you development costs and time.

If Xi has a bad day he could start a nuclear confrontation with no one able to reign him in.

But a balloon has to intrude in someone's airspace. Doing so could trip off an international incident, like it has now.

These intrusions are clearly a violation of our airspace and could even be considered an act of war.

What the hell was Xi thinking? Is he trying to communicate that China can do whatever it wants with impunity? Did he even authorize this flight or was this someone else's decision?

But the pilfering of Mozilla by its management (giving themselves million dollar bonuses and pretending they're managing a billion dollar corporation) and their illogical and fickle decisions has reduced IMHO the need for an independent open-source browser.

The only rationale for having a browser like Firefox now is to push back against megacorps like Google adding extensions to prop up their agenda (like preventing ad-blockers from working).

Mozilla had its day in the sun. I still use it but if it were to go away I wouldn't lose too much sleep over it.

You may be in the right, but I personally don't see no reason for it. Linux is the best supported operating system in the world and Google always has the option to alter the OS if need be.

I do believe Fuchsia is vastly more secure and stabler than Linux, which could be a benefit, but Google isn't exactly being pilfered by miscreants on a daily basis, so that benefit is in doubt.

IMHO Google shouldn't pull-back from using Java (or Kotlin). Rust could be an option but that would certainly degrade Android's developer experience.

Fuchsia's architecture is extremely resilient and secure by design and there's very little change culprits will be able to breach its security.

The company will soon have to decide how to move forward since replacing Linux will require a sizeable investment in manpower. My suggestion would be to focus on only replacing the Linux kernel whilst keeping other parts of the Android stack intact as much as feasible.

They should be able to do this in relatively short order, say two years.

Most likely his Bitcoin donations gave him away, since Bitcoin is far from anonymous. He might also have left other clues such as an email address which he accessed from clearnet.

Anyway, it's pretty obvious LEA cannot identify Tor users en-masse. There have been several CP websites taken down which had hundreds of thousands of users, yet they only managed to arrest the website administrators. Only a handful of users were arrested, and mostly because of dumb mistakes.

Some of my own Rust code is moderately complex but never showed any signs of instability during development. I often have crashes now and again with my C++ programs. Sure, I fix those afterwards but getting it flawless every time the first time is (for me at least) unheard of.

Programs with Rust will always be rock-stable, unlike many C/C++ programs which are more like a house-of-cards.

Most tools, even very technical tools like assemblers, debuggers and compilers, don't need deterministic memory management. Only operating systems, device drivers and some time-critical applications (like video/audio encoding/decoding) need deterministic memory management.

I completely disagree with this statement. If a Rust developer takes longer to code some feature this time will eventually be saved fixing memory bugs later on. And don't forget the immaterial cost of losing customer confidence if the product crashes or glitches because of memory instability.

And then I'm even glossing over the enormous benefit of Rust when writing correct multi-threaded code, which is almost always a minefield in C/C++. Code that looks and seems to work OK might in production suddenly crash after a year or so. A complete nightmare!

Memory safety is ALWAYS a good thing to have.