- Joined
- Oct 19, 2023
for this specific problem, i find that the r7rs-small process environment procedures are a good (portable) option
no that's the name of a feature branch which can be merged into the primary branch called
totalniggerdeathOpen Source Software Community - it's about ethics in Code of Conducts
- Thread starter CrunkLord420
- Start date
-
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
- Joined
- Oct 20, 2019
mentally retarded user
kiwifarms.net
- Joined
- Aug 19, 2022
WTF.
Angie Wormwood
kiwifarms.net
- Joined
- Apr 29, 2021
I get why it's dumb but really, this seems like such a dumb thing to push. Who cares? Both words carry the same meaning. It has something to do with leader and subordinate, parent and child. Nothing to do with slavery. Sounds like someone upset because of their deep-seated desire to be someone's property.
If your code fails-open, you're not error checking. Of course it never crashed.
- Joined
- Nov 26, 2018
Why are they kink shaming?
- Joined
- Jan 29, 2021
Looking at SPARK, it does look like too much for programmers. This requires a way of thinking that filters out a lot of people. Most programmers don't even code with security in mind so verification conditions, preconditions, etc will be way out of their mental abilities. Then again, the people coding mission critical software should have the skill.
Most of the critics have never used it, used a free model in the web browser for a single file, or fed it difficult questions you normally wouldn't encounter when coding. They have a bias and you won't ever be able to change their minds.
It's great that it enables people to make things they would've never been able to but some people are just sour.
It's virtue signaling and forcing the newspeak on the people they hate. Big tech companies' HR departments were pushing this years ago since the HR women just care about pushing whatever the upper class tell them to.
Cognitive Decline
kiwifarms.net
- Joined
- Feb 7, 2021
I will just make my slaves call me "Main" now.
- Joined
- Jun 5, 2024
- Joined
- Oct 19, 2023
as in "sheeeit main i dont need to work on dem fields"?
- Joined
- Jan 29, 2024
Going back to this, while there's no conclusion to the story, LWN published this article (paid link stolen from HN) (archive) that summarizes the issue. One thing I don't think anyone here pointed out is that the developer pushing for Rust is also one of the main drivers (no archive, fuck Discourse) behind Ubuntu's uutils.
You may now resume Rust sperging.
Curious George Jetson
kiwifarms.net
- Joined
- Mar 26, 2024
No, seriously, keep these people AWAY from the core system utilities.
They literally have no idea what they're doing.
- Joined
- Apr 1, 2024
I wish they at least chose something to replace the coretutils that I though was worth a shit.
They're literally just taking them in porting them to an overall worse to deal with on a large scale, less portable, language, With us getting in return no real benefit. In fact, we get a language that by it's nature will if anything have code that is going to require more instructions to do the same thing they already did, even once the uutils are actually working fully.
If it wasn't for this exact type of rust port, for no reason, I think I would be overall in favor of rust. I've mentioned I do like some programs written in it. Ones where they were able to just start over from the perspective of modern multicore operating systems with large amounts of memory, so they got an actual speed improvement. Where it wouldn't be that practical to completely start over from scratch with multi-threading in mind for the older implementations. But when we are literally getting, for the tradeoffs rust has, the same thing. It's a net negative, even more so if they are relying on crates for their program. (I've literally had cargo pull in HUNDREDS of crates to build one package before, literally asking for a supply chain attack to fuck over their program.)
They're literally just taking them in porting them to an overall worse to deal with on a large scale, less portable, language, With us getting in return no real benefit. In fact, we get a language that by it's nature will if anything have code that is going to require more instructions to do the same thing they already did, even once the uutils are actually working fully.
If it wasn't for this exact type of rust port, for no reason, I think I would be overall in favor of rust. I've mentioned I do like some programs written in it. Ones where they were able to just start over from the perspective of modern multicore operating systems with large amounts of memory, so they got an actual speed improvement. Where it wouldn't be that practical to completely start over from scratch with multi-threading in mind for the older implementations. But when we are literally getting, for the tradeoffs rust has, the same thing. It's a net negative, even more so if they are relying on crates for their program. (I've literally had cargo pull in HUNDREDS of crates to build one package before, literally asking for a supply chain attack to fuck over their program.)
- Joined
- Jan 29, 2024
- Joined
- Feb 4, 2021
Yup I'm going xfce asap
- Joined
- Oct 19, 2023
i can't think of a particularly stellar reason to get rid of x11 support but knowing how janky and buggy kde shit is, they might be able to simplify shit by making the assumption that you will not be using x11
best case scenario kde becomes less of a shitshow, worst case scenario the people who have setups too fragile to adapt to the second better way to display graphics on a gnu system get cucked a little bit. all of you were probably using some tiling window manager you mostly wrote yourself so it doesn't matter much in that case
after all recently kwin-the-wayland-compositor has stopped being completely retarded on nvidia cards and it now works except for the usual unexplainable kde bugs that plague both x11 and wayland but are not really showstoppers
if you actually do want to avoid retardedly overcomplicated spaghetti slop then kde is definitely not the desktop environment for you and it hasn't been for at least 10 years
best case scenario kde becomes less of a shitshow, worst case scenario the people who have setups too fragile to adapt to the second better way to display graphics on a gnu system get cucked a little bit. all of you were probably using some tiling window manager you mostly wrote yourself so it doesn't matter much in that case
after all recently kwin-the-wayland-compositor has stopped being completely retarded on nvidia cards and it now works except for the usual unexplainable kde bugs that plague both x11 and wayland but are not really showstoppers
if you actually do want to avoid retardedly overcomplicated spaghetti slop then kde is definitely not the desktop environment for you and it hasn't been for at least 10 years
- Joined
- Dec 2, 2020
It's funny he says this because hyprland's website is the most trannycoded big fancy icons electron app looking thing I've ever seen for a window manager. Even more so when you visit their "hall of fame" and it's everyone also competing to make their hyprland setup look as gay as possible: https://hypr.land/hall_of_fame/
Only good one is the WoW Horde setup imo
Combustion Engine
kiwifarms.net
- Joined
- Sep 30, 2024
It's already been happening for a while, an example I can think of is custom shortcuts. The functionality was replaced on both sessions with a gimped service to accommodate wayland's.. "special needs" after being hidden on it for a few years. I'm pretty sure a number of display-related settings were also dropped from X11, but hard to tell between the endless march towards simplifying everything into nothingness and just not wanting to keep up with something they plan to drop.. as soon as they figure out how to remember window positions for Qt applications. Non-qt apps by next decade, maybe? Given the monumental effort the
- Joined
- Oct 19, 2023
it's a TILING WINDOW MANAGER. did you seriously not expect the tranime contamination levels to be high enough to need an anti-reddit hazard suit?
- Joined
- Oct 19, 2023
this is part of the eternal war against buggy bullshit (which is a fucking plague on kde and its biggest problem imo)
10 autistic settings means 10 new conditionals and about 100 ways that weird interactions can be caused and 1000 fucking bugs
the amount of complexity introduced by supporting both a moderately crusty protocol from the 80s and a newer protocol that works quite differently will introduce 5 million weird interactions and a truly colossal number of bugs that won't fit in a 64-bit unsigned integer
that doesn't seem like too much of a dealbreaker given the potential benefits here (4 million lines of source code removed and 20 quadrillion bugs removed as a result)
they're mainly just pulling shit out of x11 that the core wayland by itself can't do (it does one thing and it does it well: render shit from programs onto the screen as fast as it can with low latency and minimal screen tearing)