[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] [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


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


Rust is now consuming every FOSS project out of complete necessity - LLMs have proven that C/C++ are not suitable for production apps in the 202x future. CISA has even banned the usage of non-memory safe languages for newer government projects.
Cniles will still defend C as if there is some pride to completely fucking up and compromising your own software. Or that 20+ years of bandaid patches on top of C++ make it a 'good' programming language (20 ways to define an integer btw.) No, they're just hanging onto the old ways because they refuse to accept this new superior reality.
Rust was always the future. You lost.
>>
>>108804831
it's the opposite. with an llm in hand memory issues basically don't exist anymore. modern exploits are more involved and can be written as easily in rust as in c. the difference is llms have more experience with c, so they're more likely to point out the bug. all the other complaints people have about c - it's slow to write, it doesn't have enough fancy abstractions - are also made transparent by ai. using any other language at this point is just dumb.
>>
for me, it’s C/C++, but thanks for the recommendation OP, i hope rust can fill the gaping hole the doctors left for you
>>
>>108804904
>C/C++,
why do people use this term? they're very different languages with different use cases
>>
>>108804831
So rust will be where all the vibe coded slop is developed?
>>
>>108804831
Complete global oxidation
>>
>>108804831
It may be the future, but you will never be an actual woman. Not ever. You have stubble, a male skeleton and a goofy voice.
>>
>>108804831
I don't care anymore. Rust is forcefully shocked into everything despite rust software still showing the same vulnerabilities they promised rust would fix. The internet is being deanonymized to "protect children" while at the same time they are banning VPNs, because of course a child owns a credit card and can pay for a VPN unsupervised. People are unconditionally trusting autocomplete chatbots because they can hallucinate confidently enough.

I give up, the psyops won. I'm not fighting for anything anymore, just tying to enjoy the rest of my life before inevitably dying in either the cull or the recolution
>>
>>108805056
jeet unis use a Visual Studio version (often from 20 years ago) to "teach" students "C/C++".
always remember that you're talking to the wintard students from these classes in rust threads as well as linux threads, as both are things that "scare" them. if a lot of what you read makes zero sense, and often the opposite of truth, that's why.
hopefully you're not a jeet yourself.
>>
>>108805737
>Rust is forcefully shocked into everything despite rust software still showing the same vulnerabilities they promised rust would fix.
"Android adopted Rust in 2019 to fix the vast majority of the security issues. At the time, Android version 10 had 223 known memory safety bugs. The current Android version has 85 known memory safety issues, a 61.88% decrease. In December 2022, Google declared they had not seen a single memory safety vulnerability in Android’s Rust code, which made up approximately 21% of all new code."
"Wah wah everything is a psyop. It's JEWS and TRANNIES" Take your meds.
>>
>>108805767
https://blog.google/security/rust-in-android-move-fast-fix-things/
A more recent example from Google saying they've observed a 1000x decrease.
>>
File: 1777383588163231.jpg (366 KB, 1216x1376)
366 KB JPG
>>108804831
>CISA has even banned the usage of non-memory safe

rust user is not advanced user: No — CISA did not ban memory-unsafe languages. It and allied U.S. agencies have issued guidance strongly encouraging use of memory‑safe languages for new critical software and asking vendors to produce memory‑safety roadmaps (with target dates like 2026 for new systems), but this is advisory guidance and not a legal ban

beside:

Jen Easterly — appointed by President Joe Biden (confirmed by the Senate).
Paul M. Nakasone — appointed by President Joe Biden (confirmed by the Senate).
Chris Inglis — appointed by President Joe Biden (confirmed by the Senate).

it is a sleepy joe programming trait aka retarded
>>
>>108804831
I like Rust for many things, but it tries to be this universal language and achieves that by hiding lots of things from you.
I'd like a version of Zig/C/Rust, ie. as dead simple and monotonous as C/Zig, but with the destructive moves of Rust. I don't care about checked multithreading, that rarely exists in my line of work anyway.
Rust is just too complicated and too high-level for me
>>
>>108805830
>achieves that by hiding lots of things
what "things"?
>too high-level for me
define "high-level"
>>
>>108806215
mainly allocations. iterators, collections, all kinds of handles will transparently allocate some memory on creation and deallocate when dropped
And sure, many types can have an additional allocator argument, but not all, and also we're back to C++ with the easy thing to write being the wrong thing.
>high level
cmon, it's not that hard. the base-line is creating well-defined stack-variables with trivial fields and passing them to plain functions to associate further memory, transform them etc.
RAII, operator overloading/traits, async runtimes and all the rest are "higher-level" than that.
>>
>>108806289
>all kinds of handles will transparently allocate some memory on creation and deallocate when dropped
what is a "handle"?
>>
>>108805830
>I'd like a version of Zig/C/Rust, ie. as dead simple and monotonous as C/Zig, but with the destructive moves of Rust.
This shouldn't be too hard to implement
>>
>>108806450
alright, you(or the LLM you've spun up) are just posting in bad-faith then, noted.
>>108806502
Probably not, but I don't want to use some niche language nobody else uses. I'd never be able to convince my coworkers, especially not about some home-brewed internal compiler project. Adoption is legitimacy, and to me Zig isn't there yet, whereas Rust by now is.
>>
>>108804831
On the contrary, LLMs will make writing everything in C with zero external dependencies trivial. Reinventing the wheel isn't a problem when it takes under a minute and you get nearly instant compile times.
>>
>>108806803
>bad-faith
au contraire. i'm requesting clarifications instead of straight up calling you retarded.
we will get back to specifics comparing C and Rust. but first, what is a "handle"?
>>
>>108805749
you almost got away with this dropping off the front page before i saw that someone had accused me of being a jeet
as a matter of fact, rust is a turbojeet lang because it is an attempt to make systems programming look more like web
i dont care about any of this for the record, im a front end engineer so dealing with actual complicated stuff. i just like to laugh at rust for being such a (trans)parent attempt to “simplify” systems dev. ironically, the borrow checker is harder to understand and master than almost anything from C



[Advertise on 4chan]

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.