Thread 106525244

>When I tried to figure out what was going on, the language had changed since the last time somebody had posted a description! And so it took days to write a program which in other languages would take maybe five minutes!

Is this why most of the rust programmers are trannies? Because they like pain and suffering?

>i just couldn't grok the mechanisms that were required to do memory sagety in a program where memory wasn't even an issue
rust in a nutshell. it only becomes more good than harm if you're writing terrible code full of slow cache-unfriendly data structures and treating the heap like a scratch register.

>>106525244 (OP)
>so you should take all of this with a giant grain of salt.
I did. /thread

>>106525244 (OP)
>take all of this with a giant grain of salt
He knew he would be quoted by tribalist fags like OP

KEK you are talking about the ultimate cnile

one obvious thing about these astroturfing faggots is they truly believe words conjure reality. if they just say "rust is replacing C" enough times, they truly believe it will just manifest into reality

>>106526483
I doesn't even make sense. c is the language the OS is written in unless you literally make and get everyone on a new rust based OS nobody will care. Sure you can replace C++ or maybe C# in applications
As long as we are on linux and windows everyone has to know c anyway

>>106526456
Typical communist, trying to erase the past and diminish the old guard.

>>106525244 (OP)
>Xitter screenshot
>No link
>boomer says Incomprehensible gibberish or misquoted
Given how lead poisoned boomers are it could be true, but I'm going to call OP a faggot instead.

>>106525244 (OP)
They would be on suicide watch if they knew who Kernighan was

>>106526569
It doesn't matter what language Linux is written in. It has a stable and documented syscall ABI for every CPU it supports.
Windows is a different problem, but not really relevant because it's nonfree and full of AIDS.

>muh Bell Labs
https://www.youtube.com/watch?v=QTiAWZ1YfzI
there are countless good programmers in this world, but you will never bring them up because they work on problem domains you have never heard of using Python + Pandas or some other shit that you consider "inefficient"

>>106526780
I literally, factually, does matter. It's always going to be easier to use c code from c than from rust. Imagine the amount context switching you have to do anytime you want to use some library

>>106526780
>but not really relevant because it's nonfree and full of AIDS.
I just want you to know, this attitude you display is why no one wants to deal with the insufferable lintard community.

>>106526821
good, normies need to keep the fuck out or they will ruin linux like every single other thing under the sun they get invited to.

>>106525244 (OP)
I guess I'm just smarter than Brian Kernighan, the UNIX and C legend...

rustfags itt seething. Kernighan accomplished more in one day than you will in your entire life

>>106526802
This. The next decade of turing awards will go to zhangs researching AI in Python while the the only things rust troons will get is the darwin award when they 41% xemselves.

He's old and his brain can't learn new things. What's your excuse?

>>106525244 (OP)
The problem with c++ Is the lack of guides for nerdy adolescents

>>106528773
I don't see the point
it's just another dime a dozen llvm frontend

>>106526805
You don't need C at all for applications on Linux. The kernel is a black box that you interact with via syscalls, and those are always done via (inline) assembly.

>>106529066
rewriting an application from scratch in asm for every architecture?
based!

>>106529131
It's just the syscalls you dumb nigger. Very little code that takes no effort.

>>106525244 (OP)

https://lngnmn2.github.io/articles/kernigan-and-rust/

/thread

>>106529475
>seething so hard can't construct a single grammatically correct sentence free of typos
yep
this is the rust tranny experience these days

>>106529425
>takes no effort
>t. never went beyond fizzbuzz

>>106529475
This is AI, right? There's no way a real human is this inane?

>Objective-C, in the corner crying
After they tossed the shit in where it automatically did retain and release on your reference count everything was there
If it needed another method to access memory directly or use another method than reference counting to do the management I am sure you could easily modify it
Even adding in more restrictions to prevent being a total moron could be added

I think everyone was just asshurt that apple used it with iOS and Mac and by association the spergs couldn’t handle the heat

The open source community continually does this, instead of improving an existing tool they try to create a new one

>>106530198
Objective C doesn't have anything like the borrow checker and nobody would have used it if it did. It's just an ordinary ref counting system that C++ also has via smart pointers.

I like both C and Rust.
Also Mr. Kernighan is old, and he said to take what he says with a grain of salt.

>>106530198
>>106530218

objective-c is a dynamic language where you can swap implementations of classes and methods at runtime. cpp and rust can't do this

>>106529532
addi x10, x0, 0
addi x17, x0, 93
ecall

Wow, so hard!
If you spent less time shitposting and more time programming maybe you wouldn't be such an incompetent retard nigger.

>>106530498
now do this for aarch64 and riscv

if rustaceans would please consult this post

