Open Source Software Community - it's about ethics in Code of Conducts

[Null]

I assume Lunduke is just trolling because otherwise I am forced to assume he's a retard

 

[analrapist]

assume he's a retard

A useful idiot, yes. He's trying to create a right-wing niche for himself in tech. You'd have a better notion than most how that tends to work out.

 

[Mikoyan]

why does matthew "the cucked" prince think a botnet can completely take cf down?

In theory it might be able to. Lately people have amassed some very large botnets that researchers in the field think have not been used to their full capacity other than maybe some random test attacks.

In related news, data I've seen about yesterday showed that during the outage the nuisance 'booter' ddos volume dropped to almost nothing because most of the booter sites use Cloudflare. lol, I say, lmao even.

 

[i440BX]

I assume Lunduke is just trolling because otherwise I am forced to assume he's a retard

He is more of a typical "boomer". I wouldn't consider him dumb, since he has some background working in the industry, but I agree that I would rather blame jeet code here.

 

[aout]

The Cloudflare outage was caused by Rust.
View attachment 8188536
Source, Archive
It failed in the exact way that Linus said it would if it was ever integrated into the Linux kernel and why it was unacceptable to ever rely on rust for anything critical—panic and crash to preserve "memory safety".
So half the internet was taken down because Rust's solution to memory safety is to just panic and crash.

why are cloudflare devs calling .unwrap() without checking it first lol

 

[White Peach]

Rust gives you so many ways to unwrap safely that making a mistake here is like somehow getting yourself impaled in a mcdonalds playspace. This has nothing to do with the language. This is just lazy and niggerlicious code that someone had to jump through a safety barrier to write, and then deploy.

Rust can never fail, only you can fail Rust.

 

[aout]

Rust can never fail, only you can fail Rust.

rust can fail its just shilled too hard as "the best programming language ever" by people with massive egos

 

[General Zoider]

Rust's solution to memory safety is to just panic and crash.

sounds like a certain class of programmers who like to wear socks.

on a serious note tho why in the fuck did they not do a bounds check either inside of that function or the one calling it. If you know something needs to be less than or equal to 60 clamp or throw an error to the client in a nondestructive way.

 

[moocow]

this perception will remain forever just like how people still think java is horrendously slow

Any time somebody bellyaches that Java is slow, I point them to Minecraft Java Edition (which is so fast even on low-end hardware it has a built-in option to limit the framerate to 60 FPS or less) and Songs of Syx (a city builder/empire simulator that can easily handle populations of thousands of individually-rendered and simulated citizens, also maintaining 60 FPS even with thousands of them on-screen at a time -- and we're talking animated 2D graphics, not Dorf Fortress ASCII here).

Rust can never fail, only you can fail Rust.

"The Titanic is unsinkable; only an iceberg could hurt it!"

Never assume a tool cannot fail. That's the best way to hear God laugh.

 

[Flaming Dumpster]

YOU JUST ADD AN ERROR HANDLER IT IS THE VERY FIRST THING YOU LEARN IN RUST

This shit where it sets the return value to Err rather than actually throwing exceptions is gay retarded bullshit and Rust is a faggot language. C# wins again. Even Python handles this better.

 

[SR Latch]

why are cloudflare devs calling .unwrap() without checking it first lol

Because they assumed Rust is a perfectly safe language and they don't need to be careful. I do not recall the name of the concept, but I have heard of a paradox in violent sports like rugby - the more protection players wear, the worse injuries they experience, because they rely on protection too much and take worse risks.

 

[Null]

This shit where it sets the return value to Err rather than actually throwing exceptions is gay retarded bullshit and Rust is a faggot language. C# wins again. Even Python handles this better.

Either<Fuck You,Nigger>

 

[Creative Username]

on a serious note tho why in the fuck did they not do a bounds check either inside of that function or the one calling it. If you know something needs to be less than or equal to 60 clamp or throw an error to the client in a nondestructive way.

they probably got a bit inattentive thinking that their language's compiler will always catch bad errors and its runtime system will always do the right thing with bounds checking
until it didn't

I point them to Minecraft Java Edition (which is so fast even on low-end hardware it has a built-in option to limit the framerate to 60 FPS or less)

actually minecraft java edition is one of those things that convinces people that java is slow
the real problem is that it has always fucking sucked at using the gpu properly, but people are not very prone to understanding the nuances behind why their game is chugging

This shit where it sets the return value to Err rather than actually throwing exceptions is gay retarded bullshit and Rust is a faggot language. C# wins again. Even Python handles this better.

sometimes you really do need the specific kind of nonlocal control flow that exceptions provide
when you don't have it, you need to do very entertaining things to express it which involve 40 phd dissertations like when haskell niggers do seemingly-simple things to any data structure more messy than a linked list

 

[moocow]

actually minecraft java edition is one of those things that convinces people that java is slow

lol wow people are stupid.

>start new world
>hit [F3] for debug info
>FPS is easily 120+ even on shitty hardware
>DAMN THIS SURE IS SLOW LOL

And that's not even getting into OptiFine or the other optimizers Fabric uses that replace the renderer with better alternatives.

 

[Creative Username]

lol wow people are stupid.

>start new world
>hit [F3] for debug info
>FPS is easily 120+ even on shitty hardware
>DAMN THIS SURE IS SLOW LOL

And that's not even getting into OptiFine or the other optimizers Fabric uses that replace the renderer with better alternatives.

idk what kind of bizarre alternate reality you stepped out of, but in this universe an ancient integrated graphics craptop will shit itself violently running minecraft 1.8 with the render distance turned up above 3 chunks

 

[Zeftax]

lol wow people are stupid.

I have vivid memories of playing this game on sub 10 fps with the shittiest settings possible a few years ago, stalker. Your gaslighting won't work, child. Enjoy bedrock edition.

 

[HildegardOrgonAkkumulator]

The Cloudflare outage was caused by Rust.

KIWIFLARE IS WRITTEN IN RUST

 

[Kendall Motor Oil]

Did they seriously not have .feature_names.len() >; 200 check or even automated testing for this?

A single line could've avoided this and a second line could've more gracefully handled the error.
.append_with_names(&self.config.feature_names)?;

It's also amazing they don't have automated testing to catch this.

 

[Outer Space Traveller]

The Cloudflare outage was caused by Rust.
View attachment 8188536
Source, Archive
It failed in the exact way that Linus said it would if it was ever integrated into the Linux kernel and why it was unacceptable to ever rely on rust for anything critical—panic and crash to preserve "memory safety".
So half the internet was taken down because Rust's solution to memory safety is to just panic and crash.

So it wasn't just poos shitting on the servers? Trannies and poos working together. A nightmare.

 

[mentally retarded user]

Go has better error handling.