>trending on GitHub
what an utterly faggy metric I bet you love getting pozzed too

what happens once the whole internet is gigaslopmaxxed?

File: file.png (410 KB, 554x554)

410 KB PNG

>>108849489
>sage
You must be new here. At least read the rules and don't behave like a newfag.
>>108849517
Picrel happens

9 out of 9 repos trending on GitHub are projects written by Claude

File: r-chamber.jpg (458 KB, 1244x750)

458 KB JPG

correctness cannot be achieved by introduction of an abstraction layer that "catches the error". correctness is achieved by a correct implementation.

a debug feature leftover becomes a crutch and cannot be seen as a higher value in comparison. its only good to babble about those pouring water from one cap to another.

File: 1747700405966271.png (500 KB, 1041x1998)

500 KB PNG

>>108849478
>3 out of 9 repos trending on GitHub are Rust projects
not here

>>108849478
Bun is only there because you gave it a star, see >>108849990

File: 1755090418030575.png (427 KB, 1280x720)

427 KB PNG

>>108849478
>>108849990
>all that agentslop
Fucking disgusting, no seriously I want to puke.
Also stars don't mean anything at this point, it's all astroturfing bots.

>>108850059
yeah I hate it, I hope all the AI LLM shit implodes

>>108850059
>Also stars don't mean anything at this point, it's all astroturfing bots.
yeah I know but I guess it showed up because starred it because it doesn't show up for me

File: file.png (51 KB, 1104x211)

51 KB PNG

>>108850059
>>108850067
>>108850082
>60k stars
>project doesn't even build
>contributors list is just AI slop or people prompt claude-code to add bloat. Dead internet theory.

>>108850119
>project doesn't even build
happens to the best of us, had this too when I moved a GitLab CI project to GitHub Actions shit

File: file.png (246 KB, 1091x969)

246 KB PNG

>>108850135
What's the point of having a pipeline if you do nothing with it? They don't even care lol. Claude probably just shoved down some .yml files and call it day.

>>108850142
okay wtf, I had like only 1 or 2 failed builds but this is really pathetic, every build failed lmao

>almost every project is ai slopped
the future of opensource is grim

>>108850234
Indeed, the current model is over, corporations finally did it they embraced and estinguished open source, although indirectly.

File: bf.png (103 KB, 2729x357)

103 KB PNG

>>108849478
can't even remember the last time i saw a new project that didn't have a slopped readme, let a lone code.
you go to crates.io and search for something, and the most amazing sounding libraries are all the same, less than 2 years old, ZERO dependants, and most laughably, broken CI and/or docs generation.
if you go to the docs.rs build log, you will always find a (picrel) in the last 5-10 minutes, and to no one's surprise, the sloppy crates almost always come from a github repo with Claude "contributions".
i think i mentioned this here months ago already, but as a rustacean, i'm thankful that the rust ecosystem managed to establish itself before the slop era. what's really "cooked" is any new language that will try to establish itself with an ecosystem of libraries now.
having strict no AI policy at the language implementation level (e.g. zig) is not going to help avoiding slop in the library space.
and let's not even talk about WIP langs that fully embraced slop in their design and implementation already.

File: c++ vs rust.jpg (137 KB, 1170x1136)

137 KB JPG

>>108850725
Ironically or not, Rust is the best language out there for vibeslopping.
Not only the errors are great, you have a strict compiler, the borrow checker and a lot of other stuff that languages like C++ simply don't have (or have worse alternatives).
Do you think Anthropic would be able to port Bun from Zig to Rust if it wasn't for how strict Rust is? Imagine having 1mil LOC of modern™ C++™, kek.
>what's really "cooked" is any new language that will try to establish itself with an ecosystem of libraries now
I don't really think that will happen. Rust is a good language for most use cases, from systems programming to front-end webshit. Rust is the endgame language for AI.
>having strict no AI policy at the language implementation level (e.g. zig) is not going to help avoiding slop in the library space
100% agree. Not to mention you can't really control if a patch is submitted using AI or not. You can just tell Claude to not make commits, then you sign it yourself and pretend you're not a Claude proxy submitting slop to Zig.
Big techs killed open source, there's no going back now.