>>106530498
>no error handling
:m

>>106526742
^this is exactly what was happening. Thankfully, the DOGE cut the New Red Guard's funding (US AID), so hopefully this movement dies on the vine without our tax dollars to finance it.

https://en.m.wikipedia.org/wiki/Four_Olds

>>106530198
In a strange turn of events, the creator of Rust is now working on Swift, which Apple hopes will replace their Objective-C

>>106529509
>>106530125
>>106529475
I know Slavic shit posting when I see it.

>>106530550
hasn't been true for a long time
https://github.com/sunfishcode/mustang
>Mustang is a system for building programs built entirely in Rust, meaning they do not depend on any part of libc or crt1.o, and do not link in any C code.

>>106530701
>Mustang isn't about making anything safer, for the foreseeable future. The major libc implementations are extraordinarily well tested and mature. Mustang for its part is experimental and has lots of unsafe.
this is pottery

>>106530658
finns do that as well
you just can't tell if they're serious or joking seriously

>>106530821
>muh unsafe
sorry, I should have added trigger warning

>>106525244 (OP)
grok is this true

>>106530895
"grok" in old unix terms means "to understand something intuitively", it predates the twitter ai considerably.
if the twitter ai comes to mind first, perhaps it is you who is the zoomer

>>106530821
they have come full circle lmao

>>106531080
All those words and not one mention of "Stranger in a Strange Land". Illiterate millennial perhaps?

>>106531103
yep, i'll a millennial. never in my life have i heard of that book

>>106529475
What an asshole. Reminds me of them apples guy in Good Will Hunting

So all the bullshit in rust is just to avoid having too mutex when mutating shared state? What is this super common problem he describes about c and c++ data getting arbitrarily moved in memory?

>>106531179
He doesn't understand how the OS maps memory. There's the entire VMS layer he's unaware of. Stopped reading around there.

>>106529509
>seething so hard can't construct a single grammatically correct sentence
And that's why Larry Wall had the right idea.
Linguists should be making programming languages, not Computer Scientists.

boomers lived in an age where software was forced to be as fast as it can in order to do anything.
Rust is the perfect, "modern", antithesis of that era; A complacent, arrogant, slow, useless language trying to claim old ideas.
which is why most rightfully hate it. And the ones pretending to like it feel like they have to because it's the "future".

>>106531374
Why are things like ripgrep, fd, dust etc so much faster than the old utils then? If their improvements don't come from rust why not improve the older utils?

>>106531417
>Why are things like ripgrep, fd, dust etc so much faster than the old utils then?
LLVM progress.
Now the real question is, why are all these rust rewrites "blazingly fast", while the core compiler and build tools are so dogshit slow and bloated?

>>106531503
>LLVM progress.
Then where can I get some non-tranny versions of them?

>>106531512
maintain your own fork.

>literal monument of "getting shit done" basically says "I don't know how you could get anything done with this"
>rustroons flip their lid

Yup, sounds about right.

>>106529475
>esl tranny seethe screed
nobody cares, didn't read

>>106530331
>cpp and rust can't do this
struct {
int (*behavior)(void *, int, int);
} vtable;


struct {
vtable v;
} object

>>106531417
dust is in fact, slower than du
ripgrep and fd's speedups mostly come from multithreading, poor internationalization support (forced unicode), and file ignoring heuristics.
The file ignoring heuristics in particular, mean they can't ever replace the system versions.
uutils is trying to be actually POSIX compliant, and its slower than GNU, and still has shit locale support.

>>106531685
struct vtable {
behavior: fn(*mut (), i32, i32) -> i32
}

struct object {
v: vtable
}

>>106530331
Isn’t that what composition is all about?

>>106531703
>poor internationalization support (forced unicode)
retard

>>106531748
Er dependency injection, rather

>>106526483
It's a huge downside to social media bubbles, especially those enforced by community voting (and thumbs being put on the scale for preferred narratives). It's altered many people's way of thinking, impacting them in the world beyond computing.

>>106531417
>Why ripgrep so much faster
it's multithreaded and uses a non-POSIX regex engine
>why not improve the older utils
POSIX doesn't allow either improvement

>>106525244 (OP)
> caring what boomers think
If you care what Brian Kernighan thinks so much why don't you go join the IDF?

>>106532045
>If you care what Brian Kernighan thinks so much why don't you go join the IDF?
>your brain on rust

>>106531103
ignorant tryhard

>>106531703
>dust is in fact, slower than du
I use it on a HPC with hueg GPFS full of many tiny bioinformatics files. It's night and day between it and du.
I don't know what your use case is where it's slower.

>>106532006
Not for the core utilities sure, but there could still be C versions of them if their improvements aren't rust related, right?