My intuition is that they will convert to zig again when it stables. If it is possible to do it using LLM in 2 weeks for rust, then it would be the same for zig, too.

While rust is nice on paper, writting complex software in it is mentally consuming. You can not do it for a long time.

If they are looking for a memory-safe language, why would they convert to Zig?

If they do, it could be because safety is a gradient and one variable among many in software development, albeit a very important one when it comes to browsers.

OpenAI is speeding up the race to be the most evil company in the world. Impressing.

Tools exists so we can spend our time focusing on more important matter. AI is not any exception of that.

Till this day even there exists IDEs with proper auto-complete suggestions (or editors with LSP support), there are still a lot of people prefer doing it in the old way (vim/emac/nano) and none of them get fired for that.

Z3 exists but we still like to solve algorithms by hand. High level languages exists but C/C++ codes are still written every day, even asm is still used.

On the brighter side of the issue, we now have ton of legacy projects written in obscure languages (COBOL, FORTRAN) that only some dozen people can maintain effectively, and those people are mostly at retirement age now. GenAI can solve that.

you can absolutely still use `--`, but you need to add spaces around them.

Have you ever tried parsing html in s-expression languages before?

For example, in elixir parsing html is this syntax: `{html_tag, attributes, children}`.

You indeed can include attributes in s expression

Don't be antisemitic.

Now? I had found some used epyc servers with 2TB ddr4 ram for around 5k usd yesteryear. Too bad I didn't purchase it.

He said GPU servers

The point is that we did have CPU servers with TBs of RAM. These machines are still pretty much relevant.

He didn't say VRAM. GPU servers are just servers with GPUs.

wal archiving is piss easy. you can also just use basebackup. with postgres 17 it is easier than ever with incremental backup feature.

you don't need horizontal scalability when a single server can have 384 cpu real cores, 6TB of ram, some petabytes of pcie5 ssd, 100Gbps NIC.

for tuning postgres parameters, you can start by using pgtune.leopard.in.ua or pgconfig.org.

upgrading major version is piss easy since postgres 10 or so. just a single command.

you do not need pgbouncer if your database adapter library already provide the database pool functionality (most of them do).

for me maintained database also need that same amount of effort, due to shitty documents and garbage user interfaces (all aws, gcp or azure is the same), not to mention they change all the time.

I also encourage people to just use managed databases. After all, it is easy to replace such people. Heck actually you can fire all of them and replace the demand with genAI nowadays.