Thinking about abuse potential, is there such a thing as irreversible finger-printing of media generated like this? So that even bad actors couldn't hide the fact that it was generated by AI.

> is there such a thing as irreversible finger-printing

No.

Here's an idea: https://news.ycombinator.com/item?id=39166038#39173769

Elm debugger did something like this, but it's much more limited in scope.

As does Vue - in 5+ years I've never used it

Did not know that. It's an interesting way to keep ownership of the project! What other projects do this?

Being a student not in a narrow sense of being enrolled in a school, but being someone who studies and learns new things by doing rather than simply doing the given task in a conventional/quick/easy way that may not resolve the underlying issues that caused the problems in the first place.

Curious why you need the map to always point to north?

It's been discussed here before, some people (myself included) find it easier to navigate when the map is always rotated north up.

In other words, it's easier to figure out which way you're going and keep your "internal" navi in sync with the app.

It's a preference, not a need.

Alexa is not on a phone or PC. It could only be so useful being available only at home.

Sure it is. There are Alexa phone apps that do full Alexa.

Up until about a year ago you could also do it on the computer but they took it down. https://alexa.amazon.com/

... Because it was a huge privacy risk.

I'm impressed that they are still around.

feels like the private equity guys just haven't gotten around to doing the Toys'r'Us playbook on them yet

With Java, they are executing it pretty well these days. Old code pretty much works out of the box, so you get the improvements for free.

Some language-level improvements are significant enough to get people excited (e.g. virtual threads).

And standard library improvements are pretty low-risk as well.

The only breaking changes I have run into are:

1) The "new" module system. (Which is, IMO, way to hard to disable for legacy code)

2) Removing some old crypto support from the default provider. And removing even mire support when a "secure valudation" flag was set. Probably for the best, but still broke stuff.

Other than that, the only Java code that really feels legacy is:

A) Pre generic collections.

B) an overuse of design patterns (normally not a language issue, although there are still a few bad APIs in the standard library)

C) Long form classes where a lambda would suffice.

Given how much the language has changed, that's a pretty impressive list. And a day with a linter can modernize most of a codebase without much effort.

Good point, but it is interesting that the computations to render visual worlds in high fidelity is the same computation to "ingest" the data to create a model.

Reminds me of how a mic is a speaker and speaker is a mic.

I think it speaks to the generalizability of linear algebra.

My guess is that it’s aimed at celebrities/politicians.