It is so weird when people idolize programming languages. They are all flawed and they all encourage some bad design patterns. Just chill and pick yours.
Yeah, but that makes it sound like they're all equal, and there hasn't been any progression, which is untrue. You're either insane or a historical reenactor if you write something new in COBOL.
I think Rust is genuinely a huge leap forwards compared to C/C++. Maybe one day it will be shitty and obsolete, and at the very least it will become a boring standard option, but for now...
Rust is already obsolete, compared to Stingpie's excellent assembly language, paired with object oriented programming!
This is the SEALPOOP specification:
I now want a community led historical reenactment of loose tie wearing software devs in the 60s where they are just chain smoking and banging out COBOL or Fortran punch cards
!retrocomputing@lemmy.sdf.org
I don't think much happens in person, but the community for it definitely exists.
C++ when it was new was exactly like this. Rust still hasn't had 30 years of legacy, all these Rust prophets will shit on it's name in 15 years when they have to maintain huge codebases with it
Besides, C++ is very likely to adopt memory safety
[warning: "annoying Rust guy" comment incoming]
I don't think Rust is perfect, but arguably I do "idolize" it, because I genuinely think it's notably better both in design and in practice than every other language I've used. This includes:
In a literal sense, I agree that all (practical) languages "are flawed." And there are things I appreciate about all of the above languages (...except Tcl/Tk), even if I don't "like" the language overall. But I sincerely believe that statements like "all languages are flawed" and "use the best tool for the job" tend to imply that all (modern, mainstream) languages are equally flawed, just in different ways, which is absolutely not true. And in particular, it used to be true that all languages made tradeoffs between a fairly static, global set of binary criteria:
Looking at these, it's pretty easy to see where most of the languages in my list above fall on each side of each of these criteria. What's special about Rust is that the core language design prevents a relatively novel set of tradeoffs, allowing it to choose "both" for the first two criteria (though certainly not the latter three; the "ease-of-use" one is debatable) at the expense of higher implementation complexity and a steeper learning curve.
The great thing about this isn't that Rust has "solved" the problem of language tradeoffs. It's that Rust has broadened the space of available tradeoffs. The assumption that safety necessarily comes at a runtime cost was so pervasive prior to Rust that some engineers still believe it. But now, Rust has proven, empirically, that this is not the case! And so my ultimate hope for Rust isn't that it becomes ubiquitous; it's that it inspires even better languages, or at least, more languages that use concepts Rust has brought to the mainstream (such as sum-types) as a means to explore new design tradeoff spaces. (The standard example here is a language with a lightweight garbage-collecting runtime that also has traits, sum-types, and correct-by-default parallelism.)
There are other languages that, based on what I know about them, might inspire the same type of enthusiasm if I were to actually use them more:
...but, with the exception of Swift, these are all effectively "niche" languages. One notable thing about Rust is that its adoption has actually been rather astounding, by systems language standards. (Note that D and Ada never even got close to Rust's popularity.)
I know religious people who could not explain their faith so specifically.
Because they just have their own brain chemistry as the basis of it whereas the above comment clearly states:
Rust has proven empirically that the tradeoff between performance and safety doesn't need to exist.
Which is truth. And it's much easier to base a coherent argument on truth rather than vibes.
Have you actually ever seen an example of such an annoying rust dev? Cause I haven't, only a ton of people who see rust as their enemy number 1 because of such people. Those who are "annoyed" are way more annoying…
I have. You just don't hang out in the "right" places
I have made experiences with annoying PHP devs and I don't hate them.
My critic wasn't towards rust devs or any devs of any language but towards idolization of a language instead of studying the nature of those languages the flaws and advantages and use the best tool available or attempting to create a better tool.
How can a rewrite in a completely different language violate this license? There should also be a clause "Once you looked at the source code you must not write anything with similar functionality .... in any programming language"
Leaked Windows code made Wine and ReactOS devs anxious, since MS could sue over it. On the other hand, I've looked up the keycodes from the Linux kernel for X11 (it's literally just PS/2 with the unused codes being used in place of the E0 keys), and they haven't yet came after us.
It made them nervous because someone might put parts of the original source into Wine. You can't do that in a rewrite in a different language, it doesn't even make sense. The thing the people in this screenshot are gloating about isn't even relevant to this license.
That's a lot of words for "I don't understand the borrow checker"
In all seriousness, yeah rust users are annoying, but I think rust is a welcome change over C/C++
Hey I'm both an annoying Rust user and I also don't understand the borrow checker. I just put & and * in front of things until it works.
I found this tutorial pretty helpful for that: http://intorust.com/
You can presumably skip the first two chapters...
Speaking as an annoying Rust user, you're being bigoted. I'm annoying, but the vast majority of Rust users are normal people who you wouldn't even know are using Rust.
Don't lump all the others in with me, they don't deserve that.
While the borrow checker has its downsides, so its legitimate uses. A few people in the D community were thinking about implementing it as a library.
Didn't know D still had an active community, that's pretty awesome. Wonder if someone has ever worked on a borrow checker for Nim.
D seems to getting traction yet again, and some stuff might get better (D3, new GC, new standard library, etc).
It really whips the crab's ass.
Lol rust winamp clone let's gooooo
Agreed, crab that anti-foss activist in particular
ironic that winamp is was built on open formats and widespread IP theft (music ripped and shared)..... but they're strangely prickly when it comes to their code.
:|
The guy who wrote Winamp Sold it decades ago. So you should clarify who is defensive about their code :-) The original coder is really good - he also wrote the awesome AVS visualization plugin for Winamp which among other things utilizes a special programming language called "eel". After selling Winamp he went on to create Reaper which also uses eel I think.
That’s insanely dumb
Rust (derogatory)
you may not create, maintain, or distribute a forked version of the software
ok, i'm just gonna host it on my website for archival purposes and if someone happens to download it that's not my fault
Huh weird, these pull requests just magically accepted themselves
host it on my website
That's distributing and barred under the other license item. Sorry to burst your bubble.
godamn C lovers
Some of these people are Javascript web developers idealizing system development and the C language.
The license, even if it's truly just to avoid rust (for whatever dumbass reason they have), is enough to me to hardpass on the entire project.
No distribution, but he didn't say no distributing a language parser to change it into rust and then microcompile a new executable on the spot.
Tell me you are having a midlife crisis over not wanting to change over from the programming language you grew up mastering without telling me you are having a midlife crisis over not wanting to change over from the programming language you grew up mastering.
Is it really just old men saying stuff should remain in C/C++ to preserve their nostalgia? What a bunch of petty bullsh!t.
I want to use Rust, but it lacks an Specification. Until that is done it's a no go.
TIL about this problem.
What is this abi and standard calling methods you speak off? Are you a rust-non-believer or some shit! Rewrite it all in rust, no questions asked!
( i too like the ideas of rust, but without a decent abi or not constantly changing interface, its useless to me. I dont want to rebuild all code, including libraries every time i update 1 library in my application )
You're aware that Rust gives you access to the full C ABI?
What language are you going to use instead that has a better ABI story? Swift? Or maybe a dynamic language like Python?
I know that exists, but whats the point of that? You loose all advantages of rust when you use the library then because it cant predict application state with the library code. There is a reason all those rust libraries are compiled locally when you compile a rust application. Its a major lacking point for rust, and as long as it lacks that its dead in the water for big projects.
Again, i like strong type stuff and i like the ideas of rust but it is not grown up enough for me
So, not a programmer, just a rando on Lemmy. There are racist programming languages?
/j
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
