>throw an exception
>willfully not catch it
>it's the language's fault

why do nocoders have such strong opinions on programming languages? what do they gain?

>>107260688

>>107170768

>>107260688
Same reasons why nocoders who criticize C++ for non-issues like uncaught exceptions terminating the program go ahead and .unwrap() in production, lol.

>>107261241
anyone with a single brain cell already bans exceptions in c++ code bases to begin with.
anyone with two working brain cells doesn't use c++ at all.
if you want to talk about c++ in this context, you can talk about how they add types like "optional" that are as useless as a pointer, while providing a facade of type safety. lmao.

>>107261337
Stay on topic and explain why exceptions are enabled in Rust in a "serious" production server.

>>107261357
what do you think "exceptions in rust" mean?

>>107261380
Something that should be banned from any important infrastructure.

>>107260928
schizo rust troon

>>107260649
If by "going stronger than ever" you mean "going to leak your private data to everyone on the internet" then sure
https://en.wikipedia.org/wiki/Heartbleed
https://en.wikipedia.org/wiki/Cloudbleed

File: 2.png (214 KB, 528x385)

214 KB PNG

>>107260688
They'd rather talk about programming than actually do it.

>>107261406
you don't know what "exception" means. and we go back to >>107260688

>>107260662
Worse
>put in a static limit of 200 features
>decide that the program should exit if it goes over
>feed over 200 features to the program
>the program detects it went over it's feature limit
>it exits
>it's the language's fault

>>107261645
Now tell me I also don't know what .eh_personality means.

>>107261618
>look I'm COOODING I'm COODING so hard *crashes the internet*

>>107260662
>purposefully name it something else than conventional wisdom
>surprise pikachu face when people don't use it as intended
yes, it IS a rust problem.

>>107261666
you don't know what an "exception" is in the context of type systems.
better?
you also don't know what .eh_personality (as an implementation detail) means if you're the retard who wrote:
>Something that should be banned from any important infrastructure.

>>107260649
>>.unwrap()
>>KABOOOOM!!
Rust is memory safe, not Pajeet safe.

>>107261817
it was needless to state that you don't know, will never know, and will never have the chance to know if you know or don't know. but thank you for sharing anyway.

Rust devs owe me money for the Cloudflare downtime

>>107260662
>use memory after freeing it
>its the languages fault

>>107260928
>DARPA project shilled by the NSA tells you that YOU are the zoggie
lmao

>>107261727
This. I'm reading /g/ all day. unwrap() is some sort of throw that can't be catch()? I don't speak rust.

File: screenshot.jpg (199 KB, 778x468)

199 KB JPG

>>107262375
Rust panic is a shitty version of C++ exception that cannot be caught in a sensible way.

>>107262390
Ok, I am a brainlet, but languages should usually atempt to be readable by someone who is not a professional with years of experience on every footgun of the language. For example, I never used PHP, but heard it has some fotguns around arrays being hashmaps, but I can generally follow along a simple example.

I literally can not follow along that pic and have any idea on what segfaults on there.

>>107262454
Segmentation fault is a signal on Linux, any process can be sent one.

>>107262390
Seems stupid and dangerous.
Why doesn't someone make a language that doesn't have this massive flaw?

>>107262483
Seems like too much effort, we could just use C with some rules.

>>107262390
Rust turns error handling into either 1. returns in a special type or 2. hard crash, with the latter one being the lazy thing to do when you assume the error can never happen and just want to ignore it
To be fair, this was shilled as the "better" way to handle errors many years ago, not just for rust, but in every hip new languages... eh, errors are just hard

>>107262390
You can catch unwinding panics
https://doc.rust-lang.org/stable/std/panic/fn.catch_unwind.html

>>107262454
Rust is a very ugly language and horrid to work with.
You indeed can't spot wtf it is doing unless you are fluid in the Rust specifications.... but there are no specifications, the reference is the Rust compiler, and that compiler is written in C++.
So basically, in order to be a good Rust developer you first have to read lots of C++ code.

It is crazy.

>>107262499
>It is not recommended to use this function for a general try/catch mechanism.
>>107262495
Yeah, I know, aborting in my fizzbuzz level toys is what I do aswell, but I'm not cloudflare.

>>107262375
Unwrap can be catched. They just didn't catch it.
>>107262512
What the fuck are you talking about? Nobody learns languages by reading the formal specifications for them. Lmao

>>107261727
True, it should have been called FromMaybe or FromJust

