Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Low bar critiques:

> For the last decade, fast-to-ship beat fast-to-run. Not anymore.

Fast-to-ship didn't beat fast-to-run, it was "beating" "quality built software." It still is. Beating here implying that it's the focus of companies.

> picked a harder, faster language

Go is absolutely an easier/simpler language than JS/TS.

> The Python ecosystem is increasingly a Rust ecosystem wearing a Python hat.

The Python ecosystem was just C/++ wearing a Python hat for years. I guess now it's C/++/Rust.

> The old defense of Python and TypeScript was really a defense of the developer experience.

Maybe for Python, but the TypeScript "defense" was always that there is a level of harmony to using the same language for front-end and back-end.

On the example used at the end:

> A shipped app, in a language nobody on the team knew, one-tenth the size of the Electron version, faster at runtime. The humans never had to learn Rust to get there.

Yeah and nobody knows or cares about the app, so it doesn't matter. Using products nobody will ever use as anecdotal evidence is not a great way to end an article filled marred with misunderstandings of the existing ecosystem and practices.



> Go is absolutely an easier/simpler language than JS/TS.

You're suggesting that a language with concurrency is simpler/easier than a language that does not have concurrency.


Does the event loop not exist? Go has parallelism where JS does not. Both are able to run concurrent actions (async in JS).




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: