Wish I had something like that when I was coding demos around 1988... :-)

(Edit): you kids have it easy.

I wrote something similar in the 1990s. Except, I had to write the TUI library myself (in x86 assembler) since nothing like what I needed existed at the time.

I was working on a project to do ECU performance curve remapping for a rally driver friend, so mine had additional features like the ability to export memory segments as .m files for plotting curves in Matlab.

I watched a video about ECU remapping (on a modern processor) yesterday, and the guy started by using the OBD port to get access to the system. I had to physically desolder the EPROM from the board to dump it back in the day.

The kids today have it far too easy.

I grew up in the 80's programming my C64, assuming that this would be more or less the sort of thing I'd be doing for a living. The reality is actually pretty disappointing. I _wish_ anybody still did this stuff.

Answering the question: it would be called "the Erlang VM", and you'd use Elixir to program it.

https://elixir-lang.readthedocs.io/en/latest/mix_otp/10.html

Yeah but... who does that?

How is that relevant? we are talking about models, now what you do with them.

For text, have a big model generate the "intelligent" answer, and then ask a local LLM to rephrase.

Yeah exactly, you can always do that by using another model that doesn't have the watermark.

...and does no harm for unfixable bugs. It's the logical equivalent of "switch off and on again" that as we know fixes most issues by itself, but happening only on a part of your software deployment, so most of it will keep running.

I do the same thing - Instead of going first to an unknown site that might (will?) be ad-infested and possibly AI generated, so that a phrase becomes a 1000-word article, I read the comments on HN, decide if it's interesting enough to take the risk, and then click. If it's Medium or similar, I won't click.

Hey, coming out feels good - I thought I was the only one.

Instead of LLM, Python and whatnot, it could have been a cheatsheet: https://github.com/scottvr/wtffmpeg/blob/12767e7843b9fd481ba...

In the end, I'm not sure I get what this is for - the venturebeat piece seems written by an AI.

Raspberry pi with microphone and camera.

The only disruption here is the hyperbole.

Just my two cents - the worst pieces of tech I ever worked with in my 40+ year career were Hibernate (second) and XSLT templating for an email templating system around 2005. Would not touch it with a stick if I can avoid it.

I don't think it was single-cycle, someone mentions a STRCPY instruction that would be quite hard to do single-cycle....

Single-cycle doesn't mean that everything is single cycle, but that the simple basic instructions are. As a rule of thumb, if you can add two registers together in a single cycle, it's a single-cycle architecture.