10 ms·
> Naming the entire project after Rust ("rustdesk") is a whole new level though :) That happens to most ecosystems that go through a "hype cycle" just like Rus
by capableweb 4y ago
> Naming the entire project after Rust ("rustdesk") is a whole new level though :)
That happens to most ecosystems that go through a "hype cycle" just like Rust is right now. So many Go projects have something "Go" in them, same with JavaScript, Ruby and all the others who've walked the path.
- xwowsersx 4y agoHah right. I'm surprised at how protracted this hype cycle is. https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=in%20rust%20&sort=byPopularity&type=story https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
- capableweb 4y agoBack in 2011 or so, until forever, it felt like every day there was a mandatory "X made in Ruby" frontpage story as well. I'm sure this one will pass too, once a new language appears that everyone HAS to write everything in.
- lolinder 4y agoNormally I see the name of the language included in libraries, not applications. In that context it makes a bit more sense because it actually does matter what language the library was written in/for. For a remote desktop application it's hard to see why it's relevant enough to be included in the name.
- cozzyd 4y agoYeah, I really think it's weird to include the language name in the package name unless it's a language-specific library (with no FFI... C libraries almost never include C in their names) or bindings to something. The language is (usually) an implementation detail for an "app" And in this specific case, a rusty desk is probably not what most people want, so if you want any non-programmers to use it... it's not the best name.