[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology

[Advertise on 4chan]


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: 1544729016111.png (492 KB, 1098x1126)
492 KB
492 KB PNG
https://github.com/google/security-research/security/advisories/GHSA-ccx2-w2r4-x649
Rust doesn't have this problem. Literally speaking, because it prevents buffer overflow in compile time.
Now watch how glowies flock to defend C(ve) lang.
>>
>>81050821
oh shut the fuck up already bruce
>>
>>81050821
>Linux kernel 4.19 and higher
I STAY WITH MY SLACKWARE
>>
>>81050838
dumb cnile
>>
>>81050821
>Rust doesn't have this problem.
Yeah but it does have a tranny problem so you should probably get to work on that ok
>>
>>81050838
based
>>
ohhh no we got too cocky bros
>>
File: 1616728914273.png (239 KB, 480x480)
239 KB
239 KB PNG
cnile trannies btfo again
>>
>>81050889
>No lambda, unreadable function pointer mess
>No monomorphism, inefficient void* tries to emulate runtime polymorphism.
>The latest C11 poorly emulates somewhat shittier version of C++98 "generics"
>No encapsulation, no modules, no standard dependency management mechanism
>Type unsafe pre-processor dependence
>Array decays
>No support for UTF-8 handling, the lead creators of C created UTF-8 themselves
>No type classes/OOP. Codebase clutters up with thousands of free functions. Devs have to end up implementing OOP anyways (see Linux)
>No RAII, no optional memory management, devs have to implement ref-counting anyways (see Linux)
>DRY violation
>No standard testing mechanism
>relies on pre-processor for conditional compilation/testing
>No mechanism to prevent double free, data race, invalid de-referencing
>No real language evolution because the standard committee boomers choking on their vitamin pill

Arguments against Rust:
>u trannie!
>but what abt ur dick hmm?
>u shill
>unsafe block?! omg rust is now c
>dilate hrt xDD
>he gay!!

It appears that Rust's superiority is creating massive butthurt.
>>
>>81050821
>if they are equipped with Bluetooth 5 chips and are in scanning mode.
That's gonna be a pretty small attack surface.
>>
Rust is actually looking better and better for performance code.
I'm not going to learn it, but it's a good thing to have out there.
>>
>>81050927
you may never be a real woman but you sure are starting to whine like one
>>
>>81050821
Rust code is always an eyesore.
>>
File: 1617615141314.png (376 KB, 420x420)
376 KB
376 KB PNG
>>81050963
>proving my point
>>
>>81050975
I don't have anything to say about rust
I'm talking about you personally making lists of complaints you have, like a woman
>>
>>81050821
So rust gives me an error if I try to copy an array of 255 size into an array of 100 size?

What if that's intentional, I only want the 100 first elements of an array like the string slice operation why is rust preventing me from doing this?
>>
>>81051006
>I don't have anything to say about rust
figures lmao
>>
>>81050927
it's unpleasant to use when the community is full of annoying people who go out of their way to be annoying
>>
>>81050821
>Rust doesn't have this problem.
>An issue was discovered in the smallvec crate before 0.6.14 and 1.x before 1.6.1 for Rust. There is a heap-based buffer overflow in SmallVec::insert_many.
>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-25900
Most of rust CVEs are memory, thread safety and pointer issues (not all of them are muh external library wrapper excuse, that heap overflow is 100% rust).
>https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=rust
Meanwhile on https://www.rust-lang.org/
>Rust’s rich type system and ownership model guarantee memory-safety and thread-safety — enabling you to eliminate many classes of bugs at compile-time.
>guarantee memory-safety and thread-safety
Gee, why would someone lie on the internet.
>but muh idiomatic rust and unsafe uses
It's almost as if you need unsafe features to do anything useful.
>>
ALL I WANT- 2 PASS C COMPILER WITHOUT RULE OF PREDEFFINATION
>>
>>81051006
>I don't have anything to say about rust
Basically every rust hater
>>
File: 1616503713718.gif (368 KB, 220x220)
368 KB
368 KB GIF
rust is a blessing, it took all the sjw, trannies and incompetent scums out of the c community.
https://www.youtube.com/watch?v=OUgKU2One5g
>>
>>81051086
>boomer cnile uses boomer memes
>>
>>81050821
>Rust doesn't have this problem
Neither does any other memelang people don't actually use for anything important.
>>
>>81051086
that was kind of funny
>>
>>81050927
I'd be surprised if more than two people on this board even program significantly in C.
The C discussion very rarely advances beyond K&R2 book recs and brainlet style threads.
>>
>>81051012
>So rust gives me an error if I try to copy an array of 255 size into an array of 100 size?
Why would you want to do that in C?
It's undefined behavior. Security considerations aside, an optimizing compiler is free to pretend that you copied only 100 elements, optimizing out any undefined operations.
This is incredibly basic C.
>>
>>81051980
Actually, I should say that once you introduce undefined behavior, a compiler is free to do anything it likes with your program, as far as the C standard is concerned. That could mean copying 100 elements, 0 elements, 2,000 elements, or even sending a dick pic to your printer.
>>
File: 1617665705716.jpg (38 KB, 960x540)
38 KB
38 KB JPG
>>81050821
>Linux trannies put bug into modern Linux versions by changing things for no reason... Again
>C BTFO!!! (continues spamming rust bait samefagging)
Not even the issue. Dumb spoiled trannies would have filled it full of nasty bugs even if it was in Lua. There are so many bugs like this caused by tr*on devs changing things that don't need changed that the loonix kernel will probably go back to being wickedly insecure, like windows. Why was the blootoot stack refactored in 4.19? It works just fine on my 4.0X machine and 2.8X machines. I'll tell you: tranny ego trips
>>
>>81050821
Windows doesn't have this problem
>>
>>81051086
amen, my project gets less gender related features request, no one ask me to change pronouns and to add a CoC anymore.
>>
For some reason I sill like C++11 more than Rust
>>
>>81050821
>Rust doesn't have this problem
Because nothing relevant is written in it?
>>
>>81052006
stop being ridiculous, undefined behavior means its not defined behavior, nothing more. It doesn't mean the devs behind that compiler will intentionally make your program send dick picks fucking moron. GNU projects have always been criticized by extending functionality that is not defined for years making their software incompatible with others.
>>
>>81052399
Buffer overflows... extending functionality.
Kill yourself, you fucking moron.
>>
>>81052399
>will intentionally make your program send dick picks fucking moron
No fucking shit, you socially clueless sperglord.
But the devs behind that compiler WILL exploit undefined behavior in many unexpected ways, leading to security vulnerabilities:

https://lwn.net/Articles/511259/
https://research.checkpoint.com/2020/optout-compiler-undefined-behavior-optimizations/
>>
>>81052984
arbitrary remote code execution is a feature
>>
>>81052137
nobody cares about your grep clone boomer
>>
Is Rust even viable for RCU-based subsystems? I would love it if we could use it to replace 80% of the garbage code in the kernel, but if everything depends on low-level internals, and a separation from those would entail significant performance regressions, then I don't really see it happening.
>>
File: 1595225635636.png (39 KB, 813x379)
39 KB
39 KB PNG
>>81051923
This, the C "programmers" on this board are dumbass LARPers who have never written a line of code, because if someone was going to write code for fun they sure as hell wouldn't be using C

it's actually remarkable just how stupid and ignorant the average cni/g/ger is
>>
>>81050821
everything c sucks but there is nothing else. Imagine asking a C programmer to name a modern book so a zoomer can start learning C and they give you a fucking book from 1979
>>
File: 1458046435769.jpg (62 KB, 421x421)
62 KB
62 KB JPG
>>81053286
>#include <regex.h>



Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.