This may be good and we'd still not have the data (but "they" can collect on their own privately/secretly)

Niantic has the benefit that they can steer "volunteers" to specific points, though.

The story here however I'm not too sure about: Isn't the game mostly played in dense urban areas? - by the time you need military drones there the area will have changed a lot (destruction, fortification, ... and overall be outdated) where I think the civilian drones (delivery, cars, ....) benefit more. While the technology certainly is dual use.

This doesn't mean they want to throw it out of the window in a way which reduces their overall margin.

This increases stakes to protest quite a lot, compared to European worker protection and social security.

For building a competitive AI they'd have to hire the talent, which is expensive and then do a massive investment, which may still end up far behind the competition. (See there attempts with Siri)

Now they can pick the model they want and if time is right they can still build their own.

In the end they still want to sell devices. They aren't doing a search engine (while they could), they are not doing an LLM model, ...

But there are two projects (why one, if you can have two!?), one being Wero by different banks, the other being the Digital Euro by the European central bank. If either finds good adaption (Wero is rolling out slowly and for quite a bunch of banks every customer already got a Wero account automatically) this could move things around ...

Regular expressions in C++ are an example "everybody" advises against using, but it's still there. vector will stay forever and so on.

One can argue about size etc, though.

So I'm not sure the theory holds up.

However a thing that changed is impact: A handful coal workers could interrupt work in significant ways.

This is all nice and good, till the employer needs a reason to fire an employee, then suddenly all such things become relevant. Maybe a bit less in at-will employment situations where there are low barriers for kicking people anyways.

KHTML became webkit (Safari) and then blink (Chrome) so they created the foundation for quite many browsers ...

Issue probably is that the standards process is slow (unless it is a feature Google "needs") and full of bike shedding (which features and how exactly they'd look) and adaption of features by developers is slow.

JavaScript meanwhile should be stable enough as an environment to allow a broader standard library.

Luckily it is slowly getting better (see Temporal as new date library, replacing moment.js usage in many places)

This however is only to some degree the package manager's fault. The JavaScript culture is strongly ordering tiny packages by individual people doing small things (left pad) rather than larger utilit libraries maintained by a larger community.

A larger community contributing to a larger library would mean that a larger community feels responsible and checks it.

That small package mentality a trace to web usage: JavaScirpt code is often sent to the client, not having a huge library but having small dedicated libraries means that it is a lot simpler for the bundler to not bundle dead code which is sent to the browser client.

With server side Node.js this lead to tons of dependencies ... which is worsened by npm allowing to have multiple versions of the same package in parallel. So if something depends on leftpad 1.0 and something else in leftpad 1.1 both are fetched and both are available.

But yeah, nowadays it's mostly SSO, I assume. Which is still annoying as on the SSO site I have to enter my mail address again (or rather: have my password manager doing it ;) ), which is an inconvenience and where I wonder how much of that is to collect data about companies where employees would like to use the service for having sales reaching out. In many places (like Slack or Zoom) company is picked by domain name (yourcompany.slack.com etc.) and then leading to the right SSO.

However PHP leaks different aspects hear and there, making this harder ...