New Gnome Code of Conduct - It's pretty bad tbh

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
On one hand my reaction is "LOL, GNOME" because… have you seen this shit? On the other hand the slowly dripping poison of CoCK is pretty annoying. The rules are always so ill defined I read them in a nasally art ho voice. My future is clear at this point, I'll probably find a busted Solaris box in a dumpster, install OpenBSD on it and live on FidoNet powering my gateway with a glorious 300 boud packet radio.

Off my lawn, etc.
 
Matz took the CoC by known leech Coraline Ada Ehmke, stripped it of any teeth, adopted the non-stupid parts in a benign form, and took Corey to like it or leave. The troon left in a huff and Matz stood his ground.

Ruby has avoided the hellpits of modern higher-language OSS development only because it's a dictatorship run by the japs. Python, JS, PHP are all infected as hell and already circling the drain.

Well, JS was always terrible.
 
I've tried explaining this to girls before, it takes a certain kind of autist to like programming and women rarely fall into that category.

Infosec is even more male dominated, but you wouldn't know that from Twitter or the convention speaker lists. OSCPs on linked in are 98% male.

Well, JS was always terrible.

JS "coders" tend to fall into two categories, troons and h1b visa "bobs and vagene" pajeets.
 
Infosec is even more male dominated, but you wouldn't know that from Twitter or the convention speaker lists. OSCPs on linked in are 98% male.
Some of the most talented hackers I know are borderline psychopathic trolls who wouldn't be out of place on 8chan. You can't git gud easily in that field if you get prickly-wicklies from being called a dong inhaling niggerfaggot.

I remember first time I used Debian, I thought the DE was a steaming pile of horseshit.
Since then I have weaponized my autism and use i3 on Arch and spend most of my time in emacs, which I do not believe has a code of cucking.

Do you think GNU as a whole is susceptible to this shit or just the normie parts like GNOME?
 
Last edited:
Do you think GNU as a whole is susceptible to this shit or just the normie parts like GNOME?
Considering Stallman got the boot for basically no reason, yes, all projects are susceptible unless proven otherwise.

Ruby has avoided the hellpits of modern higher-language OSS development only because it's a dictatorship run by the japs
I think this cuts to the core of the issue that there are so many "communities" now instead of the old model of BDFL, because God forbid even one contribution be dismissed no matter how dumb or outright harmful it is. It's not about one man's vision or even one man's desire to solve a problem anymore, it's about the endless fiefdoms and power grabs that always, always, come about when no one has the real power to unilaterally say "this is dumb and it will not be a part of this project". Getting a CoC shoved in your face, no matter how large or small the project is, is just a symptom of the diffusal of authority, IMO.

edit: wording
 
Last edited:
View attachment 1112895

Feel free to make a less half-assed version.
The problem with GTK2 was it was getting more difficult to maintain and add features. GTK3 is more modular so widgets can be extended better. GTK4 is in the works because GTK3 is starting to get to the point where it's becoming unmaintainable.

The problem isn't all GTK it's Gnome 3. When Gnome 3 was released it became a shit show. Who the fuck wants a separate application window on a separate workspace? Then all the configurable stuff such as GTK themes were out of the window. Customizable panels and windows list? Yeah let's remove that as well as a system tray because who the fuck wants a productive environment right?

GDM was re-written so it's not as configurable. The Gnome designers really hated customisation. Now we have to rely on third party tools to make Gnome 3 usable such as gnome-tweak-tool.

GTK is written in C which isn't an issue because it's fast; it just becomes harder to maintain overtime if your not careful due to C being procedural. There are bindings available for other languages such as JavaScript (why though?), python which is a slow and vala in which the GTK team have neglected (only one main developer is working on the project and probably for free). You have other bindings which are incomplete for other languages like C#, Rush, Go... The problem is GTK is managed by the Gnome team.
 
You can exclude everyone you like from private projects, there's no law against that, which makes developers bending over backwards when the trannies come crybullying even more perplexing. In the cases where the developers ignored the bitching literally nothing happened, see gimp.

Pretending these projects have no commercial aspects and that people expect nothing in return for their contributions is nonsense at this point. Any documents that people use to govern their behavior in this exchange are representations made by the parties. If you had a "no niggers allowed" code of conduct you'd be in hot water.
 
I think this cuts to the core of the issue that there are so many "communities" now instead of the old model of BDFL

If you're technical enough you can either a) understand BDFL is correctly calling the shots and play ball or b) think him a fool, fork the code and declare yourself a BDFL. But that requires skills or work, two things that are alien to CoCK authors.

You don't have to love or "respect" people to achieve things, you only need common goals. I don't give a fuck about people living two citis over, but I gladly would pay taxes to have a train line build so I can visit their pubs or whatever. CoCK goes way over what the common courtesy require from people participating in society. It's clearly a power play.

I wonder if any of the people supporting those documents can show any numbers, how successful it is in achieving its goals? How much better projects covered by that type of rules develop, how many more non-binary legless women joined the project since they had their rights enshrined? How many people stopped contributing? Surely, if the thing is so good, the results will follow? GNOME 2010-2020 timeline is clear example how much better it got.

GDM was re-written so it's not as configurable. The Gnome designers really hated customisation. Now we have to rely on third party tools to make Gnome 3 usable such as gnome-tweak-tool.

That reminded me a funny (well, "funny") story from back in a day. I knew a trollish GNOME developer who hated the new direction. We laughed our asses off with him constantly throwing patches reverting all the changes to underlying configuration. His 'tistic obsession was something about close/minialize/maximalize buttons on GTK chrome and their order. I can't recall the details now. He would go for pages and pages explaining his position with core devs getting pretty pissed. He even made a patchset, old school style, one could drop in in his source tree that would make blue arms go away.

God bless you, wherever you are. In the end, you've been proved right.
 
Last edited:
Computers are getting faster but software developers are getting lazier and stupider.
sample text
6XD7U3L.png
 
I really don't understand the systemd hate other than "how dare you make my OS usable" or being a meme made up by trannies who are overly obsessed with the ancient unix concept that other people blindly follow.
UNIX is dead, long dead, Linux and systemd are dominating because they aren't Unix, it's a unique OS with it's own API layer and systemd takes full advantage of it to offer a robust service management experience. And developers are more than happy to make use of systemd because it actually makes life easier for everyone who isn't some autist arch user watching lain in his terminal.
When I dicided to ditch Ubuntu for another distro, I was choosing between a systemd-distro vs. a systemd-less-distro, I realized that all my gripes with systemd are either fully philosophically with what I read about its development or above my technical expertise. So I went with the systemd-distro and it been all well outside a few issues here and there.

See also these videos:


 
When I dicided to ditch Ubuntu for another distro, I was choosing between a systemd-distro vs. a systemd-less-distro, I realized that all my gripes with systemd are either fully philosophically with what I read about its development or above my technical expertise. So I went with the systemd-distro and it been all well outside a few issues here and there.
The pros and cons of SystemD & OpenRC
 
GTK is written in C which isn't an issue because it's fast; it just becomes harder to maintain overtime if your not careful due to C being procedural. There are bindings available for other languages such as JavaScript (why though?), python which is a slow and vala in which the GTK team have neglected (only one main developer is working on the project and probably for free). You have other bindings which are incomplete for other languages like C#, Rush, Go... The problem is GTK is managed by the Gnome team.
GTK is written in C because it's so low level pretty much every language can interface with it.
Even a slightly higher level language like C++ has some abstraction ideas of it's own which aren't really universal and then you get stuff like name mangling and it's all a bit of a headache.
1569951997645.jpg
 
Back