This is super nice to view, could you share how you made it? I want to make something similar for Rotation Matrices

There used to be the halfbakery. I guess there still is. https://www.halfbakery.com/

I still can't figure out how to set up a completely free, completely private/no-accounts method of connecting an IDE to LM Studio. I thought it would be "Continue" extension for VS Code, but even for local LM integration it insists I sign-in to their service before continuing.

I only make art designed to be printed on 10-12 color large format inkjet printers. Making plotter art is not inherently better or worse that printing, it's just a different type of art. I love what people do with plotters, but I just prefer doing printed versions, since what I make is often not possible with a plotter, as I deal in pixels (up to 200+ megapixels), and plotters deal in vectors. It's like Photoshop vs Illustrator, the don't compete as much as specialize in different things. https://andrewwulf.com if interested.

I think there is missing point in this discussion.

Most of the time you build something else.

Like if you build a todo app and have to deal with scheduling you don’t spend time making date library because it’s not your goal. But people would do that.

Heck most developers instead of starting blog on a blog platform start writing code for their own blogging engine.

> Then I realized all those who complained was using JIRA Cloud and we were using on-prem, and it all made sense.

Even Atlassian doesn't use Jira cloud. Btw it's not "JIRA".

As touched on in the article, the beauty of colour names would be that they’re celebrated for the machine.

#124356 might look different on one monitor or workstation compared to another.

Having colour names which are calibrated for the device makes a lot of sense. Assuming those colour names are actually calibrated, which as the article also mentions, so often wasn’t the case.

As an aside, this is a big problem in DTP where your display should match the page. However you obviously wouldn’t use colour names in that specific industry because you’re dealing with a vastly greater range of colours and shades.

This is the latest in a very honourable tradition. My first encounter with it was with Martin Richards's BCPL system in 1972. The compiler generated a hypothetical ISA called OCODE, from which backends generated pretty good native code for Titan-2 and System/360, among others. One of those backends generated INTCODE, which was an extremely reduced ISA, for which an interpreter could be easily written (I wrote one in Fortran). Richards also provided the BCPL compiler and runtime library in INTCODE, so you could quickly have BCPL running interpretively. Then you could use this interpretive version to bootstrap a native-code backend implementation. Put this all together, and you now have a very easy compiler port.

Wirth's Pascal-P compiler of 1974(?) used the same idea, also in aid of a highly portable compiler. I have never been able to find out whether this was an independent invention, or whether Wirth was influenced by Richards's work.

Of course, the JVM and CLR are descendents of this, but they build a very complex structure on the basic idea. Writing an implementation of one of these virtual machines is not for the faint of heart.

So I think Bedrock can be very useful as a compiler target, if nothing else. However, I must agree with some of the other commenters that the 64KiB address space makes it very much of a niche tool. Come up with a 32-bit variant that's not much more complicated, and I think you have a winner.

There was an excellent thread(s? I think) about Nokia around these parts a few months back that covered this in detail by various commentators (perhaps you were one of them).

Wish I'd bookmarked them; some great reading in those