3 ms·
> Counterpoint - slowing down the rate of change of a properly designed language makes it stronger. Having a vast amount of bolted-on cruft with inconsistent de
by throwaway894345 5y ago
> Counterpoint - slowing down the rate of change of a properly designed language makes it stronger. Having a vast amount of bolted-on cruft with inconsistent design principles makes a language pretty horrible. Example C++
Isn't C++ an example of a language that moves slowly and still has lots of bolted on features? Having used it a bit, I would use Rust as an example of a language whose features are very thoughtfully considered and not "bolted on" at all.
If we're just looking at C++ and Rust and drawing conclusions, I would expect the conclusion would be "moving super slowly correlates with more bolted on features, not fewer".
- bregma 5y agoC++ is an example of a language whose features were very thoughtfully considered and not bolted on at all when it was as young and untried as Rust is now.
- N1H1L 5y agoYes. Let's see how much cruft Rust has in 10-15 years as usage accelerates? For example Rust's GPU support is not great right now - and it may very well feel bolted on a few years down the line.
- throwaway894345 5y agoBy C++98 the language was already a hot mess, only 13 years after the language debuted. It's been 10 years since Rust first appeared, and its featureset shows no signs of cruft, nor does its trajectory indicate that it's going to acquire a lot of cruft in the next 3 years. I think it's more likely that Rust just benefited from lots of hindsight with respect to C++'s mistakes. Note also that since C++11, the language has been evolving quite quickly and the features released since have been some of the most thoughtful.
- tialaramex 5y agoEither C++98 is 16 years after it debuted, or it has only been 6 years since Rust appeared. You can't tweak both these timelines in opposite directions and claim to be comparing anything. By 1985 C++ has a published book describing the language (which I still own somewhere, it's terrible) and a commercial implementation as well as Stroustrup's code. While in June 2011 Rust isn't even "pre-alpha" and is just learning how to bootstrap.
- throwaway894345 5y agoWikipedia says C++ and Rust first appeared in ‘85 and ‘10 respectively. Therefore C++98 is a 13 year old version of C++ and Rust today is about 10 years old. It’s entirely possible that Wikipedia uses “first appeared” to mean different things in either article, but I’m assuming (rightly or wrongly) that they aren’t doing that.
- lenkite 5y agoThe inception of C++ programming language began in 1979 when Bjarne Stroustrup was working in his Ph.D. thesis. https://www.stroustrup.com/hopl2.pdf https://www.stroustrup.com/hopl2.pdf
- lenkite 5y ago> whose features are very thoughtfully considered and not "bolted on" at all Rust has it's dangerous, unsafe warts. As someone learning rust, finding out that string slices can cause panics was utterly shocking to me. string slices should have had character indices not byte indices. This was a feature that was NOT thought of carefully. It completely goes against Rust's philosophy as a "safe", catch-errors-at-compile language.