>>108850725
New languages will simply adopt a different model, a large high quality standard library and an even larger auxiliary library, the former only developed by language developers the latter developed in a semi-closed way where you need to have a certain proven status in the community to contribute, the language will have no reliance on a package manager and/or open repositories though.
Basically it will be the opposite of everything Rust is.
But yeah open source failed, we need a new model, a new "GNU project" for the 21st century.
And yeah no AI policy will be adopted by whole ecosystems.
>i'm thankful that the rust ecosystem managed to establish itself before the slop era
Rust ecosystem was already v0.0.* "rewritten in Rust" slop long before AI though.

>>108849478
>And overnight Anthropic changed it to mean “probably vibe coded slop”.
I find it truly hard to believe trannies would be willing to or allow rust to be vibe coded

>>108850766
thank you for sharing your happy nocoder dreams with us.

>>108850806
Thank you for admitting you have no argument, I accept your concession.

>>108850765
Nobody has actually moved away from C or C++ though. If anything the new AI slop trend is going to bolster their popularity.

>>108849478
>“difficult to learn, slow to work with
this is the (mostly jeet) "filtered" perception of the language. the rust project worked very hard from day 1 to make it as easy as possible to learn and work with the language. and without that, it wouldn't have enjoyed the relatively wide adoption it managed in record time.

>>108849478
Yeah if it wasn't for corporations trying to vibecode their way out of hiring developers AI generated software would be considered a kind of lite malware, like adware.
>>108849489
kek

>>108850823
thank you for sharing your nocoder happy place with us.

>>108849478
its all garbage

File: 15657218551900.jpg (89 KB, 1024x776)

89 KB JPG

>>108850765
/g/ hates rust simply because /g/ is full of contrarian trannies who never coded anything.

anyone who ever worked with cpp commercially will immediately shill for rust or zig or whatever else is not cpp.

and no, C is even worse than cpp. only students can possibly claim c is a good language to work with.

>>108850849
new internet rule, anyone who first accuses another of being a "nocoder" is xerself a nocoder. Fuck off back to your goon cave with your programming socks.

File: 4111354193092118.png (127 KB, 309x354)

127 KB PNG

>>108850869
shut the fuck up, jeet. i personally knew 3 companies which \*transitioned\* from cpp to rust in the last 4 years or so.

>>108850861
Literally nobody wants to spend 90% of dev time arguing with your borrow checker or masturbating over algebraic types, which is why Rust is only getting popular cause of clankers.
C remains king.

File: 381110801919200922.png (434 KB, 976x866)

434 KB PNG

>>108850887
>arguing with your borrow checker
massive skill issue.

>>108850899
unsafe {
everything_actually_useful();
}

File: how a common lisp program(...).jpg (160 KB, 800x864)

160 KB JPG

>>108850823
>If anything the new AI slop trend is going to bolster their popularity
What the actual fuck? Have you tried using Claude or ChatGPT to code actual C++? I don't think so. Even for basic programs it fails miserably. Any static code analyzer will point that out. The code compiles because the compiler accepts any shit you type as long as it's valid syntax. That doesn't happen with Rust, thus Rust is widely used for vibeslopping.
>>108850835
>this is the (mostly jeet) "filtered" perception of the language
The only language that filters jeets is Lisp. We had the European Lisp Symposium and there was only white men. Not a single brown jeet there.
>>108850881
We're currently migrating our legacy load balancer (C++) with an in-house Rust solution. I'm not in the squad, but it's happening. Most C++ systems here are being replaced by Rust and Ada.
>>108850910
I would say that's skill issue.

>>108850765
>Ironically or not, Rust is the best language out there for vibeslopping.
The reason why I hate the Rust obsession is because rustshitter use Rust for a bunch of applications where even regular ass scripting languages would be a lot simpler to read, write, and run too. It's literally programming language fanboyism because Rust is thought of as le cool new thing therefore le good.