>>107262375
No, it's saying give me what's inside the container or abort the program if it's an error

>>107262454
>Ok, I am a brainlet, but languages should usually atempt to be readable by someone who is not a professional with years of experience on every footgun of the language
C and C++ are even less readable by non-experts

>>107262495
The
>just-crash-lol
trend got started by people who wanted to roleplay as superior to
>just try...catch it and continue with some default values

Jumping on trends, when its about programming, is so stupid.
For many years i was oblivious to it and didn't even know that this is a thing, i notice that new code had different patterns more likely, but only later discovered that there is a whole industry based on shilling new paradigms.

The dangerous thing about this is that you turn your brain off. Rather than thinking what you actually want, you do X because Y said that it is good.

>>107262529
I did read the C99 specification.
In fact, it was the simplest way of learning it.

File: good morning.jpg (392 KB, 841x1244)

392 KB JPG

>>107262567
>Anon learns about society we live in.

>>107260688
>NOOOOOOO IF YOU DON'T LIKE RUST YOU'RE A TRANSPH- I MEAN NOCODER!

>>107262541
>C and C++ are even less readable by non-experts
Sometimes a post is so dumb that you stare at it in awe and decide not to reply to it, because words can't possibly describe what just happened.

https://en.wikipedia.org/wiki/List_of_C-family_programming_languages

>>107262599
My thoughts reading your post and non sequitur link

>>107261357
Because unwinding generally produces more graceful exit than a process abort.

>>107260662
>when rust is misused it's the user's fault
>when any other language is misused it's the language's fault
ywnbaw btw

>>107262592
Unless you follow learn2code youtube videos or bootcamps you rarely get into contact with the trend-shilling.

File: 1763514631151131.png (104 KB, 803x480)

104 KB PNG

>>107262541
Short of the recent Python push, C/C++/Java/Javascript and other C-likes were what was taught in introductory classes for years, so one would have some familiarity with it. Sure, enough to follow along >>107262390 (but not to spot the error), but not nearly enough to follow along picrel.

File: .gif (14 KB, 220x220)

14 KB GIF

>>107262613
>now now guys, listen, we had a major global outage, we wasted your time okay, you're still with me? Well, it happened more gracefully than usual.

>>107262617
What should a program in your dream language do if it is fed an invalid config?

>>107262626
Update rollback is not a responsibility of a reverse proxy. The proxy should inform about the error and exit. It's watchdog's responsibility to rollback system to the last working configuration.

>>107262618
good thing that 99% of people totally don't follow learn2code youtube videos or bootcamps

>>107262390
what the fuck, why did this seg fault
what clown ass language they got going on over there

lrn2zig

>>107262390
>four replies to a retard with a fake picrel

>>107262638
>now now guys, again, we understand, we lost you millions of dollars, but... it was our watchdog's fault ok? Same nocoders that caused this rustranny rewrite to crash, are responsible for the watchdog too, but it's not their fault at all. It's... it's da choods, da C, da memory unsafety.

File: screenshot.jpg (168 KB, 1366x768)

168 KB JPG

>>107262655
Haha, yeah, totally fake.
I wonder if Rust would've prevented this segfault.

Why bother with Rust then?
It is better to use C++ then.

If they want a trully safe language, then they should do like javascript:
if error -> do nothing

In a dev enviroment, it should work normally, throw errors, close the application etc...
But then they could enable a flag in production, that when an error happens, it does nothing and just send the error to a log, but the program keeps running forever.

>>107262645
Here's a more funny thing: you can have a rare bug in Rust that causes a real segfault once, and Rust code will keep executing until it happens again.

>>107262706
That wouldn't change anything. There would still be an outage, just without error messages.
The sane thing is to have exceptions and occasionally even catch them. Ofc as usual this is more of a testing issues than anything else. Which arguably rust makes worse with its "safe by default" mentality.

lmao, i'm reading some of the rust docs.

instead of throw_exception_something()

it is panic("you hurt muh feelings")

>PANIC
>PANIC
>PANIC
>PANIC

What a gayass name for error or exception.

>>107262663
>it was our watchdog's fault
Yes

>rewrite to crash
Nginx also crashes on invalid config

>>107262681
kek
/g/eets deserve being made fun of this way tbf

File: 00s.jpg (160 KB, 500x333)

160 KB JPG

>>107262751
What if we just used nginx and never had an outage?

