4 ms·
> Rust has the complexity of C++ plus additional complexity from the functional community. Not even close. C++ has IIRC whole books just on exception handling.
by adamnemecek 9y ago
> Rust has the complexity of C++ plus additional complexity from the functional community.
Not even close. C++ has IIRC whole books just on exception handling. And it's crazy how many styles of writing C++ there really are. Exceptions or not, standard library or not, templates or not, boost or not, etc, etc. C++ templates are a language of their own. A lot of times, if your code made a particular choice, you are stuck with a set of libraries that made the same choice, or you'll be writing an insane amount of boiler place to duck tape it together. This code tends to be some of the most sucky code in existence.
Rust on the other hand feels very cohesive and there seems to be like one style of really writing it.
What parts of Rust do you find experimental? The only thing that's new (in a popular language) is the borrow checker but we can all agree that despite it's novelty, it's a huge step forward.
Another thing about Rust is the community. Just about every Rust package I've come across was very well written. Some even teach me a thing or two. E.g. I haven't seen trees implemented the way they are in this package previously https://github.com/PistonDevelopers/history_tree https://github.com/PistonDevelopers/history_tree.
Go packages are more all over the place. Also the community seems to concentrate mostly on web stuff. The recent Vulkan tutorial by the Khronos group (i.e. the people behind the standard) used Vulkano.rs which blew my gourd. https://www.khronos.org/blog/beginners-guide-to-vulkan https://www.khronos.org/blog/beginners-guide-to-vulkan
> Now it's happening to Rust.
Please elaborate.
> Václav Havel's "The Memorandum"
It's crazy that you are aware of this, I always thought that his work had only a local appeal.
I've written a modicum of Go and the boiler plate was driving me crazy.
- Animats 9y agoMost things about Rust are well thought out and well designed. It's the total weight that gets you. Like LISP, back when too many smart people from MIT were adding to it without an overarching vision. It's hard to keep it all in your head. The add-ons aren't libraries with specific functions; they're new control structures. This gives me the feeling I had dealing with the MIT Loop Macro.[1] Proliferation of control structures is not a good thing. > Václav Havel's "The Memorandum" It's crazy that you are aware of this, I always thought that his work had only a local appeal. Saw it at Fort Mason in SF in the 1990s. I've written a modicum of Go and the boiler plate was driving me crazy. That's how I felt about Rust. See some code I wrote at [2], at "Return type and its error handling". Now that's boilerplate. The last time I mentioned this, it was brushed off with "Oh, you'll be able to do that with the '?' operator when it's implemented." Feel free to submit a pull request for the rewrite. [1] https://www.cs.cmu.edu/afs/cs/project/ai-repository/ai/lang/lisp/code/iter/loop/mit/0.html https://www.cs.cmu.edu/afs/cs/project/ai-repository/ai/lang/... [2] https://github.com/John-Nagle/rust-rssclient/blob/master/src/rssread.rs https://github.com/John-Nagle/rust-rssclient/blob/master/src...
- zzzcpan 9y agoI think you are describing the "design by committee" kind of problem, that Rust definitely has.
- adamnemecek 9y agoI get your lisp comparison but the fundamental difference is that in rust even the craziest stuff is bound to be safe. I wouldnt be comfortable doing this sort of stuff in other languages, but I'm OK doing it in rust. Re error handling, Option's map method doesn't do the trick? Sorry on my phone and reading code is hard.