>>108850940
I will never leave my beloved JavaScript

File: 2021-05-09-224237_1920x10(...).jpg (22 KB, 405x406)

22 KB JPG

>>108850910
>he doesn't even know how rust works
every filtered /g/ troon: the post

>>108850881
what are you doing?
when the village idiot shows up, you greet him and leave him alone in his happy place.

>>108850725
>i'm thankful that the rust ecosystem managed to establish itself before the slop era
That's massive cope right there also
>unironically calling yourself a rustacean
Christ

File: d99b7062befa5e0c43a6b71e4(...).png (135 KB, 377x346)

135 KB PNG

>>108850940
rust is the simplest language there is.

no using your javascript garbage or incomprehensible python shit that doesn't run is not easier than brainded portable assembly with some qol features. if your repo cannot be compiled/interpreted with a single command, reliably, fuck off.

>>108850926
>What the actual fuck? Have you tried using Claude or ChatGPT to code actual C++? I don't think so. Even for basic programs it fails miserably.
Skill issue

File: 1633025772494.png (1.41 MB, 1280x1024)

1.41 MB PNG

>>108850899
>>108850982
Rust will only be remembered as that language infested with trannies that supply-chain attacks simple and that makes aislop easy to produce at scale .
Nothing you might say will change this fact.

>>108849478
3/9 repos are trannies

>>108850987
rustacean:
>you can filter all the slop trivially and reliably with created<2025 && non_owner_dependants>2
/g/eet tard:
>OMG HOLY COPE

i guess i will come back in 5 hours when most jeets are asleep

>>108849478
Dunno, I always saw rust as "probably jeetcoded slop" since at least the 1.3 days or so.

>>108850765
Anthropic DID NOT SUCCEED In porting bun yet. Look at the code yourself to understand why.
It's obvious when code is ai slop because it's slop (the fact ai made it is immaterial in that argument).
But I generally agree with your post.

>>108850861
Rust is a terrible language for human writers. This is also why the first thing every serious rust project does is box all their types to avoid the borrow checker altogether.

>>108849977
Humans don't do correctness and thus stochastic parrots don't either. Cripples need crutches and we're all lame.

>>108851556
I love how all these deflection posts reveal exactly where the /g/eet behind each one of them got filtered lmao

>>108851609
Jeets will be majority of Rust users in a few months, jeets only use LLMs, Rust is best language for LLMs, simple as that.
Rust is going to be a indian language.

File: 1761457931377694.png (210 KB, 987x871)

210 KB PNG

>>108849478
>ruview
I thought this stuff was debunked, it's real after all?

>>108851572
you are lame, yes, the main reason is that you choose an ugly syntax (cannot blame, its the Zeitgiest of abbreviation) and a false premise of "safety". but now you know what correctness means.

>>108850993
struct A contains components B and C.
i create an object that contains a reference to B, which it needs to call somewhere later.
now i need to read the value of C, very easy in other languages

what happens next? no LLM answers btw

>>108851670
Idk, I'm still compiling webkit-gtk to check :')

>>108850993
>incomprehensible python
If your Python is incomprehensible you are doing it wrong.

>>108849478
>all ai slop

>>108849765
ts

>>108850119
my favorite example is pearpc emulator, the project had been abandoned for 10 years, the last year the author resurfaced and started to committing vibecoded slop into the repo as a result you can't build the executable anymore it's completely broken now and the author tries to convince you that

 
error: ld returned 1 exit status

is a successful build

https://github.com/sebastianbiallas/pearpc/issues/37

>>108851665
>retard thinks a rustacean can't trivially distinguish slop from idiomatic rust code
lmao
all slop spam has ZERO (non-slop) dependants btw.
whether it's jeets or the KKK behind the prompt, no one is consuming the slop. and no amount of "luddites btfo" spam threads, or "2 more weeks until rust is jeeted" (((e-celeb))) talking points will change that reality.

>>108851768
>i create an object
>object
lol

File: 1761381492290813.png (291 KB, 680x660)

291 KB PNG

