Claude did generated a rather good template for what I needed. It did not compile at first but I copy-pasted the errors and it fixed them.

Not all was good, though. It used literal bullets instead of `-` required for lists, but on whole the experience was positive.

It had taken me less time to fix the template than it would been taken to write it from scratch.

Something which Claude was good at. I throw him a crude ASCII "art" representation of what I want and get the right Typst code back.

LLMs - Lossy highly compressed knowledge which when prompted "hallucinates" facts. LLMs hallucinations are simply how the stored information is retrieved.

Memory (human in this case) - Extremely limited, but almost always correct.

Just an observation. No morals.

Almost because most common commands work, but I have not check all.

And almost, because for some docker-compose.yaml which you downloaded/LLM generated you may need to prepend `docker.io/` to the image name

But I think we still do not know.

I've started to think of LLM's as a form lossy compression of available knowledge which when prompted produces "facts".

If you are curious it was a question about the behavior of Kafka producer interceptors when an exception is thrown.

But I agree that it is hard to resist the temptation to treat LLM's as a pear.

I had to post the source code to win the dispute, so to speak.

* AI is the next electric screwdriver * AI is THE steam engine.

My pick is that the AI is not THE steam engine.

That's pretty much it, for maybe 10+ years now. There was a successor project BlueBottle with some promise, but it did not deliver. Later it was renamed to A2. Surprisingly, it did not help.

https://en.wikipedia.org/wiki/A2_(operating_system)

IMO the authors of BB/A2 bet heavily on XML/Java hype, and were trying to make Oberon more like Java. The result was something without much internal consistency and not very usable.

Not being able to use a major browser and not having the resources to write one from scratch did not help either.

Then some of the major figures of this project left. And that was it.

There are some hobbyists and some small businesses which use it for niche projects and that is all

Good for slow typers, not so much for quick ones.

Anyway, that's how I use Skype when I still have to use it. Which is about once a month.

https://github.com/sdiehl/kaleidoscope https://github.com/arbipher/llvm-ocaml-tutorial

The Haskell one is a nice one. Can say nothing about the OCaml one since I found it using a google search.

I've had a try at implementing an Caleidoscope compiler in OCaml but did not finish it. But it was fun to write.

Records were structurally typed. But you can "braid"(?) a record and that will make it nominal type.

   /dev/shm

Should teachers be judged on how a pleasant life they live, or how good they teach?

Maybe, you want to rethink that.

You need the `i` attribute. But this is filesystem dependent. Anyway protecting the `sudo` binary from package managers is a so-so idea.

Not the fastest way, but it seems to work. Best wishes to Andreas.

Debugger writers may not be happy, but maybe lldb supports all conventions supported by llvm.

   fn f1 (x, y) #-> // Use C calling conventions

   fn f2 (x, y) -> // use fast calling conventions