I’ve seen good Python projects and bad Python projects. Not all errors are caught at compile time and performance may or may not matter in non-cpu bound workloads. There’s no “right” language. Python can shine in the right context (including web applications).

The Z80 and 8088 are CPUs from when I was a kid. I clearly remember how 8088 was considered a much more advanced one back then. Nice to see this comparison. Thanks a lot for sharing.

Not a 1:1 replacement, but I created https://github.com/pacha/cels because I wanted to have a more intuitive way of working with JSON and YAML files

I agree. I find working with templated YAML so cumbersome that I ended up creating a tool (Cels - https://github.com/pacha/cels) because of it. I like Jsonnet and Starlark but in practice I don’t usually need a new programming language for most use cases. Most of the time I just want to create a base document and apply patches to do modifications. That simplifies everything a lot. The experience of writing pure YAML is actually not that bad (a couple of things about the format are really questionable, but it is workable). I find that problems appear from the complexity of the solutions you have to add to adapt documents to different environments.

There’s nothing in the original message that suggests that the commenter was expecting a faster execution in an interpreted environment.

Six months if I recall correctly