3 ms·
This site is for developers, isn't it? For me this is interesting, cause I could see myself contributing to a Rust project, I'm guessing there's more people who
by drogus 5y ago
This site is for developers, isn't it? For me this is interesting, cause I could see myself contributing to a Rust project, I'm guessing there's more people who think that way.
- falcolas 5y agoThis website is for developers; the product feature page should be about the product, not the programmers.
- berkes 5y agoDo you consider the README on Github a "product feature page"?
- falcolas 5y agoNo, but I do consider a "Design Document" to be a product feature page. It's full of product features (and non-features) after all (when it's not going on about Rust). https://github.com/MeadowlarkDAW/Meadowlark/blob/main/DESIGN_DOC.md https://github.com/MeadowlarkDAW/Meadowlark/blob/main/DESIGN...
- lijogdfljk 5y agoAgreed. Furthermore, Rust is/was imo a controversial language - early on some argued it was "too difficult" to write "real" applications in it. I'm super interested in real world performance intensive applications written in Rust, Haskell, etc. Language matters to me, even if i don't plan on participating.
- falcolas 5y agoRust is about as controversial as Python these days, though for different reasons. To be clear, I'm not annoyed at it being called out here (much - it gets old no matter which langauge is pimped). I'm most annoyed at how much space in the features doc, which should be about the project, not the internals.
- drogus 5y agoThis is an early version of the project, so this is most likely not directed at end users. Why would you even address end users at this point? Nobody will use it for a long time anyway, so in my opinion is a great move to address potential contributors in the design doc.