>>108852079

const object = {
  booba: "the boobest",
  poopa: "imagine the smell",
}

>>108851002
>supply-chain attacks
provide examples

>>108852175
chrono_anchor, time_calibrator
rustdecimal
postgress, if-cfg, serd, oncecell, and lazystatic

>>108852197
what are those.
provide sources for incidents and impact (including number of dependants for each).

>>108852234
i can provide this johnson in your mouth

>>108851670
you knuckle dragging retards are still in denial about the true nature of wifi? kekaroo

Rust is a solution in search of a problem,

>>108852234
Are you perhaps clinically retarded?
Sorry, my mom taught me better. I shouldn't bully the mentally disabled.

>>108852242
>>108852291
to the gantry: this is how (((they))) react when caught in a lie

File: 2020-01-24-013511.jpg (12 KB, 330x253)

12 KB JPG

>>108851665
lel
>>108851665
>tl;dr
you sound mad, though

File: Screenshot_20260518_213811.png (113 KB, 924x969)

113 KB PNG

>>108852234
It's literally this easy:
https://chatgpt.com/share/6a0b5c6e-bcd0-8388-a0c9-2caf143cdc33
https://socket.dev/blog/5-malicious-rust-crates-posed-as-time-utilities-to-exfiltrate-env-files?utm_source=chatgpt.com
https://github.com/advisories/GHSA-77xj-rrh3-wx3v?utm_source=chatgpt.com
https://rustsec.org/advisories/RUSTSEC-2026-0031.html?utm_source=chatgpt.com
https://blog.rust-lang.org/2022/05/10/malicious-crate-rustdecimal/?utm_source=chatgpt.com
I can understand if you don't want to register there as that requires some sensitive data like phone iirc.

>>108852342
They *kvetched* hard because ALL these cases had ZERO dependants.
i.e. There was no "chain" in any of them lol.

There were also raising suspicions that, at least in some incidents,
the "security" companies who "discovered" these and reported them may
themselves have been involved, as a marketing tool for these companies:

>look at us finding stuff and sheet
>buy our consultancy and/or subscribe to our security API/AI/blablabla

Which is why rust devs decided to not publish dedicated blog posts about
such "incidents" anymore.

But there is more...

I have ears in the central (((entity))) pushing anti-Rust talking
points. They primarily target a subset of tech illiterates; those
who are retarded enough to not realize that they are in fact tech
illiterate. What makes this group ideal is that they would push
the talking points fervently and with full belief in their factuality.

The current focus is a Goebbels-style campaign pushing, or rather
sliding, an association between the Rust ecosystem and muh supply chain.
The goal is to make that association "factual" in the eyes of
the illiterate. Guess what word >>108851002 used ;);)

A previous focus was on making it out like Rust was particularly
susceptible to "trusting trust" attacks somehow. (((They))) didn't
know, or pretended to not know, that not all Rust tool-chains were
actually bootstrapped from the same compiler. In fact, many distros
bootstrapped rustc from mrustc. So a "trusting trust" attack would
have to have had originated in a C++ compiler lmao.
>>108852435
oh we have a new (victim!) lol. see ^^

>>108852597
Congrats on being tech illiterate but the board you were looking for was >>>/x/

>>108852616
"""
Whenever you get cornered, remember that "no u" is always a perfect distracter.
"""

File: 1453100027609.jpg (19 KB, 480x480)

19 KB JPG

>>108852175
We've been through this already in the other thread, compared to npm and pip the only reason cargo had less attacks until now is ONLY because Rust has been relatively irrelevant outside of certain tranny echochambers.
We will see more attacks on the Rust ecosystem in the near future as it gets adopted more and more to produce endless aislop.
Prepare your butthole Rustbro.
>>108852597
I use the word "fact" all the times, fucking schizo.

So yeah as said it will be remembered as "one of those languages that enabled supply chain attacks and aislop spam in the late 20's", sorry this makes you seethe but not my fault you're on wrong side of history.

>>108852673
>i was the same person pushing the same talking points in the other thread with made up "facts"
thanks

