I read it, and is not that bad, in fact the points it make are probably as close as non-controversial in how make a fast compiler.

And LLVM is certainly major slow in the compiling pipeline. And very complex at it.

What is unclear is how design "a photoshop-like plugin architecture" that allow to do all the optimizations it have, ie: How much the complexity of LLVM is related to the need to intermix all the optimizations and IF is possible to modularize them to the extend to make a lean core?

(A better way to say the same is that it must be. like the nano pass framework, that it have more pedigree in this case than use of photoshop :;)

Must be some social experiment. Machine generated?

I am also suspicious. The way the topic shifts seemingly at random is very common with GPT generated text. It has several correct technical details but they don't support a central thesis, another telltale sign of a GAN in use.

It read sensible to me, but I'm not a native speaker, so maybe the writer is neither one?

This is why Urbit is rapidly becoming more attractive than the Internet. Can’t waste $75 per post.

I stopped reading when they said its architecture should be more like Photoshop. This made me actually LOL.

Has the author ever tried coding a photoshop plugin? Or read a PSD file from scratch, its a notoriously poor interface, bogged by bad legacy decisions and duct tape and string quick-fixes. The PSD file format is a meme and prime example of garbage programming.

LLVM does use a plugin architecture, that’s what the whole IR system is.

Comparing LLVMs architecture to needing to have plugins “Like Photoshop” is like saying the Starship Enterprise should have more rope because it can’t pull this donkey cart.

As the other poster says, it’s a bot.

And which Intel Instruction set is he talking about? They have made several. x86 is the most popular, but it's anything but simple.

I made the mistake to read a few other posts on that site, I feel my brain melting. What garbage.