Hacker News new | past | comments | ask | show | jobs | submit login

introducing a new term when an established term exists seem to add another overhead. "but bro, you'll get used to it in no time." i hear you, buddy. it just leaves a bit bad taste.

anyway, i can't believe i say this, i think dhh's words on tradeoff between squeezing performance out of an ecosystem and "just throw more hardware on it" is a tradeoff that i can clearly choose.




What term are you referring to?

Also, speed and performance aren’t the only reasons to use Rust. Rust also helps ensure correctness in significant ways, and make stable applications.


I would guess "fairings", at least that's the only one I don't know on this page: https://rocket.rs/v0.5/guide/


rocket and flight terms. mount? is it a horse? launch? well, it's a rocket. fairings? good thing they don't introduce cable installation.

i'd rather use haskellin instead of rust if we're talking about "correctness" and "stability", whatever those are.


Then why not use Haskell?


you bet i do.


Every little speed bump that's thrown in your way has a real cost.

When those speed bumps are on the main path that you travel every single day, all those little sources of friction add up to a lot of drag. As an industry we've collectively established this nomenclature over the last 2-20+ years, and throwing it away so you can keep the cute rocket analogy reflects some really bad decisions being made.

Hey, at least everything isn't randomly named after Lord of the Rings characters though.




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

Search: