This is the long-term cost of how persnickety FOSS maintainers are when it comes to accepting outside contributions to their work.
This is the long-term cost of shoving every teenager through python classes in highschool for 12 years and calling them developers.
This is the long-term cost of allowing them to continue down a path that was set by corporate interests and training them to use “the next hot thing”.
This is the long-term cost of not slapping the Jr’s hard enough when they don’t do as they’re told and instead run to the product owner with “10 great new ideas” that are going to take up 300% of your sprints for the next quarter.
yeah… last I knew, if a maintainer doesn’t want your sticky grubby toddler hands fuckin in their cookie jar, it’s their fucking cookie jar and they can tell you to fuck off.
Yeah, this is a terrifying response that chases away young talent.
I saw a comment mentioning how the mature devs are cut out and don’t have the chance to help pull up the new dev/give them training and wisdom.
If the older maintainers don’t have time for new devs without all the experience they gained over a lifetime, then FOSS is in for a crash.
if a maintainer doesn’t want your sticky grubby toddler hands fuckin in their cookie jar, it’s their fucking cookie jar and they can tell you to fuck off.
Yeah, that is exactly how it works. And doing that leads to your tool dying since you have no clue how to foster a community to take care of it.
It actually leads to a fantastic product and more free time because you’re not having to babysit kids who think the world owes them something because they can code ‘hello world’ in python.
Then the old maintainers retire and die, and so does their precious baby that was ‘open source’ but not really, stranding it all in an old distro.
But hey, who cares how shitty the world is after you die amirite?
The code is open and there for you to read. What you’re actually saying is you’re too lazy to read and understand it because the world owes you something. amirite?
You are pretty much the case in point: Grossly stereotyping the alternative into a perspective only based on extreme prejudice with an ample amount of pet peeves projected from personal experience. Like, I was actually expecting to see at least one valid counterpoint, like how much corporate interests shit on and ransack OSS, or the inherent dichotomy between software maintained out of goodwill in an environment that’s increasingly defined by greed and intellectual property bullshit inside failing economies, but nope.
They’re waiting on ChatGPT15 and it’s ability to re-write the GNU/Linux kernel in Python3 and PHP5, commit to master branch, and finally rid the wider POSIX community of “Digitial Equipment Corp. refugees/VAX apologists who poison the minds of the youth by mentioning pointers, time sharing, endianess, word size, registers, and worst of all that while Multics may seem obtuse to the uninitiated, the way it handles memory is actually galaxybrain.”
TL;DR - Seymour Cray tried to do for super computing what Malcolm X and Elijah Muhammad did for men who were honorable not only in front of the wife and family but ultimately GOD.
The suggestion that you could go from little endian to big endian by reading about multics and shitposts about turbo assembler means you’re either some kind of degenerate libertine IRIX wizard who still uses bogimps to talk about speed in relation to MIPS or the human manifestation of exclusive XOR or as the Cartesians say “what would happen if I didn’t NOT ?!”
Alert(“Hi I’m a kernel panic crashing this party on behalf of the Self programming language by way of not having a type system, a String not really being a string, and was expecting a long long unsigned int instead of an Integer”);
Omg we could re-write it in dart-lang too in /usr/src/experimental/top-secret/.hide-this-from-the-ai/linux-kernel-dart-7.0.0-SNAPSHOT
This is the long-term cost of shoving every teenager through python classes in highschool for 12 years and calling them developers.
This is the long-term cost of allowing them to continue down a path that was set by corporate interests and training them to use “the next hot thing”.
This is the long-term cost of not slapping the Jr’s hard enough when they don’t do as they’re told and instead run to the product owner with “10 great new ideas” that are going to take up 300% of your sprints for the next quarter.
yeah… last I knew, if a maintainer doesn’t want your sticky grubby toddler hands fuckin in their cookie jar, it’s their fucking cookie jar and they can tell you to fuck off.
Exhibit A. I wonder why nobody wants to work with you…
Yeah it’s really a mystery why no one wants to step up with well-regulated people like this one in the space.
Yeah, this is a terrifying response that chases away young talent. I saw a comment mentioning how the mature devs are cut out and don’t have the chance to help pull up the new dev/give them training and wisdom.
If the older maintainers don’t have time for new devs without all the experience they gained over a lifetime, then FOSS is in for a crash.
Yeah, that is exactly how it works. And doing that leads to your tool dying since you have no clue how to foster a community to take care of it.
It actually leads to a fantastic product and more free time because you’re not having to babysit kids who think the world owes them something because they can code ‘hello world’ in python.
Then the old maintainers retire and die, and so does their precious baby that was ‘open source’ but not really, stranding it all in an old distro. But hey, who cares how shitty the world is after you die amirite?
The code is open and there for you to read. What you’re actually saying is you’re too lazy to read and understand it because the world owes you something. amirite?
Jfc your replies in this thread are so cringe. Gatekeeping boomer energy.
Oh the irony. What’s gatekeeping about not wanting rubbish code in your repository? Lack of knowledge is self-gatekeeping.
The ‘wah wah…boomer’ cries are…cringe. Either step up with the knowledge and action, or don’t bother and cry “gatekeeping”.
You are pretty much the case in point: Grossly stereotyping the alternative into a perspective only based on extreme prejudice with an ample amount of pet peeves projected from personal experience. Like, I was actually expecting to see at least one valid counterpoint, like how much corporate interests shit on and ransack OSS, or the inherent dichotomy between software maintained out of goodwill in an environment that’s increasingly defined by greed and intellectual property bullshit inside failing economies, but nope.
Woah I disagree so much with all that
Edit: Maybe not the sprint stuff
They’re waiting on ChatGPT15 and it’s ability to re-write the GNU/Linux kernel in Python3 and PHP5, commit to master branch, and finally rid the wider POSIX community of “Digitial Equipment Corp. refugees/VAX apologists who poison the minds of the youth by mentioning pointers, time sharing, endianess, word size, registers, and worst of all that while Multics may seem obtuse to the uninitiated, the way it handles memory is actually galaxybrain.”
TL;DR - Seymour Cray tried to do for super computing what Malcolm X and Elijah Muhammad did for men who were honorable not only in front of the wife and family but ultimately GOD.
You’re making me hard! Don’t stop!
The suggestion that you could go from little endian to big endian by reading about multics and shitposts about turbo assembler means you’re either some kind of degenerate libertine IRIX wizard who still uses bogimps to talk about speed in relation to MIPS or the human manifestation of exclusive XOR or as the Cartesians say “what would happen if I didn’t NOT ?!”
Why not port everything to JavaScript and electron. Haha
Alert(“Hi I’m a kernel panic crashing this party on behalf of the Self programming language by way of not having a type system, a String not really being a string, and was expecting a long long unsigned int instead of an Integer”);
Omg we could re-write it in dart-lang too in /usr/src/experimental/top-secret/.hide-this-from-the-ai/linux-kernel-dart-7.0.0-SNAPSHOT