Incorrect. Japan doesn't want immigration from any country. Japan has allowed a large number of Nepalese people to immigrate.

Homoglyphobie?

Two reasons imo
1. Avoid funny unicode characters, and Chinese, Japanese ...
2. /. code was written 25 years ago, in Perl (write-only language) and nobody has the smallest clue how to fix it

This "feature" actually saved me quite a bit of work at a job I had a few years back. The documentation people were so afraid that anyone who was not a full-time Word expert would irrecoverably screw up the corporate branding (IOW, formatting) of their docs, they didn't want developers to directly edit them. So I was often able to get away with emailing a quick text summary to them, and they had to do all the fidgety proof reading, formatting, etc.

I don't know how they managed to get their jobs done, given that they had no real source control and mainly juggled each update amongst themselves over email and random impoossible-to-find folders on Sharepoint.

Since all the docs had the same basic layout and they were mainly trying to make them look consistent with whatever corporate branding was being promulgated that week, it could easily have been done by writing them in "markdown" and having a script that converted them directly to PDF. Or maybe even learn LaTeX. Then the docs could all be maintained and diffed in github like all the other project artifacts. I didn't even bring that up because I knew that their heads would explode.

Fortunately, it doesn't appear to be a Pakistani terrorist act.

time.

but not when it comes to summaries. It's the kind of C vs Rust futile resistance...

Given the rough average volume of a human being, and the formula of a sphere from its radius, any high school student would solve the equation in minutes.

"Anyone who believes that exponential growth can go on forever in a finite world is either a madman or an economist." - Kenneth E. Boulding

There never was a proper CUDA "moat".

Sure it is a convinient way to do some things with a lot less work than other approaches, but most sane people doing anything on large scale will eventually want to optimize the actual running of things. As long as the development was fast enough in algoritms and hardware that any incremental gains from optimiation were less important such was obvioisl low priority. But once the number of users for a service grows huge, even say a 5% imprevement is suddenly huge numers in real terms and thus worth some effort.

At the easiest level it is to think of it as linked web pages running locally.

Basically you did stacks of cards that could contain things like information, buttons and such and you could then navigate them like you can a web site today.

But on a more complex level it could actually also have actual scripts and such in addition.

As to what to use it for:
-We did a adventure game based on exploring a crazy mages whacky dungeon on it and shared it with others.
-But more seriously it was used for things like training materials and presentations extensively. Less for actual more complex programs.

Well, it depends on your loaclity.

Basically where I live we have a "expectation of privacy" rule. That limits scopes of laws.

Like if you are naked in a fenced in area with no expected visibility outside he area you cannot be prosecuted for public indicency, but if you do that in your open front yard you will be..

Same applies to many other things too where a place with expectation of privacy has special protections for things like photographing, where you need permission in such, but not in places without and many more activities.

That is the difference.

There are plenty. Memoization for instance. Try to solve codeforces problems with algos that run within the time limit...

..to warn Australians that it would impact Apples profits.

...just follow the money. That is how companies operate.

Where inflation has caused drop in big ticker purchases that have driven a lot of the ad revenue, defense spending is instead increasing.