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

I'd mention fearless concurrency on the website/blog post, as that distinguishes your webserver from, say, caddy.


I wouldn't. Blazing fast, fearless concurrency, etc. are all super cringe at this point. Just say it's fast, secure and reliable or something like that.


I tend to agree. It makes me think that a project is more interested in optics / following trends and is likely overstating things.

Instead of "Blazing Fast", just show a chart showing you are better per core than XYZ.

Instead of "fearless concurrency", show that you are better at utilizing system resources than XYZ.


No it's not.


How does Caddy pale in comparison?


Thank you for the feedback! I think this is an advantage of Rust that prevents common pitfalls related to concurrent programming, making web servers written in Rust safer.


So deadlock free, or don't you just fear deadlocks, rather ignore the possibility?


Deadlocks are easy to debug and fix. Data races are not. There are also tools like tracing mutex to catch deadlocks more easily at runtime without necessarily encountering it.




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

Search: