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

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Guarantee this will or has already fizzled out, the only place you can host a functional version of this is GitGud or a private repo that won't shoah you for adding heretical words. Very cool idea though. Having a one-size-fits-all "nigger injector" would be a great way to prevent AIjeets from slopping you off.
There are other repos that contain words like 'nigger' in like `BAD_WORDS_LIST.txt`. It's just too tough for anyone to actually submit a PR with the word 'nigger' even when crossing all your anti-racism T's and dotting your globohomo I's. The self-censorship has become self-reinforcing even when it's objectively stupid.
 
Last edited:
Someone ran Miri (Rust's undefined behavior sanitizer) on the AI port of bun and immediately hit UB, since these retards seem to think transliterating zig into rust makes it magically more sound
1778973125995.png

Issue thread

Remember they have over 10,000 unaudited unsafe blocks, which is defined by the language to mean you are asserting something the compiler cannot verify has been audited by you.
1778972943614.png
 
Someone ran Miri (Rust's undefined behavior sanitizer) on the AI port of bun and immediately hit UB, since these retards seem to think transliterating zig into rust makes it magically more sound
View attachment 9016090
Issue thread

Remember they have over 10,000 unaudited unsafe blocks, which is defined by the language to mean you are asserting something the compiler cannot verify has been audited by you.
View attachment 9016080
I wonder what the zig code looked like for that, because im pretty sure zig has safety checks for that while the rust equivalent doesn't, because "unsafe" zig is safer than unsafe rust lol
 
I wonder what the zig code looked like for that, because im pretty sure zig has safety checks for that while the rust equivalent doesn't, because "unsafe" zig is safer than unsafe rust lol
Unsafe zig is safer than unsafe rust yes, in two ways:
1. Unsafe rust is allowed to make assumptions zig is not. Aliasing is an easy example.
2. Unsafe rust is expected to be defined for all safe codepaths that can reach it. This is a conventional requirement more than a technical one.

Bun probably violates the second case more than the first. Effectively they break the assumption which is normally present that you can just call whatever and not hit UB unless you write "unsafe {}", which will throw off AI tools and humans alike. If you can't make that assertion you're supposed to bubble the unsafe keyword to the caller until someone can, instead of what bun did which was just ignore it somewhere.
 
Someone ran Miri (Rust's undefined behavior sanitizer) on the AI port of bun and immediately hit UB, since these retards seem to think transliterating zig into rust makes it magically more sound
View attachment 9016090
Issue thread

Remember they have over 10,000 unaudited unsafe blocks, which is defined by the language to mean you are asserting something the compiler cannot verify has been audited by you.
View attachment 9016080
good read https://zackoverflow.dev/writing/unsafe-rust-vs-zig
 
The funniest thing that could possibly happen would be for the rewrite to work perfectly and be easier to maintain, therefore causing maximum zigger meltdown while simultaneously validating just throwing tokens at the problem until it's solved.
 
The funniest thing that could possibly happen would be for the rewrite to work perfectly and be easier to maintain, therefore causing maximum zigger meltdown while simultaneously validating just throwing tokens at the problem until it's solved.
I don't know, impossible miracles are rarely funny. At most people would be baffled that it worked, and suspecting that some trick is in play like paying a bunch of reclusive geniuses to do the rewrite and pretending it's AI. If an AI is actually capable of that intelligence, then it would mean that AI has literally reached the level of humin intelligence and insight and a skynet or AM situation is on the horizon. We'd be fucking lucking to get a Mrs. Davis that's helpful but misguided.
 
The funniest thing that could possibly happen would be for the rewrite to work perfectly and be easier to maintain, therefore causing maximum zigger meltdown while simultaneously validating just throwing tokens at the problem until it's solved.
There is absolutely zero chance for that.
They ended up with an enormous codebase that is ZIG but written in a tiny RUST subset, with unsafe everywhere.

It is like the grey-beard's saying "a good fortran programmer can write fortran66 in any language" but not as a joke but as a statement of fact.
They fucking willed that meme into being a reality.

This blob of code is 100% unmaintainable.
 
The funniest thing that could possibly happen would be for the rewrite to work perfectly and be easier to maintain, therefore causing maximum zigger meltdown while simultaneously validating just throwing tokens at the problem until it's solved.
won't happen. rust produces so much technical debt, it's not even a joke at this point.
My personal anecdote from my current job is that for a mere 10% of our codebase rust has a massive overhead when it comes to keep it up and running. every cadence is filled with crate upgrades, rustc upgrades, CVEs, we ship with CVEs on rust.
For the normal part of our codebase we only upgraded our build machine from win7 to win10 because rustc couldn't be installed and run there.
It's not a huge codebase, it's 400k-500k LoC, mostly normal code, some C++ and the rest as I said is rust.
There are parts in there that were last touched in 2015 and the never complain about anything. they build from winxp (yes we still have customers) to rhel6, AIX, solaris, dropped ubu16 last month but hey, I can fire up debian lenny and compile the normal code and the c++ code just fine.

I used to be a zigger up until 0.12. Now the language has lost its purpose of being a modern C. It's a clusterfuck of features just shoved in there.
Zig Creator Andrew Kelley 5-5 screenshot.png
fuck this purple haired faggot.

If an AI is actually capable of that intelligence
it's monkey work.
 

More info has been disclosed.

github said:
We are sharing additional details regarding our investigation into unauthorized access to GitHub's internal repositories. Yesterday we detected and contained a compromise of an employee device involving a poisoned VS Code extension. We removed the malicious extension version, isolated the endpoint, and began incident response immediately. Our current assessment is that the activity involved exfiltration of GitHub-internal repositories only. The attacker’s current claims of ~3,800 repositories are directionally consistent with our investigation so far. We moved quickly to reduce risk. Critical secrets were rotated yesterday and overnight with the highest-impact credentials prioritized first. We continue to analyze logs, validate secret rotation, and monitor for any follow-on activity. We will take additional action as the investigation warrants. We will publish a fuller report once the investigation is complete.
 
every cadence is filled with crate upgrades, rustc upgrades, CVEs, we ship with CVEs on rust.
For the normal part of our codebase we only upgraded our build machine from win7 to win10 because rustc couldn't be installed and run there.
I don't get it, routine dependency updates are not automated? Why tf were you using windows 7 (and windows in general) in 2026?
 
Back
Top Bottom