Re:We Fell Out of Love with Next.js and Back in Love with Ru...
by baq on Sunday May 04, 2025 @05:24AM
(#43885592)
I agree, nowadays working on mostly TS backend with some parts in JS written before async/await was introduced and I’m inclined to say TS is better than Python at most things bakcendy. I’m missing sqlalchemy and a sane numerical tower pretty much.
Re:We Fell Out of Love with Next.js and Back in Love with Ru...
by freeone3000 on Sunday May 04, 2025 @03:46PM
(#43889022)
Python suffers from the same problems: its type system has many escapes and implicit conversions, making soundness opt-in and impossible to statically verify. Any language with an implicit cast from its bottom type to an upper type is unsuitable for use.
Re:We Fell Out of Love with Next.js and Back in Love with Ru...
by AlchemistCamp on Sunday May 04, 2025 @01:53PM
(#43888220)
It reminds me of an older dev I met when I was just beginning who had worked even more years and said Fortran 95 was "fine". And he could use it to build pretty much anything. That doesn't mean that more powerful language features couldn't have increased his productivity (if he learned them).
Re:We Fell Out of Love with Next.js and Back in Love with Ru...
by CuriouslyC on Sunday May 04, 2025 @05:36PM
(#43889786)
There's something to be said for using the right tool for the job. There's also something to be said for maximizing your ability to hire developers. Software is a game of tradeoffs, and while I can and do still pick up modern hotness when warranted (e.g. Zig), sometimes the path to minimum total software cost (and thus maximum company value) is to take well trodden paths.
As fun side anecdote, if you're doing scientific computing in a variety of fields, Fortran 95 is mostly still fine ;)
You should still know a language like Rust or Zig for systems work, and if you want to work in ML or data management you probably can't escape Python, but Typescript with Bun provides a really compelling development experience for most stuff outside that.