Whenever someone says they think Rust is a very low-level language I show them this:
 Thalidomide Vintage Ad Shirt $22.14 |
 UFOs Are A Psyop Shirt $21.68 |
Thalidomide Vintage Ad Shirt $22.14 |
Whenever someone says they think Rust is a very low-level language I show them this:
looks like a C++'s template
This is unreadable. I was gonna check out Rust but having seen this, I shall discard Rust in the trashcan of troll languages like Befunge and Malboge.
Do yourself a favor and pick up Go.
Go's compiler is satanic and evil for connecting to the internet for dependencies, so no.
You can make unreadable trash on any language, this was either done on purpose or by someone moronic.
yeah I think aesthetics are underrated when it comes to programming languages and rust is the ugliest language Ive ever seen and with the ugliest user base of any language
I would second the advice of
if youre not doing low level systems and if you need something thats fast, compiled, memory safe, has the best built in concurrency of any language, etc
and best of all you can gain a working knowledge of the language in an afternoon
just
use std::iter{Map, FlatMap, Take};
Holy cancer
It's about as low level as C or C++.
Rust is more akin to Typescript than it is to C. It is not low level by any means.
>It is not low level by any means.
Other than a richer type system, what makes Rust "not low level"?
I'd be more inclined to ask what supposedly makes Rust low level. What makes C "low level" is that it maps closely to machine code, it feels like a natural step up from writing x86 assembly. This same correlation does not exist in Rust, not by a stretch of the imagination. Rust may feel very low level to a programmer used to writing Javascript, but comparatively, Rust is much higher level than C.
>What makes C "low level" is that it maps closely to machine code,
Lol. Reminder, C being a "low level" language is a very modern idea.
>it feels like a natural step
So what makes something "low level" is someone feels like it's low level? What makes something low level?
>Lol. Reminder, C being a "low level" language is a very modern idea.
Reminder: Rust is a very modern language.
I was demonstrating how
> It's about as low level as C or C++.
is clearly wrong. !!Comparatively!! Rust is a much higher level language than C is, I quoted "low level" for a reason. The way you know C maps closely to machine code is because you can easily predict what kind of assembly code the compiler will produce. That is not the case with Rust.
>The way you know C maps closely to machine code is because you can easily predict what kind of assembly code the compiler will produce
I've never met anyone that can actually do this. Lots of claims, no evidence.
I don't disagree with "mapping closely to ASM" as a definition of a low level language, my argument is that there is no language that does that.
>I've never met anyone that can actually do this. Lots of claims, no evidence.
you have to turn off optimizations first, genius.
> I've never met anyone that can actually do this. Lots of claims, no evidence.
People who have studied the ISA they target, read and study the compiler output and debug those programs. I'm not claiming I always have a full comprehension of the assembly-equivalent program, but it's definitely possible to predict what the compiler may produce when writing C. This is not possible with a language like Rust. You haven't met anyone that can do that? I believe it, but that doesn't mean those people don't exist.
>If you study your language, the ISA and the compiler like the Quran, then you can sometimes have a vague idea about what ASM will be produced.... provided you've turned off optimizations.
The level of cope demonstrated by Cniles is honestly incredible.
Imagine learning how computers work to write a program. Imagine working as an embedded engineer, kernel developer, etc.. fricking Cniles am I right? If you actually learn your tools then you will have an accurate idea of how things work under the hood.
>C and compilers are how computers works
Oh am lafin. You've no idea how far abstracted C or even assembly is from how computers work. This is why I mock Cniles, they think that they know "how computers work".
>t. EE
if x86 assembly is so abstracted from x86 then what's the damn point...
There is more to how computers besides a compiler outputting assembly, wow you must be some kind of genius. What exactly is your point, moron?
>in a relatively new field, this idea regarding the field is modern
holy moron
Rust is commonly called a successor to C++, not to C. Zig is the C successor.
The people who work on all this shit unironically hate God.
according to ziggers at least. reminder that even Go started as a C++ "alternative" before the narrative shifted. There's no point to using zig vs c++ or even rust tbqhf
>Zig is the C successor.
Says who? Zig is perpetually in alpha (for almost 10 years now) and continues adding more and more complexity just like C++ and Rust.
If anything, Zig is just another C++ successor, just a simpler one than Rust.
Right now, there is no true successor to C, none.
Nothing small and simple, close to the hardware enough, and yet modern enough to be worthy of being called "the C successor".
I'll wait until someone develops an "embedded first" system programming language, because right now every wannabe system language appears to be some LLVM-addicted turing tarpit of infinite memory and complexity.
It's almost like we forgot how to write small and efficient programs after weblicious companies took over the industry.
I'll be coining this term now:
>embedded-first system programming language
>a system programming language which started with only an embedded version and was then adapted to larger, more capable hardware.
There, if your shitty toy language is capable of running on embedded systems and performs well enough there, it is almost a guarantee it will perform well on more capable hardware. The opposite is almost always not true, likely due to the designers not being forced to design the language under resource constraints.
No language will be worthy of being "the C successor" unless it works well on embedded systems and is close to the hardware enough to displace C in usual low level hackery code. Take your bloated LLVM-addicted weblicious "systems" language and frick off.
I agreed with most of your point but I don't see how performance is an issue. you can get c++ working in embedded systems trivially,at the exact same performance. sure it's still more common to see C based SDKs but quite a few MCUs come with c++ SDKs now. and they aren't worse unless you use the Arduino framework to compile your shit or something lol.
but yes, other than C and to a lesser extent, C++, everything else might as well be irrelevant for most embedded programming. especially LLVM based languages.
>but I don't see how performance is an issue
Only really an issue with newer LLVM-based languages, both C and C++ started with 70s and 80s hardware which had similar capabilities to some embedded systems today.
Good luck getting any Rust or Zig code to run efficiently on a Commodore 64 (from the 80s), that thing only had 64K of memory and a 1MHz CPU. C and C++ on the other hand will likely still run well enough on it.
>C and C++ on the other hand will likely still run well enough on it.
C code certainly runs nicely on small devices. That's why so much embedded work is done in it.
>Nothing small and simple, close to the hardware enough, and yet modern enough to be worthy of being called "the C successor".
hare?
that's ok, he isn't even the craziest maintainer of projects i support
Send this video to drew devault
>ai channel
kys
you're saying the video is made with ai?
kys too btw
>The people who work on all this shit unironically hate God.
>Presentation five (5) years ago, still no 1.0
>Released ten (10) years ago, still no "killer app"
Why are people calling this the C successor again?
This is just Andrew's vaporware language.
>Rust is commonly called a successor to C++
>successor
that never happened. people aren't abandoning c++ for rust in large numbers, troony.
Rust makes it really painful to write anything while caring about memory
>okay, i will turn this vec into a boxed slice because i want to prevent the possibility of resizing or changes in memory location
>allocates
everything allocates/copies/fricks you over
>boxed
>If I put something on the heap, then it allocates
No shit.
the problem is that if you try to do anything with that heap allocation, rust will probably allocate some more
there are no guarantees that drop will ever even be called lmao
>just use Pin bro
doesn't do anything
>just use #[no_std] bro
no, i need to have a fine level of control over allocation, not get rid of it
>rust will probably allocate some more
It shouldn't, at least as far as I'm aware. You'll need space for the size of the pointer + it's contents. But other than that I don't think it should allocate anything else.
>there are no guarantees that drop will ever even be called lmao
Well yeah, something can live for the life of the program. So obviously there can be no guarantees about drop being called. If you're sure about what you're doing, then you can just call drop manually.
turning a vec into a boxed slice calls shrink_to_fit which can allocate
so basically to avoid all of that i have to just use raw pointers and manual allocation, at which point why am i even using rust?
>okay, just write a custom type bro
every crate returns a vec because of how convenient it is
>reading comprehension
Oh yeah
C++ chads are now interested
The double colon for namespaces is horrendous.
Rust is a Turing tarpit.
Reminder that C used to be considered a 'high level language' because it wasn't just straight up assembly. Now it's languages principally with no automatic memory management and AoT compiled.
>MaybeUninit
>PhantomData
it's all so tiresome
i genuinely have no idea what that code does, all i know is that map applies a function to each element of something
It's a definition of a struct with an iterator type spelled out verbosely. Iterators in rust are static - instead of going through a pointer to inner iterator's increment function, they call it direct as it is part of their signature, for example FlatMap has three type arguments FlatMap<InnerIterator, MappedToType, FunctionMapingElements>
They are static for performace, no runtime cost of dereferencing a function pointer, and less function calls in general, because codegen will inline iteration function of InnerIterator into the iteration function of OuterIterator (recursively)
It took me a while to realise this was a type definition and not a function.
Less readable than C++, failure.
Have you ever seen those shitty wallpapers that they use on the news for "foreign hackers?"
Have you ever seen an generative-AI image where you try to get it to generate a photo of code?
Rust is like that.
mental masturbation, basically
What a shitlang, this is supposed to replace C? It reads even worse than C++, and that's already bad enough.
I love Rust so fricking much. Look at this beautiful code. It is immediately clear what it does (as long as you're not cnile).
More like 'as long as you are insane'
you're sick in the head
also
>Ok()
shitter
This is a combination of the worst parts of Python, TypeScript, and Befunge. Legitimately how is it clear?
>Yoke { yokeable: KindaSortaDangling::new(...
what the frick does ANY of this mean?
it's a struct moron. i don't even know rust and i figured that out in 2 seconds
>Look at this beautiful code
>yokeable:: KindaSortaDangling::new()
AHHAHAHAHAHAAHAHAHAHHAHAHAHAAHAHHAAHHAAHHAAH
>Allow clippy
>unsafe
I can't make this shit up any more.
estrogen is known to cause logorrhea and turn people into wordcels who think verbosity is a measure of intelligence
>Create the most obtuse, opaque, convoluted dogshit the language has to offer
>morons respond
gr8 b8 m8, i r8 it 8/8
>Verification not required.
Wtf is this shit
This is a complete dog shit language.
>A Cow-like borrowed object “yoked” to its backing data.
Hi, I am the person who posted this. I would just like to add that I am trans, wear thigh highs, and worship femboy dick.
> '
this language unironically uses ' as a part of its syntax outside of pure strings
holy shit i refuse to believe this level of degeneracy
40 years of C and this is what we have to show for?
>40 years of C and this is what we have to show for
indeed
>more vulnerabilities as Rust gains more popularity
>literally just use strncpy() instead of strcpy()
I see you've never built something larger than fizzbuzz
What happened to 5G languages?
https://en.wikipedia.org/wiki/Fifth-generation_programming_language
it says what right there
>It turns out that, given a set of constraints defining a particular problem, deriving an efficient algorithm to solve it is a very difficult problem in itself. This crucial step cannot yet be automated and still requires the insight of a human programmer.
>Go
type response2 struct {
Page int `json:"page"`
Fruits []string `json:"fruits"`
}
Rust is shit but you can stop talking
literally reads as it is compared to Rust examples above
its not even funny to compare based Go
>Go
>Easy to read and immediately understandable
>Rust
>Cryptic, overly complicated, syntax only a mentally ill schizo can understand
If you are arguing in favor of Rust… just lmao
Literally what is bad about this?
backticks
also moronic way to do json unmarshaling
backticks are standard in javascript for template literals, I believe python uses them too but that might be deprecated I dont remember
literally nobody uses backticks for regular strings its not ambiguous at all
Based go devs making common patterns like json serialization dead simple
>#[derive(Serialize, Deserialize)]
>Her language needs to use another language to derive features.
Why does it seem like Rust would be literally unusable without derive macros? You can't even implement the Copy trait without derive.
Your whole language depends on yet another language to do anything useful. Shit language design to be honest.
>You can't even implement the Copy trait without derive.
You can, just no one does because derive is easier.
I had to look this up, because I was under the impression you couldn't.
>impl Copy for MyStruct { }
Somehow the result is even worse than using derive. You leave it empty... and compiler magic happens?
Yeah I can see why no one does that.
That's just does what derive does. You can, AFAIK, implement custom copy and clone logic there if you need/want to.
>pub trait Copy: Clone { }
I think both of you meant "implement Clone", because you can't implement Copy, there is no logic there that has to be implemented.
It's there to enable compiler magic.
You leave it empty because Copy is trivial for a struct whose members are all Copy. If they're not then you have to do it yourself.
how is this even remotely ambiguous
you have to be a nocoder theres no way
I get you complain because it uses ` to enclose tags, but look at the rust example.
It's not enclosed, it's just a single ` straight outta fricking nowhere. I hope it's rare, my first time seeing it, but goddamn why
>I hope it's rare
>40 years of C and this is what we have to show for?
C was a mistake.
Language designers should be thinking about how to make an abstract syntax tree easy to grog and manipulate instead of how to best pretend that you can use traditional math notation to write computer programs.
They are, see https://www.lamdu.org or https://hazel.org and similar projects (from non-research stuff possibly coming to Unison at some point). It's just going to take 100 years for us to get there because MUH TEXT FILES BETTER.
>40 years of C and this is what we have to show for?
Pascal has been there all along everything else is just solutionism.
>Pascal
Based. Computing would be in a much better place if everyone listened to Niklaus Wirth. Instead we ended up with the corpo trash that is C.
> corpo trash
we're not really talking about corpo trash yet with C, more like universities before they regressed into mental masturbation academia
>C
>Developed by Bell Labs
>Bell Labs, the research arm of Ma Bell
homie, are you high? C is peak corpo trash.
Not corpo trash. C isn't owned by a globohomosexual company.
> are you high?
yes, but also, don't see how this is makes C corpo trash. I doubt you have any idea what the design process was for C, or how many people were actually involved with that.
Now implement it in Zig
cniles are seething that they can't have safe zero cost abstractions
Can you show the asm that the compiler outputs for this? I totally believe it's zero cost, it'll just help some of the C users in this thread see how cool your language is.
generic function don't output asm, dumb moron.
Hello Satan, as it turns out when you use a function it will in fact generate asm. All you need to do is throw in any other function that calls it.
>generic function don't output asm
I knew rustroons were dumb, but not THIS dumb.
Don't you know what fricking monomorphization is?
kek
relevant: https://youtu.be/Wz0H8HFkI9U?si=q8uaX6a0Fv-2zs2k
This is by far the worst youtube video, what a homosexual. I couldn't even sit through 10 minutes without skipping ahead by 30 seconds every 5 seconds
I skipped far enough ahead, the last line I heard him say before I closed the video is "this article is ignoring the hype factor [of rust]"
What a fricking dumbass, why did you (You) me with this shit. No one on IQfy is this moronic.
well I wanted to link the the article itself but its paywalled now so this is the next best thing
I linked it because the article mentions the assembly produced by c++ versus rust and why c++ wins in that arena
Im literally arguing in your favor you moron
frick you, die
>I'm on your side bro!
>I'm on your SIIIIIIIIIDEEEEEEEE!!!!
I don't care, I don't like most rust users because they're moronic, and I don't like you because you're moronic.
If you were more intelligent, you'd understand that the only "side" you can have is your own.
>t. 14 year old who cant even sit through a youtube video
yeah you are very intelligent
>this looks like an interesting article
>LOOP:
>posts on twitter
>reads chat
>reads 2 sentences
>goto LOOP
Yeah totally, I'm the moron for not sitting through it and just mashing right arrow. I should have just sat there and watched a guy go about his daily routine in front of 300 people live.
youre seething
you're*
>video reacting to 5 min total
>react video 40min total
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
>play video
>pause video
>screeching voice
I have no idea how zoomers watch this and think that they used their time effectively. At least I know that being here at IQfy is the worst use of my time.
You can do lists like
(a b c)
Simple as.
HOW DOES THE COMPUTOR KNOW
It is translated to machine instructions, only because people in the past who built computers didn't know lisp yet.
forgot the quote 🙁
That's a submission for an obfuscated code contest....RIGHT?!?!
you dont really need to use all of that stuff. you can use rust like C with a borrow checker if you really wanted to.
You could just do a for loop, m8
This. Obsessing over chaining combinators is moron behavior. Loops are perfectly readable and there's really no reason to prefer chaining combinators over a simple loop over an basic iterator.
nocoders
What a ridiculous syntax. Is this something that one would typically write or just a moronic example for the sake of an argument?
Lifetimes denoted with the ' are necessary even for simple code, because the compiler cannot solve the lifetime of variables.
Don't know much else.
Anytime you need to create complex iterators you're going to get into shit like this. Anything async is far worse.
that code got C++ bros like pic
>where the void pointer at?
>I don't understand
More like I don’t understand why I would torture myself with this for nothing.
>waaaahhhh the entire world should cater to my Black personbaby understanding of things, I should never be outside my Cnile Safe Space
The number one thing a software developer is expected to do is learn and not be afraid of new constructs, tools, situations, etc. You are the opposite.
even if it fricks up everything and goes against sanity and reason and productivity and creativity?
I'm sure the assembly is very clean, you should show it off.
still haven't seen a response to this yet
You won’t get one. Trannies are innately cowards.
>My trivial program has an obvious output
Oh wow. Who would have guessed.
trivial Rust program doesn't have an obvious output, who would have guessed?
https://godbolt.org/z/Gjd19Tz58
>-O
Here's a comparison without.
Rust does overflow checking when optimizations are disabled, dumb moron
Sucks for rust. I don't see how that's my problem.
What is the output when you call a function such as
Just paste it in there, add an fn test() and call it from test
Rust:
https://godbolt.org/z/6ohrjqW6P
C:
https://godbolt.org/z/6hE41YMW5
Probably some very unidiomatic C, but that's about as close as I can get to making something similar. IMO, not a huge amount in them, but I am surprised at how badly the C code gets optimized. The rust code just looks like it's moving around the stack to get at the mov, and imul, which is largely what you'd expect.
>TL;DR: there's no (real) difference between the outputs.
-O0 in C is the most basic 1 pass you can imagine.
It seems that rust has no way to disable minor optimizations, which is an interesting choice. I'd say the closest equivilant would be clang -O1 because they both use LLVM then.
Still, we're talking about more than add(a, b), I asked for a sample like the one picture he posted mentioning "zero cost abstractions"
I would simply like to see these zero-costs. To be 100% honest with no lies or doubt, I totally honestly for sure believe him when he says zero-cost
It'd just really show up some C people if he showed the ASM
If you pass -O1 in the C example it cleans up quite a bit, but I thought we were just compiling with no optimizations? Anyway the ASM that gets produced is still no different. The only real difference I can see is unwinding in Rust. Anyway, I'm not going to reproduce some of the larger rust examples in C (I don't even want to reproduce them in Rust tbh) to compare them. As far as I'm concerned I've show that you can use abstractions in Rust that produces largely similar ASM. Some bits are qualitatively different, but the action is the same.
Rust doesn't seem to have a "no optimizations but no overflow check"
If there is one, I'd be interested to see, but as it stands that's probably the closest you could get.
> tweak compiler, llvm generates obvious output
great, we're reinventing C now. let's try this next
meant
>cnile does an UB
Syntactic diabetes.
Go-like languages will be the future
meanwhile cniles use linked lists and segfault all over the place
ffff embedded engineers, constrained systems? fricking cniles cniles cniles ahh cniles embrace javascript ctards ahh rust rust rust cniles cniles cniles
why is there an amogus in the trait name
because Rust allows Unicode identifiers and this trait is sussy.
extremely cursed
>'
>'
> A FRICKING '
Rust has all the power of Haskell minus the moronic shit.
In Haskell this is just
class Applicative f where
pure :: a -> f a
TBF in Rust you have two kinds (because lifetimes), so a more fair comparison would've been linear Haskell. Still looks immeasurably better:
class Applicative f where
pure :: a %1 -> f a
(<*>) :: f (a %1 -> b) %1 -> f a %1 -> f b
I'm not familiar with Linear Haskell, but that does look like Rust lifetimes but neater. I'll look into this.
/dsart/ - daily seething about Rust thread
Trannies have no future or legacy which is why they have an affinity for this. They are selfish in all aspects.
KNR4K!!! IT'S A SIGN!
This is why I gave up on being a coder. This shit is moronic. Algorithms can sure be hard as hell and require divine intellect to create them, but then the reality of programming is:
>spend your time dealing with confusing code
>spend your time making sure your code works on 10+ different standards/100000+s different hardwares
>spend time making sure your code works on different browsers
>ad infinitum
no thanks, I make better use of my time learning other sciences. Then I just have to figure out how to break nature's code, rather than deal with fresh newly invented human-made code every year
>GUIDE guess what! New coding paradigm engine/framework and language!
>Time to throw away all you spent learning in the past 5 years!
>It does the exact same job, but differently!
>NEW THING!!
>NEW THING!!
jesus christ
The thing is virtually all non-meme, non-esoteric languages are quite similar to each other, so unless you're a total moron changing from one programming language to another is just getting used to a different dialect in a language. Annoying at first but you get used to it pretty quickly.
>I make better use of my time learning other sciences. Then I just have to figure out how to break nature's code, rather than deal with fresh newly invented human-made code every year
All sciences are by definition "human-made". Math, diagrams, weird latin/greek-derived names are all human-made ways to describe concepts that you'll have to learn anyway. I'd argue that even in the other sciences the concepts change almost as frequently as in coding but it's not as obvious because other sciences doing active research don't instantly post the changes to their paradigms on the Internet in easily digestible form for the public
BURN THE HERUSTIC!
KILL THE CRAB!
PURGE THE TROON!
ITT: nocoders seething
cniles wish they had even a fraction of Rust's power.
best thing: this is absolutely zero cost. amazing, innit?
frick, screenshot is ruined by web 2.0
Just typed this in, generated worst ASM I've ever seen.
No I won't post it, I dare you to prove me wrong.
Cool what does it do though?
nothing
c-cope!!~ c-c-c-c-cope! cnile!!! ahh yes cnile cnile cnile ahh cnile NNGHHHHHHHH cnile rust rust traits rust rust borrow check rust safety
>his command line argument parsing library doesn't have a zero cost TypedValueParserFactory
how do you even justify getting more than 10 bucks per hour? might as well program orders into the cash register at mcdonald's.
Rust is so fricking ugly holy shit. More colons than c++. At least with the majority of languages you can jump in and read it and get the gist of it. With rust it's what the frick is a
<Black person::f.std::iterable::buttfrick
.->{...unpack}.return()
'->fG::gayot<map.zf.hr.qr "Black personhomosexual" [y.unpack(return)]
::&'myballs<u64><T>>{
cum, n, i, g}
where::troony().cuts.dick.off<i4>
)
};::unpack()
>ERROR: didn't arbitrarily add .unwrap() to ignore this error
It would have crashed anyway if this broke, so now I'm just saying "if you're crashing, please crash"
I thought this was real Rust code for a second
with a few macros it is
I lost 6943883730 brain cells reading this shit.
you never had any to begin with, Cnile babby
come back to me when your programming knowledge progresses past your first semester toy language
> cniles cniles cniles ahh cniles ngghhhhhhh cniles c-c-c-cnile!
congratulations on your second year bachelors informatics (you're basically a programming god now). keep cramming more features into your language and see if it outlives C.
Cnile is mad
> cope
when you realize your operating system and the majority of your userspace you use to write braindead messages is written in C
please defend this design
javascript and python are very readable but they get hate here. Why are compiled languages like this always so unreadable?
Rust syntax choices are mixed bag: some are good, some fine and some bad.
Also I am not sure what exactly I am looking at. Is this some official rust lang source? If not , what's the merit of this screenshot? That someone writes a verbose code?
I write prettier Rust in my small console applications and you can make this pretty easily with few imports and different formating.
So what exactly you want me to defend here?!
Rust has the worst syntax of any popular language, C, C++, and Java are pretty readable and you should be familiar with them if youre going to pursue a career as a dev
most modern languages syntax is derived from those three
in terms of Python level readability, Julia is the most readable compiled language Id say (literally the same syntax as Python)
go is also quite readable
You can literally read it, reft to right, top to bottom
>but I don't know what it meeeeans
Learn rust then. Do you expect to know dutch because you know some other germanic language?
>All of that type masturbation for just two fields in a struct definition
I'm sorry, but that's unreadable... and don't even try to justify it by saying that whoever wrote this is moronic.
I've seen this kind of Rust code in production before, only rustroons can read this shit.
Do I have to take daily estrogen to be able to read this kind of type-level vomit?
it's some optimized library code, who the frick cares?
>who the frick cares?
Yeah who cares about readable, maintainable code, right?
Are rustees "optimizing" libraries for unreadability now?
Because there's no way that troonlicions code is optimized for performance.
Have you seen how printf is implemented? Some things just are messy.
write(2)
You don't have to implement printf in unreadable, unmaintainable troonlicious code.
Cniles are also not immune from this.
"It's unreadable therefore it is optimized" is the most moronic logic I've ever seen in compsci.
>masturbation
dont you mean meanstruation tho
All languages are so ugly except for C and JS.
I had more fun programming in VHDL than rust.
Such shit language. If I ever need to write rust, I will just feed my c/c++ to an AI and tell it to translate.
if you think that shit is unreadable, you have not seen typescript type declarations for complex data structures
i mean, that's entirely on you for using a microshit product to barely wrangle the mess that's javascript
nah, typescript actually fixes javascript in many ways, but its type system is like a butter knife with a button, if you press the button by accident you blown the frick up
typescript is for wankers, it´s just javascript with a different syntax, because there is people out there who want to monopolyze everything, so they created this crap on top of js, just to call it their own.
>typescript
lucky
powershell with their modern segregation of services makes syntax impossible. every time it doesn't work it's a syntax error
Most disgusting syntax ever. I'm puzzled how someone would even want to spend an hour with this freak of a language
Low T level.
Rust is all the hype now because of the blockchains. But it is evidently a very dotty language.
that code made throw up in my mouth. Why is the syntax so ugly?
Genuinely impressive that they managed to make something uglier than c++. The only thing they actually improved is having a package manager
The first impression I got from rust years ago was when I opened a youtube video of some talk, this was a bit before it became big. I think it was the main dev speaking or some other sort of woman. What I noticed was that a legit question about the language's design was dismissed quickly, not elaborated, and then the next question was about merch, t-shirts, the dev suddenly brighten up and talked enthusiastically about it
Why would the programmer write it like this? It's not good practice to make everything cryptic.
>I know a different programming language therefore I am entitled to understand rust without learning rust
Filtered and gatekept
No lazy people allowed
if you can't read this, you might as well end it now because ChatGPT can read this with ease.
get replaced by matrix multiplications, cnile.
The C I wrote 10-12 years ago as a university freshman is more readable than this
METHINKS YALL SOME GODDAMN moronS FOR THINKING THIS RUST ISN'T MAD DECENT.
AIEWNUHXFAIEURXNGHMISMERUHSXOISMHRSFIUMHRFOSMEHRFOIUMHEROIUFHMSRFUMHFIUERHMFIOUM
only a moron would write something this unmaintainable doe
rust is trash but you're a dishonest homosexual