>>108852709
Rust fanboys need a daily beating, every day until you like it.

>>108852799
yes. your happy place is real. stay there.

>>108849478
All AI slop. I hate poojets so much

File: vaxry hates rust.png (365 KB, 512x512)

365 KB PNG

>>108852799
I don't think they would complain
>>108853033
AI was only possible because of the amount of open sores code out there.
Now AI comes back to completely destroy open sores.
That's poetic and ironic at the same time lol

>>108849478
Those are all AI crap. Bun is trending because its owned by anthropic and they rewrote the codebase from zig to rust with AI and the code is now 1 million lines and has many safety issues.

>>108851670
No? It's been proven multiple times now, last big story was last year

a reminder that not a single anti-rust concern troll has proved yet that they are not your average wintard:

lsof -p `pidof -S',' firefox` -Fn | grep -E '\.so(\b.*|$)'| while read l; do expr "$l" : "n\(.*\.so\).*"; done | sort -u

feel free to use that test when you see one of them waffling.

>>108849478
These projects have no real usecase at all

>>108852597
This is borderline schizo argumentation.
Supply chain shit is a legitimate high-risk attack vector in languages with good package managers so it's useful that people can't stop talking about it.

trending on github basically means the project got upvoted on some indian/chinese forum and they raided it with stars
unironically a bad look for a project

>>108854289
Tell that to the hiring manager.

>>108854272
you can't guarantee 100% safety in a supply chain with external dependencies.
locking/pinning dependencies (with dependency content hashing checked in with the code) reduces supply chain risks by A LOT.
applications (codebase with executables) written in rust have always been encouraged to check in Cargo.lock, and almost all of them do. since rust statically links code by default, this is the way 99.9% of people actually "consume" rust code.
there has been FAT ZERO actual supply chain attacks in the rust ecosystem with real impact (in the form of a SINGLE real dependant).

these things can all be right at the same time, and they indeed are since they are (actual) facts. but there has been a coordinated effort by (((some))) to pretend that rust is particularly susceptible to these attacks. when in reality, the risk is literally lower than your average distro.

and here the tech illiterate wintardation shows its head, usually with two arguments:
>distro maintainer/packagers check all code
not realizing that distro devs would be the ones laughing the loudest at this imagined reality.
>teh rust codebase has too many dependencies. should have a few only, with a "flat" dependency tree
to which you respond to the wintard by asking "it" to post >>108853846, only to get complete silence ;);)....until the next thread, where the same (((directive-following))) talking points are parroted again.

hope that helps

>>108850765
>Rust is a good language for most use cases
kek, you're a junior

>>108850926
>The only language that filters jeets is Lisp. We had the European Lisp Symposium and there was only white men. Not a single brown jeet there.
Based.
Although since you're a Rustacean, this means that even though you're based, you have a deep psychiatric disorder.

>the rusttroon is so mad he's sperging out at imaginary wintards even though the argument is for Linux style packaging
lmao at your life

>>108854553
>"the argument"
post

lsof -p `pidof -S',' firefox` -Fn | grep -E '\.so(\b.*|$)'| while read l; do expr "$l" : "n\(.*\.so\).*"; done | sort -u

>>108850765
can you link me AI slop Rust code? I want to see if it actually follows the coding standards they teach in the official TM book

>>108849478
I've noticed over the years since Rust was first introduced, your only consistently unchanging arguments are ideological.

You lot have been shifting goalposts since day one; you don't have an argument.

>>108855407
Checkout the bun codebase.

>>108853846
>>108854837
I'm not going to post it.
I know, I know
But basically I am just not going to post
HAHAHAH
>>108855861
So this is the future of aislopped rust, lmao

/g/ hate for Rust is based on emotional kneejerk reaction to trannies. If you described these features of Rust objectively in a neutral context most /g/tards would say this very promising and interesting.

For years "Built in Rust" was kind of a staple of at least some quality whether it be glazingly fast or something. Now if it's written in Rust, it's probably slop

>>108856653
No, you're falling for the same issue every outsider to 4chan has always faced when coming in at first. When people complain about irrelevant things like trannies, it is because all technical merits and demerits have already been extensively debated and the demerit side has won extensively. Thus, there is no point in further talking about it, as it's a cognitively complex conversation about a topic that is already settled. Thus, people say 'trannies' as shorthand.
The fact is, there are no extant rust programs in the wild despite the intense funding and social push for it. The only rust programs people know about are rewrite-it-in-rust effort. At best, you have that one dude trying out rust without any organization-wide buy-in, and deluded rust fanboys pretending the whole org must be using it. It's the reverse of that trick all startups do where they say 'trusted by X' where X is a big name when they managed to sell exactly 1 (non-business to boot) seat to a X employee, to accumulate social proof.

These devs https://loglog.games/blog/leaving-rust-gamedev/ might be pretty mediocre, but their experience report is exactly what everyone who's ever used rust and tried to write a serious program (in or outside games) has realized as well.

File: Screenshot_20260519_130449.png (159 KB, 327x776)

159 KB PNG

>>108856653
Rust was the language that hit Haskell community hard... Because shit ton of Haskellers switched to Rust. If Haskell were more popular here, it would get as much hate, for huge jew influence and trannies. They have judaism symbolism and naming embedded even in core language tooling like "cabal" being a build tool and that's not even mentioning Snoyberg with his Yesod, Keter and other Kabbalah references. Overall judaism in Haskell community gives me more of a "number theory schizo jews" vibe rather than "capitalist overlord jews" vibe. It reminds me of guys like Perelman and a movie called "Pi" (1998), directed by Darren Aronofsky.

>>108856668
facts

File: 1679782965018818.jpg (129 KB, 765x720)

129 KB JPG

>>108856653
/g/ has always been a C and Lisp fanclub, memory safety and strict algebraic types are reddit and hacker news territory, we like having fun programming here and Rust simply is not fun to program with.

>>108856687
> These devs https://loglog.games/blog/leaving-rust-gamedev/ might be pretty mediocre, but their experience report is exactly what everyone who's ever used rust and tried to write a serious program (in or outside games) has realized as well.
Nowadays everyone uses ECS in gamedev anyway, and when you use ECS, you don't have to deal with Rust's owneship/borrowing at all, because ECS maintains entity lifecycles on its own and everything you write is contained within the scope of a system which is just a function, which uses Entity type as safe pointer to let entities reference each other. Look at Bevy.

>>108856687
This is simply false at least when it comes to /g/. All the hoo haa about Rust on /g/ is centered around trannies. When you dig beyond that and just ask an average senior software dev about Rust they will say it is interesting.

>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," Google's Jeff Vander Stoep said. "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

>With roughly 5 million lines of Rust in the Android platform and one potential memory safety vulnerability found (and fixed pre-release), our estimated vulnerability density for Rust is 0.2 vuln per 1 million lines (MLOC).

>Our historical data for C and C++ shows a density of closer to 1,000 memory safety vulnerabilities per MLOC. Our Rust code is currently tracking at a density orders of magnitude lower: a more than 1000x reduction.

https://security.googleblog.com/2025/11/rust-in-android-move-fast-fix-things.html

https://thehackernews.com/2025/11/rust-adoption-drives-android-memory.html

/g/ insists to shift the focus of the discussion to trannies. The originatorss of Rust are straight white men and even the chud Eich who got booted from Mozilla for homophobia, was one of the foremost supports and early adopters of Rust. /g/ tranny hysteria overwrites this history for their narrative.

File: 1767718320274257.jpg (157 KB, 1200x675)

157 KB JPG

>>108856668
Best signs of good software are C and shell. Python and rust are probably the most vibecoded. Python is still somewhat ok since AI has a lot of data to work with, but rust is just bottom of the barrel slop. I mean your input data ise literally trannyware, what can you expect

Is there a more hated language than Rust?

