Everyone can tell that you're being sarcastic. You're being downvoted because you're implying that rust is just a fad, and is only being considered because it's popular right now. You're ignoring everything that makes rust great, and all of the reasons why it's one of the few languages that could be used in the kernel alongside C.
? Its syntax is modern and clean. I'm a Java developer, and writing Rust code is both easier and more fun in basically every situation. Just because industry props up shitty langs like Java doesn't mean we like them. "The borrow checker" isn't a feature or an "idea" they just added for funsies, it is a necessary consequence of ensuring ownership compliance at compile time.
The part that Rust done right but Haskell did not is familiarity, the syntax of rust is so familiar to C-family language that it’s much more easier to pick up than Haskell, although both of them shared similar concepts underneath (sum types, default immutability, trait/typeclass etc).
When I started learning Haskell, I spent way too much time parsing the code than actually understanding it (fortunately I managed to get pass it already), but when I learn Rust I just imported my JavaScript parser from my brain and it works most of the time, leaving me more time to actually understand the concept beneath (borrow checkers etc).
That's because a language being good in that sense makes it difficult to comprehend and hard to use. Those particular examples remain academic curiosities for a reason.
Java isn't that bad a language, at least not on the same order as javascript. It just probably needed to make some significant and breaking changes sooner than it did
I think you’re confusing ugly code people write with the language itself.
If you want to see great examples of how both bad and good Java can look, just take a look at AOSP. The permissions stack is pretty much illegible, but the wireless stack is rather nice and easy to read
Oh yes, let us see a 10 million SLOC Rust project, have it compile in a minute or so at most, and run reliably for over a decade with no problems whatsoever - no traits hell, no lifetime hell, no need to jump down into unsafe code. You clearly have no idea what you're talking about.
I'll say it, Lisp is basically not maintainable by most reasonable standards.
It's elegant for some classical definition of the word, it's fun to write, it's (in principle) even easy to write performant code in (since it enables some really powerful optimizations), but it's difficult to read and reason about considering the object models available in Lisps are a bit awkward (looking at you, CLOS).
Java's ugly as hell with a basically fascist licensing system (if you're using Oracle's JRE), and Javascript's got a type system that actively tries to sabotage you, but portability and maintainability (and enterprise support in Java's case) elevated both of those to where they are now.
I've got no real opinion about Pascal and I like Haskell but it's pretty obtuse relative to most popular languages and part of it is probably a degree of programmer autofellatio.
Is liking Javascript/Typescript (I could not go back to writing actual applications without static types) unpopular in here?
I see a lot of people talking about how it's a shit language but tbh nowadays unless you're actively going out of your way (using var instead of let and const, == instead of ===, etc) the quirks and warts don't really come up.
I feel like a big part of the stereotype is because there's a lot of shit Javascript, not necessarily that Javascript itself is completely awful. When a language is easy to pick up, runs on every computer made in this millennium, and necessary for any website that wants more interactivity than a PDF, you're bound to get a large volume of shit code.
I feel like a big part of the stereotype is because there's a lot of shit Javascript
This is true, but it's led to some design decision in (at least client-side) JS that allow that to continue, and the solutions are pretty silly.
Basic <script> tags will, by default, let you write ultra-weakly-typed, semicolon-optional, var-riddled, ==-riddled code unless you go out of your way and opt into "use strict";.
If you want to avoid that problem client-side, you can use a cross-compiler and just write straight TS (for example), but if you're new to the ecosystem chances are you'll be convinced to use one of a billion frameworks that are going to be out of fashion in a year or two, some of which go as far as using a completely bizarre DSL (React's probably the most heavy-handed popular option)
Then there's NPM. It's just a complete trash fire in terms of code quality, supply chain security, and frankly scope of modules (like left pad, come on, does that really need to be a module?)
React is 8 years old and still going strong. The top 3 js frameworks have been react, vue and angular for at least 5 years. At this point it's hard to take anyone seriously when they claim that libraries go out of fashion every year.
I get that js is a fast moving ecosystem, but it's not nearly as fast as you are implying. It's not 2012 anymore.
Wait, people hate Rust already? Or is the usual fringe fraction of every community that has this potent self-hatred for the thing they read and use every day?
It's weird with Rust. People who dislike it absolutely detest it and are very vocal about it, though they never seem to actually explain their reasoning. It's always just some comment about how it's a fad or how they don't like the syntax.
I may be making premature conclusions, but imagine our average JS coder sees Rust gains popularity, but it's too complex for their skillset. How do they save their fragile ego? Why Rust sucks and the entire community sucks, of course.
I haven't seen this kind of attitude over at C++, probably because C++ is boring and for old people (/s), so the cool kids don't feel like they need to know it to self-validate.
Interesting, my perception is almost the complete opposite. Rust got more JS devs to try out native development than anything else I've seen. Albeit, wasm was a big draw for them too.
C++ devs, on the other hand, seem to be very protective of their turf. Rust is the only realistic contender that C++ has had in decades. And I'm sure quite a few of them are livid at Linus for banning their language while allowing Rust in.
Well, C++ devs are not livid to Linus, because they're busy shipping a good chunk of the world's software.
As for JS devs moving to Rust, that kind of supports my theory. Some JS devs are bright and ambitious and they learn Rust. The rest who don't get it, decide Rust and the Rust community sucks. Them sour grapes ;-)
Did you even read the article? Linus has provided valida objections that if fixed, he might consider allowing it in the kernel. The Rust Brigade has work yet to do to break down Linus.
57
u/JoJoJet- Apr 15 '21
Everyone can tell that you're being sarcastic. You're being downvoted because you're implying that rust is just a fad, and is only being considered because it's popular right now. You're ignoring everything that makes rust great, and all of the reasons why it's one of the few languages that could be used in the kernel alongside C.