Okay so basically this is saving bytes on a technicality but also good programming language design (for this specific purpose).

The first aspect is that since you’re scored on bytes, it’s not really to your advantage to use a language that uses ascii (or utf-8) for it’s tokens, because a large part of it is unprintables like DEL or BELL. So people have designed specially crafted golfing programming languages that use a full 256 possible characters in order to pack as many features as possible in as few bytes as possible.

The good design part of it is that if you really think about it hard, there’s really not that many things you expect a programming language to do. It turns out that 256 total different operands is about in the sweet spot, so each character that’s available in the 1-byte code page is mapped to one command, and the languages are also designed to make as many things as possible implicit, both at the cost of readability. Remember, all that matters here is getting the lowest score, not code maintainability or anything else.

This leads to languages like japt (which is a terse form of JavaScript, I’m pretty sure) or pyth (same for python) or Vyxal (my personal favorite, used to be python based but is now bespoke) that look like this but absolutely own at getting a task out in as few bytes as possible.

Obligatory: https://codegolf.stackexchange.com/q/275739/88192

I was about to say something like "as if management would let you send a design for tapeout without extensive verification and simulation but management that allows you to use genial for this would be exactly the type to not do that 😭

Sure grandpa, let’s get you to bed.

I work in semiconductors, and the very best “AI” has to offer in this space is just searching documentation. It is fundamentally useless at anything silicon-design related, much to the dismay of EDA tool vendors who would really like you to buy more licenses for shit you don’t need.

DevOps was a lie pushed on devs to make them become sysadmins, unfortunately.

Maybe it’s time we invent JPUs (json processing units) to equalize the playing field.