>>108856772
The whole point of AI is that it generalizes to a significant extent. I vibecode DSLs with AI and ask it to write code in them. It does work well with big models. It does a great job of writing compilers in JS/TS even though most of its knowledge of relevant concepts could only come from compilers written in C and C++.

>>108856805
Believe it or not, there is a substantial amount of hate for C and especially C++. On /g/ though? No, there is no competition. Rust is by far the most hated. Go maybe is in second place for being hated on /g/, but far behind Rust.

>>108856808
Sure, but generalized data is worse than specific data. Anything you ask for in python it just stitches together human-written code 1:1. The more you deviate from the norm, the more hallucinations and errors.
>>108856818
Fucking hate C++ too. Object oriented is a meme.

>>108856805
Python is irrationally hated by a lot of people here, because they assume that the only way you use it is as a patchwork of bloated third party libs, but you can actually use it in a very efficient way by using only stdlib and dynamic libraries through ctypes.

>>108856808
LLMs are fine at translating stuff in custom DSL, it's kinda fun to do novel language design with a LLM cause you get to see how it would look and feel right away, but it's only good at the syntax level, at the semantic level it will make a lot of mistakes like making up stuff you didn't specify or changing the semantics of the language randomly.
If your DSL maps semantically to an existing language your experience might be better.

>>108856742
>didn't even read
lmao

>>108856751
It's pretty clear you're brand new to /g/. The fact you take what paid people with agendas on the internet say at face value is even more hilarious to me though.

>>108856860
>ctypes
>efficient
Opinion disregarded
>the absolute state of pyjeets
>even so much as implying in the first place that the problem is efficiency and not the absolute shitshow that is maintenance and deployment in pyndia

File: Screenshot_20260519_141938.png (157 KB, 725x865)

157 KB PNG

>>108856910
Okay, I did scroll a bit:
> A canonical example of this is Bevy's events, which are the go-to suggested solution for anything related to "my system needs to have 17 parameters to do its thing".
Idk if it's a new feature, but I personally solve this problem by using SystemParam. It allows to simply move those "17 parameters" into a struct as more of a syntactic sugar thing instead of introducing more complex event-based indirection. Works fine for me.

>>108857014
> This is a relatively simple example, but it is something one might want to write. And especially when implementing a new mechanic and testing things, it is something that you can just write. There is no maintainability to think about, I just want to do very simple things, and I want to do them in the place where they are supposed to happen. I don't want a MobHitEvent, because maybe there's 5 other things I may want to check the raycast against.
So basically this person complains that someone told him rapid prototyping thing he wants to write is not the most abstract and scalable enterprise EE tier solution, and that alone makes him so uncomfortable he doesn't want to use Bevy anymore. But the fun thing is that Bevy allows that style he wants to write. And it is more of a default and the most simple style, with events being more complex and secondary option. It's true there are some rare minor annoyances like:
> crash with a double borrow error if I'm accidentally inside queries with overlapping archetypes
But overall that sounds more like a burnout rant rather than actual foundational obstacles. It's still very usable and not bad at all. You could find as many or more issues in any other game engine or even game engine paradigm if you looked this hard.

>>108857086
I see you've never written code in your life and have no idea what bevy is or does lmao

>>108856751
lmao no. The guys in my office are all calling it a tranny lang, shit gets routinely mocked for being a garbage lang as well.

File: Screenshot_20260519_152906.png (186 KB, 1124x932)

186 KB PNG

>>108857172
I literally showed my code one post above, you retarded moron.

>>108856751
>thehackernews.com
>same retard (jeet or bot) adopting opposite positions within the same 48 hours
4jeet really likes fake discussion traffic, doesn't it?

>>108856805
by tech illiterates consuming zogtube and shitter, and sub-80 IQ jeets? no lang comes even close.

File: ab.png (71 KB, 677x806)

71 KB PNG

