[anon7000]

This is just what modern languages have out of box. (Like rust and go.) it’s a true shame that web isn’t actually unified behind a type safe language with a single solid toolchain. It’s a huge pain to manage and I’m curious how much money it’s cost the industry. “Vite+” isn’t a true solution to that. There are many competing toolchains. And no default standardized one.

[Quothling]

I'm not very familiar with Rust, but doesn't cargo pull a lot of external dependencies for most projects? I really like how Go can do everything with just the standard library, but I wasn't aware Rust was similar. For typescript we've moved our stuff to bun. It has it's own risk management perspective compared to node, but at least it's now possible to build web services without having to rely on a bunch of external dependencies. Which in our highly regulated business would require security policies for each dependency explaining the risks, why we accept them and how we mitigate them.

[jjice]

Cargo itself doesn't pull the dependencies, but yes to Rust's standard library being much more lean than Go. Bring your own HTTP, text templating, and such, but core data structures are provided.

Go gives you a bunch of goodies in the standard library.

Rust provides things like your build system, testing, and package management all together, which is what I assume OP meant.

[nicce]

> without having to rely on a bunch of external dependencies. Which in our highly regulated business would require security policies for each dependency explaining the risks, why we accept them and how we mitigate them.

How about the dependencies Bun is pulling? How did you ever managed to pass security policies with Bun which has so many segfaults that nobody even bothers to write CVEs for them.

[Quothling]

> How about the dependencies Bun is pulling?

What dependencies? OpenSSL, libc or?

> segfaults

Those would not be a compliance issue though.

[1-more]

> a type safe language with a single solid toolchain

Been paying the bills for 5.5 years now writing in one that gets a fair amount of stick for being ~6.7 years with no language version releases (one is planned for this summer though that should make it just under 7). There's one compiler, one standard library, one formatter (with no config options), one linter, and two test runners but one is a rust rewrite of the other one so it's chill. The language being on a timeout has led to all kinds of things like compilers for native (consuming the intermediate representation .o files), fullstack un-forks (no change to syntax of language), fullstack actual forks, really a lot of weird but delightful activity.

It's like me and a few hundred other people, so "unified" is the part that's missing, haha.