So if a language can't do HTTP and async I/O (with state-of-the-art performance)... | Hacker News

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

_54qb on Jan 14, 2018 | parent | context | favorite | on: Rust in 2018: easier to use

So if a language can't do HTTP and async I/O (with state-of-the-art performance) then we shouldn't consider any other possible application for it? Rust is not Java, you have better languages to build webservers with.

kod on Jan 14, 2018 | [–]

Yes, if a language can't easily do async IO and HTTP in 2018, it is in deep shit with regard to long term adoption. The Rust devs realize this, otherwise they would be putting less effort into tokio.

StreamBright on Jan 15, 2018 | [–]

So if a language cannot do our business need then we shouldn't consider any other possible application for it?

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