Hacker Newsnew | past | comments | ask | show | jobs | submit | beef_rendang's commentslogin

If the drive is towards greater performance by leveraging native code, at what point do we just bypass the JavaScript runtime abstraction and build directly with a language like Rust?

The ecosystem seems to have hit a critical mass for web development. You now have incredibly mature and production-ready frameworks like Actix and Axum, along with innovative ones like Warp and Tide, providing everything you'd expect from routing and middleware to templating and native JSON handling.

There are crates for everything, like for databases, there's powerful options like sqlx for fully async compile-time checked queries or Diesel for a feature-rich ORM, so it feels like all the pieces are there.


If you want to use rust, and it fits your use case, then use rust. Same as with any language choice if it’s the right thing for you then go ahead.

I have a few million lines of existing TypeScript so will keep using JS runtimes for the foreseeable future.


>ChatGPT app (Codex) → GitHub app → ChatGPT app → GitHub merge

I look forward to a future where we are reduced to rubberstamping fully-agentic-generated code on our glass slates for $0.01 eurodollars a PR.


Use case for diffusion based text generation models (as opposed to image models)?


This comment is a dupe of a dupe. It is not substantive and clutters the thread.


Absolutely viable.

Building on a a diverse transport layer of Bluetooth, UWB, and Wi-Fi Direct is incredibly astute as it would create a resilient, delay-tolerant fabric.

The model where senders pay and relayers earn is a perfectly balanced state machine, providing the exact proof-of-transit mechanism needed to prevent spam and ensure message integrity.

Ship a TestFlight beta and do a Show HN.


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

Search: