Comment by godelski
9 months ago
> the battle for Linux as THE desktop OS was sabotaged by its most ardent practitioners.
This definitely happened with Arch. For some reason they killed the noob guide (which I helped maintain). It was a great guide that helped people go from noob to kinda knowing linux.
You can't have wizards without first having noobs.
Why gatekeep people from enjoying the same thing you enjoy?
Well, I guess all that gave us EndeavourOS and Manjaro. But still, we need more places for people to learn that nitty gritty stuff.
Hell, I'd love to learn more about the hardware hacking the OP is talking about. Love to learn about those GPU hardware modifications people do. I know it's hacker news, but I'd actually love to learn about that hacker stuff. If these companies are going to continue to fight this hard to prevent us from owning the things we buy, it sounds like an important thing to learn. Or else we're soon going to have robot butlers that are just sending lidar maps and high resolution photos of our homes back to these companies. We don't need elitest pricks, we need wizards teaching noobs
Regarding gatekeeping, there was one webforum I used to visit when I was a kid, which I think approached this in an interesting way. Most of the boards were available to the public, general users could post in them (other than the one that announced rules of course), but there was a subforum which could only be accessed by those who had demonstrated some minimum level of competency. Specifically this was a forum about programs for bots for a for-kids MMO (said MMO didn’t really have PVP that depended or gear or levels or anything, or a way of trading items or anything like that, so there wasn’t any player economy. So I think these cheats were pretty harmless. Well, except for the people making bots move in arrangements to make offensive symbols.). The process was, one could submit a program one had made that did something interesting, and they would judge whether it was sufficient to be allowed in to the subforum.
I think this had the benefits of:
• allowing people who don’t want to bother with newbies to not have to, if they stay in the subforum
• still having the places for “people who are skilled and willing to work with/help newbies” and “people who are skilled but don’t want to deal with newbies much” be in a sense the same place, while also having the place for the latter be the same as a place for newbies.
• provides an incentive for newbies to become skilled.
_____
Of course, this method doesn’t work if no one is willing to engage with the newbies. But I think it’s probably fine/reasonable to keep outsiders away from a few things provided that there is a reasonable path in.
Though, I’m not advocating that the approach that forum used be implemented everywhere. I just think it is something that a community could reasonably choose, depending on their priorities.
C'mon name the game. I need to know now.
It was “Club Penguin”.
The forum was primarily about the “Penguin Client Library” (or “Penguin Client System”, I think they went back and forth about the name?), which allowed writing PHP scripts to interact with the game servers.
Why PHP? I think maybe it was originally so people could use it to make web forms where people could put in their username and password and it would e.g. give them whatever item, but that kind of cheat was blocked very quickly, and I think it just remained in PHP for historical reasons, so instead you had a bunch of people running PHP on their local machine to run a bot doing normal game actions (but combined in unusual ways). Or maybe it was just the language the devs were most comfortable with, idk.
Something I know from a past role is that teaching is demanding, and for any broad audience you've got to consider the range of different thought processes that you may need to provide your knowledge in different ways. As someone trying to increase my linux skills (and assess the best one for potentially migrating/supporting my parents) it doesn't help that a lot of linux documentation comes across as barebones, or very concise about the one way it's meant to be done with a certain distro (plus potentially outdated on an earlier version), and a general lack of explanations.
As example toy projects I'm trying to test out dnf-automatic because I'd prefer not to have the admin work of manually keeping on top of routine updates, but there's little feedback (although so far that's better than pacman on Arch which specifically expects atdmin), or learning why a distro has set up swap/zram/zswap the way they have, what the limits are on that config, how to measure what my system uses and if/how to adjust it. There's little guidance within the system to get you up to that level, and to open another can of worms the terminal-first approach in linux's DNA usually doesn't present anything but the bare essentials for whatever tool you're running, but any extra/wasteful information shown could nudge you where the next step is.
But rewarding. What makes it less rewarding online is we don't see the benefits. We don't hear thanks. Which we should say more often
One thing I try to encourage is writing documentation. People are extremely resilient to this and I'm not sure why. It has a lot of benefits. I forget what I did, it helps remind me.
But people often claim no one else will read it or it's obvious. I think we've all dealt with the frustration of dealing with undocumented code. Seen how much time it takes because of the lack of documentation. Why doesn't this encourage writing documentation?
When docs are scarce and you have access, add a little. It can be built over time. Some is better than none.
The other thing I do is write notes. I put a lot of them in my dotfiles actually. This means I keep them just text (or link for images) and these can get carried around with me. I hand them out frequently and am always happy to have others contribute or share theirs but honestly I don't know a single other person that does this. But I find it extremely helpful. I reference them all the time. Granted, they're written for me but I think more people should.
Oh boy, I had many people telling me "please teach me how to use Linux [but I do not want to read any documentation!]". It gives me PTSD whenever I see people talk about documentation. I write documentation for myself and others who give a crap. I have been downvoted here for just simply stating that I wish people were less reluctant to read documentation, so y'know.
1 reply →
> Why gatekeep people from enjoying the same thing you enjoy?
That's an easy one to answer: they will eventually demand that Foo changes and remove things they do not like. It has happened to all media, it has happened to all software, you can be damn sure it will happen to something as modular as a Linux distribution.
This seems to falsely assume that technical users are more aligned with whatever the status quo is, and non-technical users are the ones who are looking to change things. In reality, technical users become technical users because they want to make changes, and 'casual' users just use whatever app/OS/etc is given to them, as-is.
Having bad or no support for your software isn't some good way to keep it 'pure', it's just keeping it less useful/relevant. Linux is OSS: fork it if you don't like something new, but don't hurt the ecosystem.
Deliberately hamstringing software or documentation so that others will stay away and not make changes is literally antithetical to OSS as a philosophy.
> This seems to falsely assume that technical users are more aligned with whatever the status quo is, and non-technical users are the ones who are looking to change things. In reality, technical users become technical users because they want to make changes, and 'casual' users just use whatever app/OS/etc is given to them, as-is.
Neither of this is true. There are plenty non-technical users that will be suggesting changes, there are plenty of technical users where they don't want things to change.
> Having bad or no support for your software isn't some good way to keep it 'pure', it's just keeping it less useful/relevant.
You are conflating "bad or no support" with "gate-keeping". Gate-keeping is about keeping riff raff out, but allowing those that are interesting to a path to being involved.
With respect to Linux distros. Linux is like a "kit". Different people offer you different "kits" called distros. Some of these kits may be given to you pre-assembled (Ubuntu/Fedora/Debian), other will require partial assembly (Arch) and some will require full assembly (Gentoo/LFS).
Arch/Void/Gentoo flavours of Linux don't advertise itself a user friendly distro like Ubuntu/Mint/Fedora. *It is expected you read the documentation and understand the command line*.
Thus why people were suggesting they should use the CLI tool. If a user doesn't want this, they should use something else.
Having a "noob" version of installation instructions for something like Arch/Gentoo will have the effect of allowing someone to fumble about and maybe achieve getting something functional, but they won't actually understand what they are actually doing and this will cause them problems in the future as they won't understand how to fix issues when they arise.
> Linux is OSS: fork it if you don't like something new, but don't hurt the ecosystem.
It is extremely difficult for even for large companies to run their own fork of large open source projects. Sure you can fork a smaller piece of software and maintain your own version, but anything significant you are unlikely to be able to do that. So you are forced either to use the changes you may not like, or you use something different, or you are are like the anti-systemd crowd essentially running a protest distro.
Also all the big forks in the software ecosystem is when two important factions have disagreed fundamentally on the direction of the project. We are not talking about individual users or developers, we are talking about the top tier developers/maintainers. A part-time/bedroom coder is unlikely to have any significant effect, even if they did it is often lead to burnout of these developers.
> Deliberately hamstringing software or documentation so that others will stay away and not make changes is literally antithetical to OSS as a philosophy.
Ignoring the fact that you are misstating the issue. It isn't antithetical to the philosophy at all. People decide their own level of involvement in any group activity. If you aren't willing to "pay your dues", then it maybe better for you to not be involved.
You will BTW see this to varying extents in Churches, Cricket Clubs and even your place of employment.
e.g. If you go to Church you have to accept certain tenants about the faith or at least respect them while you are there. I've been invited to Churches in my local area, by very nice people that I would like to get to know, but I can't believe in Christ, so I don't go.
4 replies →
It was rhetorical
Really, I'm calling people dumb for gatekeeping the things they enjoy. Things change regardless.
With Linux, you can have your distorts. Because Linux people tend to understand that you don't build "products" but environments. Places to build from. To build in. It's not always but it's a good idea. You can't make a product for everyone, but you can make an environment for everyone. It's why a computer or a phone is so universal but iOS or Android isn't
Well Linux can be used to plot crimes against humanity, can’t it? Can’t let that happen, think of the children.
> You can't have wizards without first having noobs.
But maybe some wizards feel miserable when they are forced to interact 95% of the time with noobs, instead of other wizards? Maybe they want a circle for themselves, as a basic human need?
I'd follow "Thumper's Rule"[0].
If you don't want to interact, you don't have to comment or engage.
Fwiw, I'm a big fan of having private spaces and niches. It helps to filter this out. I think it is a mistake we make in our community designs, that everything needs to be public or whole cloth (e.g. Reddit doesn't allow subdivisions within the community). I do like that HN puts a threshold on the downvote, but I'd even like a lower threshold on the upvote. Allows people to wade into the community.
But yeah, I think there is a problem now that the majority of communities have no ability to self filter and self form hierarchies. Without this, noob voices tend to drown out experts and frankly, noobs begin to believe they are experts. I'm sure we've all seen the typical CS stereotype of "read first line of wikipedia article, assume I know the rest" type of person...
[0] https://www.youtube.com/watch?v=9fYngTUZeUQ
Oh I am so pissed about the noob guide thing. I have intentionally removed my post about my bad interactions with the Arch community from my website, but if you're curious it's in the history: https://github.com/VegaDeftwing/OpGuidesHugoSrc/commit/dcc07...
The TL;DR: Arch gets harder year over year as the number of ways to setup/options for each piece of your system grows. Hell, even picking a bootloader among 10 options is confusing. A guide that just at least says "This is common for X, this for Y, the others are interesting and may be worth trying. If you don't want to investigate now, use X" Is DESPRATELY needed.
I tried to have that on my site, and a pretty high level arch forum admin came buy and told me to delete my website and made a PR just deleting the page. It was honestly one of the most rude and hateful interactions I've ever had online.
> Hell, I'd love to learn more about the hardware hacking the OP is talking about. Love to learn about those GPU hardware modifications people do. I know it's hacker news, but I'd actually love to learn about that hacker stuff.
This, I feel like ever since the fall of Twitter, a true hackerspace has been missing for awhile.
> For some reason they killed the noob guide (which I helped maintain).
Is it up or archived anywhere?
You can probably find an archive somewhere but it's utility is probably low. It did need constant maintenance. Which was fine. There were enough of us.
In fact, I even got more people to contribute. I used to say the best way to learn Linux is to install arch. To come back to me after your third failure. It's rough, but you learn a ton and accelerate really fast. Telling people to expect failure helps. They know it's not them being dumb and they won't ruin their computer. Plus, they have a safety net and I promise I will help, but the real lesson is the struggle.
Are you referring to the Installation Guide that had everything on one page? The guide now consists of many links, it is no longer on one page which is kind of annoying (still helpful, but there is more friction when using links/lynx).
I do not remember the "Noob guide" otherwise, but I do remember the old Installation Guide which was great as it had everything on one page!
6 replies →
hear hear