You can't make this shit up if you tried lmao. This is one of the most poorly managed languages to date.
You can't make this shit up if you tried lmao. This is one of the most poorly managed languages to date.
You can't make this shit up if you tried lmao. This is one of the most poorly managed languages to date.
Their PR team is very talented.
Checked, now post the "Rust documentation is a compiler code" gif.
Well, since you asked nicely.
the fuck is this boomer shit?
>cniles referencing shitty obscure films from the 70s
like pottery
seethe, cope, dilate
can't be worse than C++ clusterfuckery
It is worse because Rust doesn't have a Bjarne to lead it
The same Bjarne that allowed C++ to become the clusterfuck it is today?
>autists develop a memory safe language as fast as c++
>the industry freaks out and tries to roll it out as quickly as possible
>a memory safe language as fast as c++
So, Java?
>here are your ints on the heap bro
C++ is memory safe tho
If you use it that way
Reality is most C++ developers are retarded troglodytes who still use malloc
then use it the mem safe way, idiot
No it isn’t.
The language is undefined, just like their sex lulululul
>>Java
>>as fast as C++
Yes. There are no developers on this board who work on the products with complex computations or memory fuckery that require maximum performance.
For everything else there is no difference in performance between Java and C++.
I work 90% on numerical software, probabilistic programming and machine learning. So shut your mouth.
>machine learning
Is dominated by Python. Not exactly the best performant language.
I use mainly Julia. But you are a retard because you have no idea how the python numerical libs work, they are all written in C or Fortran
Well, it's YOU who are a retard then.
Low-level doesn't matter, because it's written once. You can unironically kill off all people who can write a compiler and IT industry will not stop.
You can't, because people who know how to write completes are necessary for making new cpu's, you will eventually run out of working chips.
>making new cpu
Once the CPU layout is ready making it is a completely automated process.
And the CPU progress has stagnated already, you can use even a 10 year old CPU and not feel any difference.
e whole factories
>e whole factories
The whole factories with all the manufacturing processes are being sold, and no CPU R&D is required to operate them.
>And the CPU progress has stagnated already, you can use even a 10 year old CPU and not feel any difference.
Hilarious cope. I hope your 2500K is keeping you warm.
CPU progress did not stagnate at all. you probably mean consumer compute chips, like your PC's or phone's CPU. many things have improved that are not so easy to market, i.e. load-branch-prediction, better parallel silicon utilization for ooo-execution, many commonly used code-segments/functionalities received dedicated circuits like crypto etc.
we also saw some of the biggest regression happening, like intel pushing TSX only to abandon it completely when someone proved it to be a security nightmare. multiple flavours of ARM TrustZone being released and broken etc.
learning how to write a compiler (full toolchain) can be done in your basement. other than some manuals, electricity and time, no resources required. I bet you could even make a sort-of-useful compiler with zero knowledge other than being a competent programmer, just by bothering chatGPT long enough.
designing chips (for non-proto/non-scientifc applications, that can be mass-produced, are useful, and are profitable) is a hands-on practical experience you can only learn by working at (or founding) a billion dollar factory. any gap in experience must be mentored, or learned by making costly mistakes.
and when your new chip uses an old ISA, you can re-use the compiler. adding new instructions to an existing assembler is probably a hard thing, but you don't need to be able to design a full compiler or assembler to add a new instruction.
>Not exactly the best performant language.
Python isn't used directly for ML you brainlet, it acts as a wrapper for c libraries which perform the calculations
Rust definition: impractical shit in a rusty dick cage.
>as fast as a native exec
Cool, but where is the real use case?
You know, a microservice that reads some HTTP json request, calls a database, does some business logic and returns a HTTP response.
Ahh, there it is.
https://www.techempower.com/benchmarks/#hw=ph&test=composite§ion=data-r22
>Rust
>Rust
>Rust
>Javascript
>Java
>C
>Java
>Java
>Rust
>Rust
>Java
>Pascal (lmao)
>real use cases
pretty much anywhere outside of your docker containers. Besides not every system has the capacity to run a whopping JVM and eat up all its ram. And in many realtime software, you don't want to have to deal with the GC doing a massive cleanup, slowing down everything else it's doing
>pretty much anywhere outside of your docker containers.
So, not in FAANG.
oh believe me, fagman loves c++. Your typical corporate job however less so
Just because you webshits are not allowed to touch critical stuff that doeen't make it disappear
>first language with a user specification
BRAVO
What, do they specify the users of the language? Now that would be new.
>the code is the spec
this is how you make something that's "open" into proprietary software
There's one working reimplementation (mrustc) and another in progress (gcc-rs). The test suite goes a long way.
IME the vast majority of software is like this, including a lot of software that is following some standard or other. I like specs but they're uncommon.
cope
Yeah because rajesh's billionth crud api doesn't need the same rigour as a fucking compiler to a top10 language
Kys
C and C++ both took ages to get a standard, Python has a "language reference" but PyPy has to mimic so many implementation details that it even uses the same bytecode, leading JS implementations refuse to implement required parts of the spec (tail call elimination), the SQL standard is widely considered a joke.
Rust getting a true specification after eight years is run of the mill. It's fine.
I mean they can't define what a woman is, you expect them to define a programming language?
>starts thread about rust
>thread comments are all jabs at c++
Why
Rust makes C++ entirely obsolete.
It only makes certain subsets of C++ obsolete. C++ is memory safe if you use it correctly.
>C++ is memory safe if you use it correctly.
Does anyone?
That's the problem
Irrelevant to the topic.
does rust have oop?
No inheritance but otherwise yes
>No inheritance
That sounds crappy. You need to rely on composition in this case, and the code will still look ugly if you try to deduplicate the logic in different classes.
>and the code will still look ugly if you try to deduplicate the logic in different classes.
Brainlet take.
Works out well enough IME. Depends on what you're doing of course.
It does have default implementations for trait (interface) methods, that solves some cases.
because rust can "win" only when compared to a 40 year old language (only in cherrypicked scenarios)
What other newer language beats C++ in its niche? It's depressing as hell but C++ still reigns
Weird that the most poorly managed language is also the best one.
Rust is literally peak language:
- safe
- highly performant
- effortlessly covers low level to high level
The only downside is that it requires highly intelligent developers.
Whenever brainlets try Rust you get nothing but concentrated seethe.
>peak language
Peak application language, maybe. A systems language can't be "safe"
So unsafe rust is the peak systems language?
>So unsafe rust is the peak systems language?
The failed RedoxOS shows this will never be true.
What makes RedoxOS failed? It looks pretty well implemented to me.
It was written in rust
Why being written in rust a failure? Are you saying C products do not fail?
First off, after 8 years it is nowhere near the useability Linux had after 4 years. So much for the promises of Rust being a superb language for development.
Secondly, the drama is out of control, which it has in common with the Rust community in general, and there has been at least one purge of developers. There is a reason why Linux and even the much younger SerenityOS is ahead and have more active developers.
Last, but not least, there has been at least one suicide already.
Definitions are fascist!
>specification team
>who will not specify
what's their job then? another tech daycare?
Maybe they're working on a new code of conduct.
Descriptive rather than prescriptive
my C code is memory safe
May I see it?
yes
LMAO! The crap language doesn't even have specification!
I knew they were trash but not to those levels.
HA HA HA!
Get festive!
So true sister. You showed those RusttranSegmentation fault (Core dumped)
You can learn rust right now and in 2 or 3 years switch to gccrs with a stable edition.
>You can learn rust right now and in 2 or 3 years switch to gccrs with a stable edition.
You can learn rust now, by the time gccrs hits debian stable you'll be on life support at best anyway.
Good. I want a C99 replacement and no_std is already doing a fine job so I don't care if we wont see it before debian 14. Better stable and working over nightly and shits not compiling anymore overnight.
gccrs is a typical freetard hostile attempt to fragment the ecosystem. rustc is and will be the only rust compiler
Not my problem. I'm welcoming this freetardation because i don't trust the rust webshitter community.
Amazing that the open, diverse, inclusive and welcoming Rust community openly endorses authoritarian monoculturalism.
One Rust.
One Compiler.
One Reich.
(no specification tho)
it's a technical and logical reason. if someone came along and made a better compiler, there's a real risk the rust board will lose some of it's members in a non-recoverable manner.
If someone came and made a better compiler it would be sued by Rust for trademark abuse because it's a direct threat to the board's power.
You can't even use the words "rust" or "cargo" in your monetized yt videos because it falls under "commercial use" - https://foundation.rust-lang.org/policies/logo-policy-and-media-guide/
Not even C++, Microsoft (C#, .NET) or Oracle (Java) are that anal about their trademarks.
>You can't even use the words "rust" or "cargo" in your monetized yt videos because it falls under "commercial use" -
It says it's allowed in books or publications like "Rust Cookbook". I'd argue youtube videos fall into this category, but I'm sure there are gleeful traders whose intricate schnozzes just swung into action from reading my words, detecting potential gains.
But seriously, this is the free and open source spirit.
>But seriously, this is the free and open source spirit.
It absolutely is not. Actually it's the opposite.
I do not understand all this bootlicking.
I was being ironic. So more like this is the absolute state of the free and open source spirit.
I think this entire trademark garbage is ridiculous, especially considering it's 2k23. For comparison, you are explicitly free to use the PHP logo and the PHP elephant too, and it's a much older project than Rust. I understand why Microsoft reserves the right to its trademarks and why projects don't want others to take the same codebase and call it the same thing, but for an open source project to say their logo is for non-commercial use only is a perverse decision.
It all makes sense once you realize that the entire Rust movement is about subverting open source.
Python's and Laravel's trademark policies actually seem stricter than Rust's. Python's even mentions royalties.
They are not. Python's is way more lenient. If you use the trademark "Python" correctly, as in basically not to scam it's allowed for both not- and commercial uses while Rust outright prohibits all commercial uses without prior written approval.
of course, rustc is the Hyperborea, whereas gcc is Detroit. Noone needs 20 incompatible rust compilers as is the case with C compilers.
Of course it's needed. Do you really think that stagnating GCC would've been able to revive itself was it not for LLVM/Clang?
I can link against libraries compiled with tcc from gcc just fine.
Rust has only one compiler and the binaries are not compatible between compiler versions...
good luck compiling code written against gcc compiler extensions with tcc though
What? Did gcc stop stagnating? Last I checked it wass still incomprehensible mess internally and the only feature I'm aware landing because of clang was slightly improved compiler errors, which are still undecipherable if you're dealing with complex things.
It's still irrelevant though, rustc isn't stagnating.
Competition breeds excellence. You can't argue against that.
If you side with the authoritarian policies you're no better than Microsoft.
>rustc is not getting spec and will never be stable
really fits the tranny mentality
>Not having 13 different versions of the same program is literally 1984
My nagger, the gopher has a specification and two official implementations. Even memelangs like Nim have a spec and if it got more popular I wouldn't be surprised to see some autist make gcc-nim. Rust as far as I can tell only exists so corporations can use cuck-licensed reimplementations of popular libraries
Rust is winning, working on a spec would only slow its adoption. We're still in the pre ANSI C era of rust.
You guys do know that they're literally just working on a spec right now?
https://blog.rust-lang.org/inside-rust/2023/11/15/spec-vision.html
Well fuck they're moving too fast for me to keep up with the shitposts.
It's the topic of this thread, the OP just uses a maximally confusing headline
Are they going to patent the specs once it's ready and make them free for non-commercial use only?
>hostile attempt to fragment the ecosystem
that's rich coming from a rust fanboy. I will learn your shitlang and target this compiler's quirks only.
guess you shouldn't have pushed for inclusion into the linux kernel
>check Python library for sending simple requests to certain HTTP API endpoints
>open Github
>nice, should be simple enough, let me see how it wo--
>code is actually in Rust exposing Python entry points
>completely unreadable
>everything is behind 7 layers of abstraction, scattered across a lot of files
>code looks like bad ASCII art, no idea what I'm looking at
>fuck this shit
>look for an alternate library
>less than 200 lines of pure Python
>nicely organized
>straightforward program flow
>functions do what their names say they do
>nicely commented
>just works
Why the fuck do rustards do this? Most Rust projects are only written in Rust for the sake of writing it in Rust. You clearly don't need extra performance for calling an API, and it adds a fuckton of complexity. This is like calling web APIs through C code just because you like the language with the exception that more people would understand your code if you used that instead of Rust.
and you would never know about it if you didn't look, because any program that is secretly rewritten in rust by some mentally ill freak is never advertised as being made in rust, but any software written only in rust is SUPER pushed as "MADE IN RUST"
They NEVER want people to know about rewrites, look at anki.
>They NEVER want people to know about rewrites, look at anki.
This is absolutely true. I remember seeing the codebase first a couple of years ago when it was full Python. I was like yeah, this is cool, perfectly reasonable, it's a portable codebase with a language that is suitable for the job. Then I saw it a year or two ago and it was an unholy mix or Rust, Python, and things many people (including myself) never even heard of. Because you just need the extra performance to show flashcards on a screen.
every sane distribution at thiis moment uses the old version with no rust
>old version with no rust
What's the version number for that? Is it even compatible with their current servers?
Compatible? Yes. Optimal? No.
I use a 3 year old version and even this is nagging me updoot and it prompted me to change some kind of scheduler to a nu version i was like no way fag you ain't fucking up my entire collection
Based.
Lol, it looks like they nuked all the older releases from their github
>Optimal? No.
care to elaborate?
2.1.15
>Is it even compatible with their current servers?
yes
No, it's 6.1.
I'm starting to feel like pushing Rust is the new systemd.
>cant read rust
hahahahahahahahahahaha imagine being this fucking stupid
in your fit of rage you replied to the wrong person
>Uses library written in language he doesn't understand
>WHY CAN I NOT READ THIS
I say that but I don't look like that.
I can read simple programs in normal programming languages. There are no excuses for Rust looking as horrendous as it does. Familiarity is very important for adoption. But I guess the alternative way is to build a literal woke cult around it and push it down everyone's throat.
Why do rust trannies try so hard to uproot c++? Is it because they don’t have jobs
They've devoted a significant portion of their time and based their personality on this language, and they spend an equally significant amount of time trying to convince people that it's worth using so they can get a job. Meanwhile Java, C++, and C# are still the most used and most hirable language skillsets which these trannies can't or wont learn, and C is still the dominant language in open source/hobbyist projects which makes them even more upset so they shill their language even harder.
>Why do rust trannies try so hard to uproot c++?
It's a personal matter to them.
They're focusing on rewriting systems programs because the goal is to be able to say something like
>Over 90% of the internet's traffic is routed using code written by transgender developers. Every operating system, on every computer, phone, tablet, and mobile device uses code written by transgender developers. Without transgenders, there would be no internet, no phones, no modern age.
They'll leave out the part where all of this worked fine already before they came along and rewrote what already existed, using the existing C/C++ code as a template.
>>Over 90% of the internet's traffic is routed using code written by transgender developers. Every operating system, on every computer, phone, tablet, and mobile device uses code written by transgender developers. Without transgenders, there would be no internet, no phones, no modern age.
This is why Bell Labs trannies wanted to rewrite everything in C.
>They'll leave out the part where all of this worked fine already before they came along and rewrote what already existed, using the existing C/C++ code as a template.
C/C++ is why everything stopped working. We had Lisp machines with no buffer overflows in the 80s.
Ego
Rust has no standard, so everything is undefined behaviour.
I mean they would have to define what a woman is first before figuring out a programming language. Too bad they are too busy matching programming socks to their moods.
Experts are predicting that @cogwise is taking over the finance sector in a year or two.
can anyone find a single rust programmer that has kids? I don't think one exists and adopted does not count they have to have had sex. impossible challenge
Bryan Cantrill and Andrew Gallant mention their kids every now and then. I don't feel like stalking people to find out more
>Two men mentioning "their kids"
Anon...
Pretty sure they're married. And not to each other
These are basically normies
At this stage proof is needed. Ijust don't want to see it.
Why are you interested in kids?
>they have to have had sex
I'm not sure if that produces kids when your testicles or womb has been removed, anon