6 ms·
I hope we get an alternative than Rust, though. I understand that lots of people like the language, but I personally find it very unpleasant to use.
by JohnFen 3y ago
I hope we get an alternative than Rust, though. I understand that lots of people like the language, but I personally find it very unpleasant to use.
- NewJazz 3y agoWhat about it? What about other languages would you rather see?
- JohnFen 3y agoI just find Rust to be very clumsy and high-friction. This isn't a technical criticism, merely a matter of personal taste. But I dislike Rust enough that I've decided that I won't take a job that requires me to use it. Rather than risk getting into an online argument about Rust, though, I'd prefer to focus on the idea that we should have more than one "memory-safe" language.
- steveklabnik 3y agoFor what it’s worth, the government stuff this article is based on absolutely focused on the category at large, and not just Rust.
- bigfishrunning 3y agoBeing the government, I assume they want to give Ada another go
- steveklabnik 3y agoAda is mentioned surprisingly little, to be honest. I think that everyone remembers The Ada Mandate and its failure.
- pgwhalen 3y ago> I'd prefer to focus on the idea that we should have more than one "memory-safe" language. The very very large majority of code written today is done so in a memory-safe language. C/C++ is the only mainstream exception. The reasons we associate the phrase "memory-safe" with rust is 1) memory safety has been a solved problems for decades for most programming languages, so we forgot about it, and 2) it was _not_ a solved problem for "systems" languages like C/C++ that rust is directly trying to steal market share from.
- fancyfredbot 3y agoThere are an awful lot of memory safe languages. For example Python, Java, JavaScript, and the safe subset of C#. Rust just happens to achieve memory safety with a relatively low runtime overhead.
- JohnFen 3y agoThat's a good point. I was thinking of compiled languages and so wasn't thinking about those.
- IshKebab 3y agoThere are memory safe compiled languages too, e.g. Go or Dart. I think Java and maybe C# can be AoT compiled too these days.
- jeremyjacob 3y agoAs well as Nim and Swift
- pjmlp 3y agoJava and C# have been AOT compiled from yearly days as well, the difference to today was for Java AOT compilers were only available in commercial JDKs, and NGEN only supported dynamic linking, while being designed for fast startup times only.
- silisili 3y agoThe paper specifically eliminates languages with garbage collectors, however.
- bpicolo 3y agoSeems to specifically include them? https://media.defense.gov/2023/Apr/27/2003210083/-1/-1/0/CSI_SOFTWARE_MEMORY_SAFETY_V1.1.PDF https://media.defense.gov/2023/Apr/27/2003210083/-1/-1/0/CSI...
- sBqQu3U0wH 3y agoI have a similar opinion. What puts me off about the language is it's horrendously ugly syntax and toxic, cult-like community (maybe these types are a minority, but they are awfully loud).
- calamari4065 3y agoIt's like someone took C, Python, and Perl, extracted the worst parts of all three and jammed them into one hellish language. There's not one thing about rust syntax that I enjoy. It's probably the worst out of any language I've tried, including Perl. I would rather read someone else's Perl script than Rust. It's very much one of these new-age languages that feel the need to reinvent every wheel and invent entirely new syntactical idioms just so they can be different. And yeah, the "just use rust, pleb" attitude is also super offputting. I'm not interested in dealing with people like that when I'm learning a language. I have plenty of much, much less terrible options.
- zkldi 3y agoCould you give any examples of syntax you've hit that didn't make sense or seemed awful?
- calamari4065 3y agoSure, "let foo = bar" is one of the worst things any language can do. Let is redundant, that's what the = is for. Unless it's meant to be equivalent to 'var' or 'auto', in which case it's even worse. Let contains no information, it's pointless clutter that replaced something that did contain vital information. Let tells you the next symbol is a variable. What type? Who knows and who cares, it's a variable, deal with it. C marks a symbol as a variable by using its type name. I mean, this was a very large part of why Perl is so miserable. I will never understand why people choose to implement this in modern languages. Anyway, variables and parameters without explicit, visible type information is a hard no for me. I took a sniff of a couple rust projects, saw this mess, and decided that rust is not for me. I don't care about all the other magical benefits that cure all my ails, this feature is a dealbreaker, full stop.
- alex_lav 3y agoBold take to discuss this on the internet. I agree entirely, but my gripes are generally met with the software dev's version of "git gud".
- wilg 3y agoSwift!
- jamesrr39 3y agoNot sure why either why the article just gives Rust as an example. Whilst there are some performance demanding use cases where Rust/C/C++ are really the appropriate choices, >99% of applications that have been written and are out there are not really worried about shaving the nanoseconds off or GC-pauses and are working just fine and memory-safe on Java/C#/Go/Python/Javascript/Ruby/PHP etc...
- crq-yml 3y agoMemory safety in a general sense of "just" computing things and getting an answer has been solved for a long while by using either garbage collection or static, bounds-checked, allocation with handles and liveness checks. It's the intermediate space where you can allocate byte buffers and make pointer structures willy-nilly that is troublesome, and idiomatic C sends you in that direction like flypaper. Rust is useful in addressing that specific space - with qualification, since of course it concedes to pragmatism and lets you do an "unsafe" where you want to break the rules. But I believe the future of low-level is more in the realm of original open-hardware designs, because you CAN design a computer that builds in the kinds of runtime checks that are currently done in software. It just isn't the focus of companies that want to sell a lot of bells-and-whistles silicon.
- begueradj 3y agoIt seems you are not alone: https://www.infoworld.com/article/3713264/rust-developers-concerned-about-complexity-low-usage.html https://www.infoworld.com/article/3713264/rust-developers-co...