Kinda like a /. post.

The real killer app for AI will be when someone creates an AI that grovels over all the millions of low-effort AI slop games out there and flags just the interesting/fun/novel ones for your attention. Otherwise you'll never find the gems amongst all the dross.

I felt that Duke Nukem 3D was a journey of ripping people's heads off and shitting down their throats ;-)

It's worse. OpenAI train on user conversations and monitor them for keywords, looking to scoop people's private ideas. This has been documented in individual instances, it is also implied in the terms of service, and it is common sense in a world where the primary training materials (books and web conversations) have been exhausted while the system shows no sign of improving on its own.

Luckily their financial ponzi scheme isn't going to last too much longer. Neither will Anthropic's.

Exactly. And Vmware's calculus is that as long as it has a dozen gigantic clients (governments, huge enterprises) that it can charge whatever it wants, then the small fish aren't worth it.

With permanent DST we won't get the stories twice a year.

They'll need the money to settle all the resulting lawsuits.

D'Oh!.

There's also a novel that states that the lifeblood of an organism can be used to bring eternal life to certain parasitical creatures (who otherwise can't survive in sunlight). It's probably worth washing the transplanted hearts in holy water before inserting them into the recipient.

There's no reason why Python (compiled from Rust) would be any slower than Python (compiled from C). Both languages compile to native executable code, and both have good optimizers available.

We have bubonic plague infections every year in the United States. Very, very few, admittedly, but it's not like it's been eradicated. So there's still benefit in studying it.

"Past performance is no guarantee of future returns" applies to any recorded dataset. Modelling a fictional being's mental states is fun, but stating that it is useful is premature.

The observed fictional being might be always sleepy in your dataset (because it's easier to record him when he's not moving much). And identifying the being's favourite colour (orange) may be irrelevant and wasteful in your model.

If you observe yourself in the mirror, and see your reflection eating spaghetti, is it a useful framework to pretend that the spaghetti is real? If you're still hungry, will you reach through the glass to steal the plate from the other you? And should you first make a plan how to defend the loot, in case the reflection becomes angry and punches you in the face?

Python isn't a glue language. It's the lingua franca of most programmers in the workforce at this point in history.

Try hiring some expert C++ programmers, or even competent Java programmers. They're in the minority. What you get instead is barely competent grads who only know Python. What do you do with those grads after you've hired them?

1) teach the grads a strongly typed industrial strength language so they can contribute.... eventually

2) develop your new projects in Python because the grads can be productive straightaway, and the long term issues with Python can be pushed off to a future manager.

Which brings me to my point: Python should be frozen as is. No more development. Tinkering with it just because some people want to contribute and get visibility in open source is not a good cost/benefit outcome for humanity.

Freeze Python. It's the modern BASIC. Move all the existing developers to a new, unrelated programming language project. Give them free reign to do whatever they want there.

The more I hear about this so-called "SF Democratic Party," the more I'm convinced they don't speak for the majority of SF voters. Seriously. They seem to be some strange, centrist organization that no voters belong to and nobody knows where they get their money from.