- Joined
- Dec 28, 2014
Who knew that having retarded "codes of conduct" to appease kiddy diddling troons would be an open invitation to bullshit like this?
Diseased Open Source Software Community - it's about ethics in Code of Conducts
- Thread starter CrunkLord420
- Start date
-
🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
- Joined
- Aug 13, 2020
Yeah just wave after wave of Java shit that underpins half of the fucking internet like Kafka, Lucene, ActiveMQ, Hadoop, Zookeeper, Tomcat to name but a few, but of course they're written in Java so they are clearly not worthy of your precious respect.
- Joined
- Aug 17, 2022
Yeah, pretty much
- Joined
- Aug 13, 2020
It's still being developed, although given that DCVSes won the mindshare war it is not a very active community by comparison. I know a few lawyers who swear by it but I wouldn't expect major new features ever. Probably this is a good thing as it does one thing rather well and any other requirements can be filled in by another piece of software.
Git can also version binary files for you however, and the large file extension means that you don't have to download all the previous binary versions to get a clone of the repo. If you would like something a bit more future proof this could be a good thing to move to.
- Joined
- Dec 28, 2014
Lawyers are super conservative about adopting anything new because interoperability, often with ancient systems almost as old as a boomer judge, is absolutely critical. When you're constantly filing on the last day, submitting something that's gibberish to the recipient is a disaster.
This carries over into a general suspicion of anything new.
- Joined
- Aug 28, 2015
I had a sideline in the, I dunno, late 90s working on doctors' and lawyers' in office systems. Caaaaaaan confirm.
- Joined
- Dec 12, 2022
As they should be. It's really insanity, how computers as a whole are managed. They're very important, and the real engineering goes into their physical manufacture, since hardware that doesn't work is worthless, but then they take these wondrous devices and let any dipshit write the software, since software that doesn't work is normal nowadays.
Here's an example of a new wrecker on the scene:
X servers no longer allow byte-swapped clients (by default)
In the beginning, there was the egg. Then fictional people started eating that from different ends, and the terms of "little endians" an...
who-t.blogspot.com
Yay indeed. By adding even more code and breaking things that previously worked, this young fool is convinced he's actually decreased the amount of code, and anyone who doesn't like it simply understands not the security concerns at play here. His attitude reminds me of the RFC8482 fuckers I see in my DNS responses from large servers.
Look at all of that nice work he made for others.
I'd liken this to someone who walks into a building wielding a sledgehammer and then attacks a column. Then he puts a lot of scaffolding around it so people can't get too close. This blocks the entryway to a staircase, but that staircase was hardly used anyway, and he's a volunteer, so no one can complain.
- Joined
- Aug 28, 2015
Why do The Kids hate the very idea of display clients and servers so much? The sheer hatred against the very concept of X has been fascinating.As they should be. It's really insanity, how computers as a whole are managed. They're very important, and the real engineering goes into their physical manufacture, since hardware that doesn't work is worthless, but then they take these wondrous devices and let any dipshit write the software, since software that doesn't work is normal nowadays.
Here's an example of a new wrecker on the scene:
X servers no longer allow byte-swapped clients (by default)
In the beginning, there was the egg. Then fictional people started eating that from different ends, and the terms of "little endians" an...
Yay indeed. By adding even more code and breaking things that previously worked, this young fool is convinced he's actually decreased the amount of code, and anyone who doesn't like it simply understands not the security concerns at play here. His attitude reminds me of the RFC8482 fuckers I see in my DNS responses from large servers.
Look at all of that nice work he made for others.
I'd liken this to someone who walks into a building wielding a sledgehammer and then attacks a column. Then he puts a lot of scaffolding around it so people can't get too close. This blocks the entryway to a staircase, but that staircase was hardly used anyway, and he's a volunteer, so no one can complain.
- Joined
- Dec 12, 2022
The same acquaintance who uses the term wrecker has an explanation for that as well. He claims part of why Python 2 was replaced with Python 3, everyone else be damned, is because Python 2 too closely resembled a working product, so that had to be corrected. Now, X11 sucks in design and implementation, but what exists works well enough after only several decades of work, and we can't have that.
- Joined
- Aug 17, 2022
I don't really know Python, but wasn't the problem with 2 something like it did divisions in a stupid way?
I agree with you about X. If it relies on endianness, that's undefined behaviour - they should be sorting that, rather than putting a sticking plaster on it.
- Joined
- Dec 12, 2022
The given explanation was improving Unicode support and, since they were already changing major things, to change whatever else they wanted to change.
The particular issue in the article regards X11 sessions in which the server and the client (these mean the opposite of what they normally mean in X11) differ in endianness; one end is supposed to compensate for the other, which is what the wrecker broke.
It's usually small things like this, and then all of a sudden nothing works once they accumulate.
- Joined
- May 17, 2019
I heard the way Python 2 handled Print was causing problems as well, which is why they added the parentheses. My memory isn't the best, though.
- Joined
- Feb 8, 2021
The split makes no sense if you only ever use a standard desktop computer and they've never used anything else. Doesn't help that people have been sabotaging the idea behind X for ages by sending bitmaps over the wire nonstop, hence the idiots who tell you that remote desktop protocols are "just as good" as network transparency. They fucking aren't and anybody who has ever used both knows that.
- Joined
- Dec 12, 2022
X can't support displays of differing refresh rates on the same session, or most relevantly in the present era a VRR display + a fixed refresh rate display, a very common setup for gamers!
- Joined
- Jan 27, 2020
Probably because the Apache Software Foundation tried memoryholing the real story behind the name being a play on "a patchy server" (describing how the software was based on existing code and a bunch of patch files) and inserted some flowery bullshit about one of its founders coming up with the name "Apache" after seeing a documentary about Geronimo (A). Apparently this change of story only happened in the last couple of years.
Last edited:
- Joined
- Dec 28, 2014
And now you know why you never try to cater to these fucks.
"It's called GIMP bitch. Don't like the name? Don't use it, you fucking gimp."
That's the proper response.
- Joined
- Jun 15, 2017
The complainant, being an "indigenous tech group", has no standing, but the complaint is valid. The name is misleading to normies, who read/hear "Apache Foundation" and think "feather-Indian org". This generates fake news, like, normies read, "feather Indians received a grant", "feather Indians made software that runs half of the world's computers". A foundation's name should be either nondescriptive or broadly related to its purpose. Peace Foundation weapons smugglers, ok. Peace Foundation bee conservationists, not ok.
- Joined
- Aug 17, 2022
You mean to tell me Red Hat wasn't produced by a group of milliners? Or that GNOME wasn't written in the Underdark?
- Joined
- Jan 28, 2018
The X thing is really nothing new, just another iteration of X getting ruined piece-by-piece on purpose. This has been going on for years. Meanwhile, wayland still sucessfully escapes usefulness and the only way to use wayland day to day is to run an X inside of it. Progress.
Maybe somebody should sic the rust trannies on wayland by loudly starting to wonder on reddit how C could ever be a safe language for something that important to modern linux usage. I'll bring the popcorn.
Maybe somebody should sic the rust trannies on wayland by loudly starting to wonder on reddit how C could ever be a safe language for something that important to modern linux usage. I'll bring the popcorn.