That's not what "Jobs" is about. It's the setting of a character-driven dramatization of Steve Job's life and his personality. You do not grow a company like Apple merely by dominating rooms with your personality, dropping oneliners and speaking in absolutes. There's a lot of actual work involved, the details of which would make for a movie rather boring to most audiences.

"Jobs" is a movie about Apple as much as "Inglourious Basterds" is a movie about the US military in WW2.

It just reflects the spoken language. And having the unused symbol then be the thousand separator is natural.

The Stasi had beds, some sense of privacy through proper doors, and an hour a day one might spend outside in a small courtyard to get some sunlight.

However the level of psychological torture (sleep deprivation, hours of standing/sitting in a prescribed posture, hourly checks, ...) appears to be milder in Japan. The Stasi could take that pretty far once they weren't allowed to use physical torture anymore.

That prevents trying to swap the module, but doesn't prevent swapping out the sensor on the module itself.

Also even if it doesn't get leaked directly, the security of TPM chips is not absolute. Secrets from them can theoretically be extracted given an attacker with sufficient means and motivation. Normally nothing that's on a typical TPM chip would warrant a project of that magnitude, but a widely used private key can change that equation.

Plus a TPM chip doesn't really have means to tell the phone isn't being lied to. You could swap out the actual phone camera hardware and sensors for a custom board that feeds the entire phone camera data of your choosing and it would be none-the-wiser.

That means for now it's useful.

"Oh shit!" indeed.

If they didn't have an LLM wipe their DB, they would've found another way. At least that's the feeling I got reading that.

Fully agree. From a US perspective, that sucks. For everyone else it's pretty great.

At this point the world's opinions of China are better than those of the US in some polls. One country invests and helps build infrastructure on a massive scale globally, the other alienates allies, causes countless conflicts, and openly threatens to end civilizations.

Indeed, even if one isn't partial to China, there's reasons to be glad that an increasingly hostile US has powerful competition.

> This is about who will dominate the world of tomorrow.

For this you'd need a technological moat. So far the forerunners have burned a lot of money with no moat in sight. Right now Europe is happy just contributing on research and doing the bare-minimum to maintain the know-how. Building a frontier model would be lobbing money into the incinerator for something that will be outdated tomorrow. European investors are too careful for that - and in this case seem to be right.

Libraries like Tokio (mentioned in the article) have support for this built-in. Goroutines sidestep the issue completely. C# Tasks are batteries included in that regard. In fact function colors aren't an issue in most languages that have async/await. JavaScript is the odd one out, mostly due to being single-threaded. Can't really be made to work in a clean way in existing JS engines.

Also the syntactic rules around control flow within elements/literals/identifiers seem a bit inconsistent. Some things require curly braces, others don't.

By the way you can probably implement this to 90% without needing a compilation step for React. Just track what elements get created by react factory functions during the function component execution (similar to how hooks work), and treat any that weren't passed as children to another as implicit returns. This only breaks when they're used verbatim in expressions, but this library doesn't allow doing that without a special wrapper tag either. A library approach should probably add a lint rule to disallow it.

The only thing you can't implement as a library is some of the syntactic sugar that allows one to directly put control flow within elements without wrapping the thing in an IIFE.

Overall a bit too much magic for my taste. The style stuff is nice, but I'd prefer a library approach for that in a react app as well.

Finally here's something with rather strange output:

    export component Test() {
      
{Date.now()}

      if (Math.random() > 0.5) {
          return;
      }

      
    }

    const Test__static1 = 
{Date.now()}
;

    export function Test() {
        if (Math.random() > 0.5) {
            return 
{Date.now()}
;
        }

        return Test__static1;
    }

    /* CSS */
    div.tsrx-vhi6ss {
        color: "red"
    }

I'm not sure how much of that is intended, and how much is a bug.

Framwork is usability and performance first, openness second. MNT is the other way around.

In fact all Kobo e-ink devices, except the Kobo Mini, wifi, and the original one, are still getting firmware updates.

Their android-based tablets with IPS screens are all discontinued though (as far as I am aware).

This is more than Amazon ever did. They haven't updated the firmware on some of their devices that are officially "supported" in years.

Also custom maps are mods by definitions anyways, with the exception of games where the creation of maps is a component of gameplay.

Yeah. Bored 15 year olds for laughs.

We had a great time putting the most ridiculous stuff out there.

Having a classmate who was actively buying into tons of conspiracy theories (9/11, cold sun, hollow earth, ...) was just the cherry on top and probably what got us into it in the first place.