Why don't YOU spend the engineering resources to add RAII and a borrow checker instead of blaming your users?

The language that actually solves concurrency is Rust, but they will never acknowledge that.

And of course there is Rust, which compared to Go has better performance, lower memory usage, smaller binaries, safe concurrency, safe resource handling, and a real type system with tagged unions.

The Go team built good tooling around a mediocre language. Now most other languages have caught up, and Gophers are left writing mind numbing `if err != nil` checks with no benefits left to show for it.

Its languages like C that you have to watch out for, because the LLM will gladly say "this is safe!" when its not.

Integration testing is a breeze through data dependencies. The reproducibility guarantees means we can reference container image SHAs in our Terraform and if the image didn't change the deploy is a no-op.

Bazel is an outstanding build system that handily solves a lot of practical problems in software engineering. Not just "at scale". Practical problems at any scale.

As long as Chromium is open source I don't see what there is to worry about. We literally have the code.

There's a lot to be gained by standardizing on Chromium as well. New features, improvements and optimizations only have to be implemented once instead of thrice, and developers only have to deal with bugs in one implementation instead of the union of bugs in all three.

- gRPC, protocol bufffers

- OpenAPI, Swagger, JSON Schema

- Apache Thrift

- Apache Avro

- Cap'n Proto

- IDL, Microsoft IDL, Web IDL

- etc

And there's no sandboxing at runtime either, everything has permission to do whatever the user can do.

If the "Any" type is just a top type but you have to downcast it to use it, like in Kotlin, then it's not considered optional typing, since you still have to talk about types ;).

If everything goes well, yes. Everything is moving towards static typing with local inference.

This is an important point. There is a small mental burden users face every time they see a new website and have to understand how it has been laid out and where things are and what they mean. Medium gives users "just the content" in the same familiar layout to streamline the process.

Not to mention the sites that have silly disorienting scrolling effects, with things moving around while they slowly load, or are barely even functional on mobile. Although these tend not to be problems for the average blog.