>>107262773
They could even have a good rationale for why "panic" makes sense, but when the entire industry call something an "exception", you actually need a better rationale for CHANGING what everybody expects something be called. Otherwise you get INTERCAL's "come from": being contrarian for no reason.

Nobody is talking about the real issue of why that unwrap ran into the error in the first place. They preallocated a fixed size buffer for the features for performance, but that doesn't mean that the computer physically wouldn't have had enough memory to store them.
They said that the feature file "doubled in size". Does that really sound like something that would OOM the whole machine? The machine is presumably using a lot of ram for other stuff too, so less than a 2x spike.
The real issue here is them being retarded enough to use a static fixed-size buffer instead of a growable one. Avoiding allocations is great, but you get the same performance increase by using a normal growable buffer with and preallocating.
It would have been trivial to do in any language, but in Rust it's even more trivial because of the implicit destructors.
>>107262773
It's a very common word for it. Google "kernel panic".

>>107262622
what is this color scheme everyone uses for rust samples?

>>107262751
It's amazing how they screw it, instead of having proper structured error handling they have verbose pattern matching and unwrap. If you have a good error propagation using sum types you can even force the user to always check for errors by using some kind of annotation in the trowing function.

File: cs.png (209 KB, 2024x736)

209 KB PNG

>>107262821
who's everyone?

>>107262816
Not just that, but the standard practice for Rust based web frameworks is that you have a custom panic handler that simply returns a 5xx error code (along with logging the backtrace) when something goes wrong with a worker thread. Then you restart the thread and let the program continue if everything else looks good. You don't let panics crash the entire program like this.

So not only did Cloudflare ignore good systems programming practices, but they also ignored Rust specific web practices.

C++: cloudbleed
Rust: downtime

File: Russia is Nigeria with snow.jpg (245 KB, 1366x768)

245 KB JPG

>>107262454
>>107262483
>>107262645
Because the Nigerian with snow wrote "pkill -SEGV" in another window.

>>107260649
Not even close
https://en.wikipedia.org/wiki/Cloudbleed

>>107263003
>how many cycles?
>doesn't do

pkill ... ; date

for more precision on the left side

>>107263039
>this bug leaked credentials and shit
<check out what got leaked
<actually, it was nothing, no victim known

>>107263079
my date command doesn't work because i am on Ubuntu and they switched to rust written uutils

>>107262853
You need to unwrap values in Rust for a huge number of things. The Rust team decided to make unwrap an easy solution, where if unwrap fails, it ends up sending a panic and killing the program.

This is a huge design flaw, created by the strictness of Rust. The idea would be that unwrap always requests a default value in case of failure, or that data types in Rust have a default value.

But between avoiding creating a more complex type system, adding hidden control flow, and simply wanting to avoid so many compiler complaints, they decided that if unwrap fails, they kill the program.

Rust code is full of unwraps for simple code, even chaining multiple unwraps in a single line of code or causing C code to end up importing structures or functions with unwraps.

But even accessing vectors or arrays by index is a covert unwrap, so Rust is riddled with unwraps, which is why Rust advocates try to do damage control over the misuse of the language. Unwrap is like sweeping trash under the rug in the case of Rust.

Rust's idea of exceptions is to mimic Haskell's monads, but they need to spam unwraps with no default value and kill the program in case of failure. Haskell programmers will just laugh at calling exit(0) in the most basic and commonly used definition of accessing the value of a monad.

>>107263123
What is

date -r

even supposed to do? Recursively dating the mother, then the daughter, etc?

>>107263145
NTA
>You need to unwrap values in Rust for a huge number of things
Not really. I find myself using unwrap very rarely in my code.

>The idea would be that unwrap always requests a default value in case of failure, or that data types in Rust have a default value
This is what Java does and they consider it huge mistake.

Consider the cloudflare example. What should happen if your program can't load config file? Use default config? And then what, do whatever random thing was in the defaults and put an entire system into invalid state?

The correct behavior is to crash and let the continuous delivery system rollback to previous working version.

>Rust code is full of unwraps for simple code
Post your code and I will show you how to get rig of unwraps.
Spamming unwraps is a sign of inexperienced programmer.

File: file.png (5 KB, 161x147)

5 KB PNG

this shit is like php's mysql_escape_string levels of retardation

File: file.png (140 KB, 1613x982)

140 KB PNG

