Look, I'm in no position to talk seeing as I once wrote a cron job in PHP, but the profusion of JavaScript in the late aughts and early teens for things that weren't "make my website prettier!" feels very much like a bunch of "webmasters" dealing with the fact that the job market had shifted out from under them while they weren't looking and rebranding as "developers" whose only tool was Hammer.js, and thinking all their problems could be recontextualized as Nail.js.

Well I see huge benefits in building the tools used by a community with the technology this community masters. IMO the Python's stdlib sucks because it's written in C which is a huge barrier to entry.

Sure! Here! Electron.

Browsers have almost become the OS. At least in user land.

Eh, it's not that lightweight, Lua is much better for that.

with wasm and friendly new web frameworks, the only thing keeping js alive is inertia

I think once you get into rust you just have a hard time going back, and it doesn't feel "hard" anymore. I can practically rust as easily as I can python for scripting and for API servers.

Rust really only gets hard when doing library development IMO. That's when you need lifetimes and well chosen types. But that's also why Rust libraries are superb.

1. Rust is the best language for writing WASM in, so you can write Rust and run it in the browser without transpiling to JS.
2. Rust isn't just about speed or GC pauses. Its type system is amazing and allows you to encode things that you cannot in any other mainstream language.
3. It's so incredibly well designed, it fewla like that clip from Ricky and Morty where Morty feels what standing on a truly even plane feels like then has a panic attack when he leaves. Rust rethought everything from scratch, and isn't just some new syntax or fancy compiler tricks. No null, no exceptions, no inheritance, new typing capabilities, etc.

Go made some pretty poor design choices, and now even Google is choosing Rust for a lot of stuff instead.

I usually pick Rust for CLI tools because:

1. It's statically compiled and isn't dependent on system binaries and won't break if there if the system has the wrong version like C/C++, allowing you to distribute it as a single binary without any other installation steps
2. Still produces fairly small binaries unlike languages like Java or C# (because of the VM)
3. Is a modern language with a good build system (It's like night and day compared to CMake)
4. And I just like how the language works (errors as values etc.)

Go is fine, but it has its flaws. I prefer Rust because:

• memory safety is a compiler check, not a runtime check, so you catch issues earlier
• locks contain their values, so you can't accidentally do anything unsafe
• no nil (() is semantically different), so no surprises with contracts
• everything is an expression, which lends itself really well to FP concepts
• actual dependency management at 1.0
• pretty much no runtime, so calling from another language is super easy
• targets WASM and microcontrollers
• no pointers (not exactly true)

It takes longer to learn, but I'm about as productive with both now.

Maybe give it a try; it's my favorite language to write programs in now, it has an extremely good standard library, and for everything else there's a mass of high quality crates, its build system is actually competent and makes compiling on Windows or Linux trivial, plus many, many more quality of life features.

Has Golang fizzled? It has struck me as too primitive, but basically on the right track.

My biggest issue with Golang by far is the close tie to Google. They are not our friendly innovator, time and time again they make decisions that will help them earn more ad money, and nothing else. And they have a lobg history of releasing something and then never fix the issues with it, and then more or less abandon it.

Other than that there are afaik some other issues with go, I'm not an expert but from what I hear the GC is quite aggressive and you can't tell it to run when you want. Doing something time sensitive? Well, bad luck. GC time!

Everything eventually becomes a crab.

Sort of, browsers can run rust code through webassembly. But i dont think this is a full replacement for JavaScript as of yet.

Originally 4 years old at this point it looks like, and the great shift to wasm has failed to manifest.

It was recently shared on Hackernews, I assume that's why it's showing up here now.