Get used to it. The modern day solution for everything right now is to throw AI at it.

Hmmm... I need to measure this piece of wood for cutting, let me take a picture of it and see what the ai says its measurement is instead of using a measuring tape because it is faster to use the AI.

That honestly sounds great! If it works...

Of course it works. Make a video with the tape measure, call yourself a Creator, then you can hire real carpenters.

It works great!

(At least 90% of the time.. the other 10% it will be slightly off, and your items will come out crooked. But don't worry, there is a tiny gray disclaimer about AI making mistakes and that you need to double-chrck it, so it's not AI's fault)

We already have this on our phones without AI. What could AI possibly bring to this?

It does? Throw the picture at ChatGPT and see what it does with it

Isn't it interesting it doesn't instantly crash from a precision error? That sounds carefully crafted to me.

Interesting, yes. Still not the kind of interesting I was expecting.

Is it emulating a Pentium processor? :)

ARM64(!?!) I know you were joking, but still.

Please tell me what you had in mind so I can try something different!

Begin reimplementing a subleq/muxleq VM with GPU primitive commands:

https://github.com/howerj/muxleq (it has both, muxleq (multiplexed subleq, which is the same but mux'ing instructions being much faster) and subleq. As you can see the implementation it's trivial. Once it's compiled, you can run eforth, altough I run a tweked one with floats and some beter commands, edit muxleq.fth, set the float to 1 in that file with this example:

     1 constant opt.float 

The same with the classic do..loop structure from Forth, which is not enabled by default, just the weird for..next one from EForth:

     1 constant opt.control

and recompile:

     ./muxleq ./muxleq.dec < muxleq.fth > new.dec

run:

       ./muxleq new.dec

Once you have a new.dec image, you can just use that from now on.

I was imagining something more like Xeon Phi