>>107263145
>This is a huge design flaw, created by the strictness of Rust. The idea would be that unwrap always requests a default value in case of failure, or that data types in Rust have a default value.
Rust has unwrap_or() and unwrap_or_default() which do exactly what you just said. Anyone who reads the docs for unwrap() literally cannot avoid being aware of the existence of those other functions, because they're right below, less than half a page away.

>>107263250
Elaborate

>>107263234
>uhh, hey look over there, java bad or something
nice deflection but your dick still won't grow back

>>107263277
So, let's consider the cloudflare example. What should happen if your program can't load config file? Use default config? And then what, do whatever random thing was in the defaults and put an entire system into invalid state?

>>107263079
It's not my picture. It's from >>107262767. Shills (who are mostly from Russia or India) keep lying about Rust and blaming it on the Rust language, saying it "segfaulted" when it's really because he sent a SEGV to the process from another window! Gee, no wonder it got a segmentation fault! C programmers are really that retarded.

>>107263297
>It's not my picture
Kek. So you are reposting random image as an argument without even knowing what is going on there. Just because it aligns with your narrative.

Nocoders are real plague on /g/

>>107263284
>let's consider my head fantasy
No, let's consider the example from the real world where it caused billions in damage

also rust has the defaulting version of that fuction as well
also please tell me where java returns "default" value for anything exactly because of the top of my head I can't remember that being a thing. In fact java has checked exceptions in my apis that make it impossible to NOT do something about it.

>>107263276
in PHP there used to be like 3-4 different escape_string functions, in the pic rust is doing the same retardation with unwrap, which was the function that cloudflare fucked up. iirc its common knowledge to not use unwrap but to instead use unreal_or_else and handle the errors but yeah.

Who would win:
>Largest state backed surveilance monopoly in the history of the mankind
>One.unwrapy() boy

>>107263321
>head fantasy
Cloudflare outage happened yesterday
https://blog.cloudflare.com/18-november-2025-outage/

So, what should they proxy do when they feed it with invalid config? Use default config? And then what, do whatever random thing was in the defaults and put an entire system into invalid state?

>>107263355
Why would the default be invalid?

>>107263323
>in PHP there used to be like 3-4 different escape_string functions, in the pic rust is doing the same retardation with unwrap
It is common that languages have multiple functions that have similar name but do different things. I know what these functions in Rust do, but I don't know PHP. How are they related and what alternative do you suggest?

>>107263317
>So you are reposting random image as an argument
No, it's the other part of >>107262390 explaining why that process suddenly died with a "segmentation fault" even though it makes no sense. The anti-Rust shill killed the process himself by sending it a SEGV signal. The Rust receives the SEGV and it kills the process, but that's why it shows "segmentation fault" and looks like it crashes. It didn't originate from the Rust code, it came from him being retarded and writing "pkill -SEGV" to try to trick people into thinking the Rust code segfaulted.

>>107260649
>language claims to be memory safe; not "will never have a bug ever"-proof
>/g/ still goes full-on meltie over it.
lol
lmao even

>>107263384
nigga just read the docs for rust and you'd see why what they are doing is retarded.

>>107263378
Well, what should be the default config for a reverse proxy? Do not proxy anything? Proxy 8080 to 80?
Whatever that is, it probably won't be what they want.

>>107263399
>nigga just read the docs for rust and you'd see why what they are doing is retarded.
I know what unwraps do. I don't know PHP and what would be the better alternative. That's why I am asking you.

>>107260662
All I hear is cope

File: 1733981034186.png (191 KB, 720x651)

191 KB PNG

How much money do glowfags waste in this shill campaign? There are AI bots coping for Rust in half of the threads about cloudflare.

I will never use rust. It is a disgusting language.

>>107260688
>t. professional unemployed rust poaster

>>107263234
>>107263259
The point that unwraps without a default value and crashes the program in case of failure should never have existed as a method available to users, only as an internal API.

It's a terrible design idea, and it only highlights the problem to say that a function used in any language example code or internet forum response should never, ever be used in production code.
Just don't put a gun in the toolbox and then say, “A real Rust programmer would never use the gun.”

And the reason it exists is how tedious Rust programming would be if you always had to put a default value in unwrap or had to adapt the type system to give a default response for any value.

I am an Austrian from Austria, i am fully Z and hate ZOG and BTFO Rust troons whereever i see them.
One of the reasons is that rust is officially shilled by the mulatto military (the same "people" who made Ada written software crash when crossing timezones). They literally have money dedicated to advertise this broken language.

Rust troons deserve the same fate as Mykola who rushed with his German Leopard 2A6 into the minefields.

