6 ms·
>Feel free to create and use languages with invisible program effects or asynchrony, and I'll feel free to not pay any attention when you do. As if you matter?
by coldtea 6y ago
>Feel free to create and use languages with invisible program effects or asynchrony, and I'll feel free to not pay any attention when you do.
As if you matter? The conclusion could be stripped, and the article would still make its point.
- q3k 6y agoThe snobbishness around Rust repeatedly makes me reconsider if I really should be investing even more time to continue learning the language.
- whizzter 6y agoThe core innovations were brilliant and it does seem to attract a certain kind of developers yes, that said there seems to be quite a few awesome people in the community as well so I guess the strategy is to use it where it's the best tool and not be too invested in the rest.
- deleted 6y ago[deleted]
- justin_oaks 6y agoI'm wondering if people are looking for Rust snobbery and finding it where it doesn't exist. This is not a dig at who I'm responding to, although the comment did trigger the thought. I interpreted the points in the article as fairly generic. The idea of "Inconvenient knowledge is better than convenient ignorance" goes well beyond Rust. The author of the article does imply that Rust does a lot of things right, but I'm curious how one could say "Hey, I like this language it does a lot of things well and fixes problems I see in other languages" without sounding like a snob.
- q3k 6y ago> I'm curious how one could say "Hey, I like this language it does a lot of things well and fixes problems I see in other languages" without sounding like a snob. Just not writing “Feel free to create and use languages with invisible program effects or asynchrony, and I'll feel free to not pay any attention when you do.” would do the trick in this case. Or, generally, show your reasoning, show your arguments, acknowledge any tradeoffs, contextualize against other languages as needed. And perhaps do not jump into every programming language discussion with “this wouldn't be an issue with Rust” unprompted, as that's generally not constructive, and does not acknowledge that there is more to software engineering than just what programming language you pick.
- deleted 6y ago[deleted]
- geodel 6y ago> The conclusion could be stripped, and the article would still make its point. I'd say maybe conclusion was the point. The author clearly said others who wrote Rust articles were not forceful enough that Rust color functions are actually good thing. So they needed to make position clear.
- justin_oaks 6y agoProbably it would have been best rephrased as "Feel free to create and use languages with invisible program effects or asynchrony, but beware of the downsides when you do" That way it doesn't sound like the author's opinion is what matters.