As long as the tokens keep flowing we'll all be fine. If they stop flowing we're going to be boned with this mountain of low level software we're creating that will need to be maintained. Let's not think about that.
Well, the only way the tokens will stop flowing is if your CPU and GPU stop working, at which point you have bigger problems than what languages your programs are in.
And unless you're writing in assembly or raw machine code, "low level" isn't quite the right terminology. There's nothing more inherently complex about maintaining code in Rust, Go, or even C than in TypeScript or JS.
> My CPU/GPU is incapable of running a SOTA model, local models are garbage.
I've been using quite a few local models lately, and can confirm explicitly that they work quite well. Ornith 1.5 36B and Qwen 3.8 27B are both extremely useful. Qwen 3.8 is dense, so can be slow without a powerful GPU, but Ornith is MoE, and I can get about 15-18 t/s on my laptop, running off of battery.
> Yes compared to TypeScript code, Rust is absolutely lower level and more work to maintain
TypeScript is only higher level from the perspective of how many abstraction layers sit under it at runtime. That directly aligns with the traditional distinction between compiled and interpreted languages. Yes, Rust is often being used as a "medium-level" language in cases where C was the only game in town before, but you don't have to use it that way.
From a syntax and "work to maintain" perspective, they're about equivalently high-level, although the typical toolchains associated with TypeScript frameworks are a convoluted nightmare, and Rust easily wins in terms of simplicity and maintainability on that front.
As long as the tokens keep flowing we'll all be fine. If they stop flowing we're going to be boned with this mountain of low level software we're creating that will need to be maintained. Let's not think about that.