Why didn't they just keep using nginx?
It worked for over fifteen years for them, so why try to replace it?

>>107263473
>And the reason it exists is how tedious Rust programming would be
That's not true, Rust has ? operator that makes returning errors up effortless. It even makes it easy to clearly see where which error is handled. It lets you handle it without clutter.
But well, why would I want to handle something that entire internet depends on not crashing? It was never about security.

>>107263400
What happened probably wasn't what they wanted either.

>>107260649
I thought the entire point is that C++ allows idiots to make mistakes, and that Rust is designed to shield idiots from making mistakes.
Is this just a classic case of the world making a better idiot to surpass any attempts at idiot-proofing?

File: 1761337322106.png (191 KB, 720x651)

191 KB PNG

>the language did what it was instructed to do, chud!
using this argument just makes you look retarded

>>107263530
Because it's not written in Rust. And Rust is safer. Which means it protects you from crashing.

>>107263553
No, it's just a classic rustroon backpedaling.
>>107263562
Trvke, this argument is reserved for C and unsafe to ever use in Rust context.

>>107263553
>Rust is designed to shield idiots from making mistakes
Even if that's not the case, that's the idea that gets on to nocoder managers.

t. nocode middle manager lerning2code because fuck middle management, not lerning2rust btw

>>107263553
It prevented a memory bug. The same thing happens with unhandled exceptions (or whatever the language calls them) in any language.

>>107263473
>The point that unwraps without a default value
What should be the default value when you are writing a reverse proxy and it gets fed an invalid config?

>It's a terrible design idea,
Let's hear your idea. What should be the behavior of that proxy?

>>107263530
Nginx would also refuse to start if you feed it invalid config.

>>107263535
? Returns the result tuple in case of error, and needs to implement the trait from.
unwrap returns the data type and panics in case of error, and does not need to implement any trait.
You need unwrap as a method that returns the result of the tuple 100% of the time, but in case of failure, it kills the program.

>>107263542
Yup. What they wanted is valid config and rollback otherwise. None of these things were responsibility of that Rust code.

File: iykyk.gif (18 KB, 225x225)

18 KB GIF

>>107263670
So implement those traits, lazy nigger. This isn't a fizzbuzz, this is a cloudflare proxy in 330 datacenters around entire earth, you stupid nigger monkey.

>>107263553
>I thought the entire point is that C++ allows idiots to make mistakes, and that Rust is designed to shield idiots from making mistakes.
Not from any mistakes, from undefined behavior.
Having your program gracefully exit instead of entering invalid state is the desirable behavior.
This is also the same thing that nginx does.

>>107263572
>Which means it protects you from crashing.
[citation needed]

What Rust protects you from is for example cloudbleed. Panic is nothing in comparison to memory exposure.

>>107263729
Oh really? Then we don't need rust then. It doesn't do anything useful

>>107263831
>It doesn't do anything useful
[citation needed]

>>107263653
Code >>107262622
features_value has an invalid value.

Further down, an if statement verifies that not having a value is an error and sends the error code for file not found.

The programmer created code where they think that reading a file would never fail, and the Rust language exposes as a basic function whether a result is false. It kills the process.

In the case of Rust's if let code, it would be a good alternative if the file does not exist. It sends an error code.

>>107263872
>It kills the process.
What else should the proxy do if it got an invalid config?

>>107263871
The assertion that it does something useful is what needs to be cited. C and C++ have had functioning codebases for decades. Vibecoding a solution in rust and claiming that it somehow makes electrons "safer" is what needs to be defended.

>>107263919
>C and C++ have had functioning codebases for decades.
"Functioning" means they still have bugs from decades ago because the exploits are still "functioning."

>>107263901
Send an error message. Specify the program function and the type of invalid configuration error. The name and path of the configuration. Then the Cloudflare team finds the error in minutes instead of searching for hours because the program just crashed.

>>107262821
solarized

>>107263941
As opposed to half written codebases like the coreutils rewritten in rust that have 10 test cases for coverage and the recent cloudflare issue which caused an outage.

>>107262335
>>107262617
Please show me what the Cloudflare internal documents say should happen when an incorrect config is passed, so we will see who's at fault

File: image2.png (66 KB, 1200x742)

66 KB PNG

>>107263919
>The assertion that it does something useful is what needs to be cited.
>claiming that it somehow makes electrons "safer" is what needs to be defended.
Sure
https://security.googleblog.com/2025/11/rust-in-android-move-fast-fix-things.html?m=1

