Which is actually huge. Reviewing and surfacing all the relevant research out there that we are just not aware of would likely have at least as much impact as some truly novel thing that it can come up with.

I worked on a front line product for US banks and built a process to verify beneficial ownership for business account openings. I found the current expectations to be laughable:

https://www.federalregister.gov/documents/2022/09/30/2022-21...

> An individual may be a beneficial owner of a reporting company by indirectly holding 25 percent or more of the ownership interests of the reporting company through multiple exempt entities.

Getting around this is not very difficult if you are clever and wealthy.

The overall takeaway I had was that these kinds of rules don't really work in the cases where they need to the most. I don't know how much of a deterrent this could ever hope to be. We even developed an override process for this based on a request from one of our clients.

I program a lot in Nim including professionally and strongly prefer it over Rust or even Zig.

Primarily because I just really enjoy programming in Nim and getting things done I wouldn’t have otherwise or be capable of doing.

For example recently I needed to automate a GUI app. I tried the Python libraries but found they kinda sucked. Despite pulling in opencv they were slow at finding buttons in a screenshot. Then the one I tried also broke on hidpi displays.

Instead I got Claude to write me up a Nim library to find images in a screenshot. Then had Claude add SIMD to it.

It’s far faster than the python libraries, supports hidpi, and is far easier to install and use. I still use a small Python app as a server to take the screenshots but it’s a nice balance.

> I guess a lot of languages are kind of fungible. If you want a fast, cross platform, GC-based OOP language, the truth is, there are many choices.

It’s true, in many cases they are fungible. Though much less so for languages which compile to native code. LLMs do lower the barrier to switching.

Nim isn’t really a GC’ed OOP language though it supports some bits of that.

It’s really a systems language that can also run anywhere from an embedded device to a web server and as a JavaScript app.

The new default memory management is based on reference counting with or without a cycle collector. So it’s great for latency sensitive settings.

Car manufacturers already give you the same powerful engine that you can't afford/don't want to buy and "shrink" it with SW. If you jailbreak it, you lose the warranty and bye bye insurance.

You should not think that you're paying more for getting less. You should think that finally you can now enable more in your engine if you want to. Until today, you couldn't.

You just had to know that your car is more powerful than the papers say and live with that.

I think this is quite common with EVs especially, where the same motors are used in the base and performance models - they do normally add other stuff like bigger batteries etc too, but also cost a lot more than just 600 quid extra.

For Elizer to really deign novelty here, he'd have predicted the reason why this happens at all: training data. Instead he played the Chomsky card and insisted on deeper patterns that don't exist (as well as solutions that don't work). Namedropping Elizer's research as a refutation is weak bordering on disingenuous.