508
One Of The Rust Linux Kernel Maintainers Steps Down - Cites "Nontechnical Nonsense"
(www.phoronix.com)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Well, I've been a C/C++ dev for half of my career, I didn't find Rust syntax ugly. Some things are better than others, but not a major departure from C/C++. ObjC is where ugly is at. And I even think swift is more ugly. In fact, I can't find too many that are as close to C/C++ as Rust. As for logic.... Well, I want to say you'll get used to it, but for some things, it's not true. Rust is a struggle. Whether it's worth it, is your choice. I personally would take it over C++ any day.
When in doubt - C4!
That doesn't really excuse its behavior in the video though.
I just don't understand this. You get used to the syntax and borrow checker in a day or two. It's a non-issue.
I wouldn't say that. For primitives yeah, day or two. But if you want to build a proper program, it'll take time to get used to it. For my first few projects I just used clone everywhere. Passing by reference and managing lifetimes, specially when writing libraries is something that takes time to get used to. I still don't feel confident.
Besides that I do like Rust though. Sometimes I feel like "just let me do that, C let's me", but I know it's just adding safety where C wouldn't care.
Unless you're a functional programming purist or coming from a systems programming background, it takes a lot longer than a few days to get used to the borrow checker. If you're coming as someone who most often uses garbage-collected languages, it's even worse.
The problem isn't so much understanding what the compiler is bitching about, as it is understanding why the paradigm you used isn't safe and learning how to structure your code differently. That part takes the longest and only really starts to become easier when you learn to stop fighting the language.
I see that my previous comment is not the common reality apparently.
I'm mainly a C# + js dev of a few years, and I would love to see what precisely other people here are having problems with, because I've had a completely different experience to most of the people replying.
I tried for about a week: reading documentation, viewing and modifying example programs, using a Rust IDE with warnings for all my silly mistakes, the works. I couldn't manage to wrap my head around it. It's so different from what I'm used to. If I could dedicate like a month to learn it I would, but I don't have the time :/
At rhe beginning, I did hate it. Now I slowly embrace it as it seems like a feature to be mkre verbose.
But maybe it will never change and I will just gaslight myself liking it. Whatever.. you cant take my fun away learning rust for half a year
I hate how I can't do everything I imagine in rust.
But researching about why something isn't possible, makes me realize that the code should never be wroten like the way I did... so I can't blame rust for dissallowing me this.
You've been blue pilled by null. Once over the hurdle, it's very eloquent.
Null is ugly. Tony Hoare apology for inventing it should be enough reason to learn to do better.