>>107263503
>Z is not ZOG
lmao

>>107260649
>blog post with AI image at the top
is this the ickiest of icks or what?

>>107263953
>Specify the program function and the type of invalid configuration error. The name and path of the configuration.
That's what unwrap does. It's literally an assert, it gives you precise line number and stack trace.

>>107263670
>tuple
learn some basics brother

>>107264031
the internal cloudflare documents say that in case of an error in the rust code, all systems globally should crash and be unrecoverable for >3 hours.

>>107264148
yep, you got btfod!

>>107264148
To be fair, I have to commend their retarded faith in Rust to the point where they did not have an automatic rollback in case of a crash.

>.unwrap()

>>107264171
They never said they were didn't had rollback because they believed in Rust or that they can't ever mess up configs or whatever.

thread 'main' **panicked** at 'called `Option::unwrap()` on a `None` value', src/main.rs:133:42
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

**STATUS:** 4chan Thread **TERMINATED** ABNORMALLY.

**REASON:** Unhandled **Rust Panic** at the instruction pointer (IP) corresponding to a `.unwrap()` call in reply #133.

**ERROR_DETAILS:**
* **Exception Class:** `std::panic::PanicInfo`
* **Payload:** 'called `Option::unwrap()` on a `None` value'
* **Source:** `src/main.rs:133:42`

>>107264264
If they had proper security in place in case of bugs like this, only like <1000 people would've gotten a weird internal error followed by normal load after a single refresh.

>>107264104
"Memory safety" is an ephemeral term. Claims about the "number of vulnerabilities" buried in a largely closed source codebase indicates testing workflow, not language merit.

>>107264421
>Claims about the "number of vulnerabilities" buried in a largely closed source codebase indicates testing workflow, not language merit.
>We adopted Rust for its security and are seeing a 1000x reduction in memory safety vulnerability density compared to Android’s C and C++ code. But the biggest surprise was Rust's impact on software delivery. With Rust changes having a 4x lower rollback rate and spending 25% less time in code review, the safer path is now also the faster one.

>>107264288
That's true. There was nothing wrong with their Rust code, except maybe using unwrap instead of expect for more meaningful panic message.

>>107264131
>it's literally an assert
>but we call it something else
>what? you're confused? skill issue

>>107263473
>The point that unwraps without a default value
So if you want your program to abort, you just can't? That's ridiculous. How do you manage to be even more safetycucked than Rust?

>>107264482
I've said I'm a millionaire. Now I am worth a million dollars. You are not allowed to audit me or tax me like I'm a millionaire

>>107264570
The last time i used abort() in C was.... never.
In the past days i learned that the safety-cucks using Rust abort() everything.

>>107264744
You're literally asking the language to remove options from you so you don't accidentally call a bad function. You're more safetycucked than any Rust tranny ever dreamed of being.

>>107260649
So what's the connection between Cloudflare and Rust?

File: 1754837610883153.jpg (38 KB, 512x411)

38 KB JPG

>>107260649
JavaScript doesn't have this problem

>>107263297
I will continue to shit on rust while pretending that Russian's shitpost is really how Rust behaves simply because it's funnier to me and there's NOTHING you can do about it.

>>107265204
Now that I think about it, pretending that I'm Russian makes it even funnier.

>>107265018
a cloudflare service called an an unsafe unwrap and panicked. how is that unclear? do you even program at all?

>>107262645
because the code he ran is different than the code executed

>>107265291
I've just been living under a rock. That's actually hilarious. They need to stop hiring friends and friends of friends instead of actually competent people.

>>107265399
Erm what the sigma chud, how can someone without friends to recommend them be competent?

>>107264806
Look, C programmers are smart enough to not use abort() outside of fringe debugging.
Rust troons are incompetent and dumb and are clearly not capable of handling such power... thats why they chose Rust to begin with, because they are incompetent and scared... so of course you have to take every single chance of fucking up away from them.

In a fair world, those incompetent idiots would work at McDonalds instead of rewriting critical software into Rust... but we aren't living in such a world.
We have to deal with what we have, and the low-IQ idiots need to be protected from themselves.

>>107260649
rust is not fit for high availability, period.

>>107265443
>those incompetent idiots would work at McDonalds
I'd rather have cloudflare outages than die of food poisoning on fateful day when I decided I wanted to mix my life up with some goyslop.