I would love an immutable history temporally indexed (shows latest ‘version’ of a row by default), however this doesn’t look like it, and something ‘modern’ being built in Go fills me with about as much trust in its stability and security as it being built in C or C++, which isn’t much, so that’s a weird language choice for something where they keep talking about the security…

That’s even before getting into the lack of pretty necessary features as well.

Golang’s curse, as Java’s before it, is the accessibility and appeal to a bigger group of programmers – OK let me not pull punches here, let’s call it like it is: more mediocre ones.

This inevitably leads to an explosion of popularity, writing a lot of frameworks and tools in the said language, and then 10-15 years later the industry is horrified by the ecosystem and the software quality, someone invents the next “accessible” language, everyone is all excited how “the new stuff fixed 10% of the problems of the old stuff” (let’s get real, that’s what it is very often) and the cycle repeats.

(sighs)

Until people actually make declarative programming work – and have it compile directly to machine code, or maybe better yet, to a highly successful language in terms of a compiler like Rust, OCaml or Ada / Forth – then I don’t think the area at large will at all progress.

I am about to hit 42 and it’s all just repeating in front of my eyes and makes me hopeless. We as a collective just don’t learn…

All progress has already been or can be done by a Lisp language (or scheme’ish, like RacketLang, lol). ^.^