>>108857357
mid-code hints trigger me. and the fact that you don't make it clear that they are hints is even worse. the combination of using nvim-lsp-endhints, and giving hints fg/bg clolors that makes it clear they are not code, is indispensable for me (picrel).
someone one step above tech illiteracy may think rust doesn't have type inference, looking at your code ;)
---------
/g/eet anti-rustists are tech illiterates, and this is not used as an exaggeration. they are incapable of directly engaging with you with specific technical points outside of web search and LLM tardations.
i like how this person made fun of the retarded "unsafe greppers", together with the bun slop rewrite itself lol:
https://github.com/oven-sh/bun/pull/30759
(see the original un-modded out OP text)

people call Rust a tranny lang because they got filtered by it and their fragile egos can't handle it, so they lash out. it's that simple

>>108857357
Cry about it, nodev

>>108858140
Agreed, no lang comes even close to being so useless. Even brainfuck has more real-life uses than rust. Proof: there is no new rust software, only rewrite projects. Only 2 games made in rust and published, and they're both unplayable toys.

File: 1723800028052.png (30 KB, 915x915)

30 KB PNG

>gaymes
lol

>Rust programs are slow as hell because no one bothers to actually work with the borrow checker
>this means actually memory safe languages like Java, C# and Go should be used instead
>cargo is an npm tier dependency hell ecosystem, you're just waiting to get exploited if you use it
>if your code does anything worthwhile you will need to unsafe, making the use of Rust just another flavor of C++
>insane compile times, makes it impossible to use for game development
>the only good things about Rust are irrelevant in the grand scheme of things and are features that many other (nicer) languages also have (type system, pattern matching)
>no specification, only one (mystery binaries all the way) compiler

all in all I give it 0/10

>>108858690
thank you for sharing your happy place with us

>>108858933
thank you for your jeet input

>>108859113
thank you for your tranny reply

>>108858818
Wrong thread, manolo

>>108851768
#include <WinNT.h>
CONTAINING_RECORD(pB, struct A, B)->C

>>108850887
If you need to "argue with BC" 90% of time, then you're wrong probably 89% of time and simply don't understand why

>>108851768
If B was accessed in scope then you can split the borrow on A ie.
>ObjectThatContainsB::new(&a.b)
Allows you to still access a.c even when ObjectThatContainsB is in scope
>ObjectThatContainsB::new(&a)
does not

It's a very simple rule. BC evaluates functions independently to
>make sure every function call and struct creation is valid with their signature
>make sure the function as a whole is valid with it's own signature
So a function signature
> &'x A -> X<'x>
Gives you no information it doesn't reference the whole of A whatsoever. A borrow is an A borrow you can't say it's only a half.

>>108858818
games are the only valid use of computers apart from physics simulations (which are really a kind of game)

>>108849489
How do people still think popularity implies fitness in software?

>>108851572
There's lots more to programming than bounds checking on primitive arrays. If you can't handle such simple invariants you likely can't handle the significantly more complex ones a real application requires.

>>108851670
Lol. Xfinity literally advertizes this feature if you go into their app. They are quite proud of it.
Also, all of the "conspiracy theories" about WiFi and 5G are correct, but corpos worried people knowing would slow progress, so they pay Daily Show man on the TV to say 'people who think X are silly and dumb' so that midwits repeat it because they're desperately afraid of being seen as not smart.

I remember when Epstein's Island and the NSA spying on everyone was considered a conspiracy theory.

>>108856687
Tbh I like Rust as a Java/C++ replacement and as a way to help web devs stop writing electron shit. I just don't think it should be in the kernel or used for low level programming because it's not it's best usecase and often has to use a bunch of unsafe code or heavily wrap C code to make it work. Plus adding more languages I'd just more bloat. Zig seems like a much better (eventual) candidate for low level programming, and Odin is cool because it's Golang you can make GUI applications in easily and has no ties to Googlel. The problem is Rust enjoyer's want to kill C when their language is a C++ killer.

>>108862659
>all these words just to slip his meme as a real player
lol

>>108862659 (((me)))
Ignore the typos. They are not real and cannot hurt you.

>>108849478
I didn't even know Bun got rewritten in Rust. Oh well, back to not caring about it.

>>108862722
It's not actually rewritten in rust. An LLM was used to convert the code to compile in rust, sort of as a stunt.