Indeed, I think it’s just two philosophies that don’t necessarily need to be at odds. Permissive licenses help speed the adoption of languages and libraries, which ultimately feeds into the slowly building momentum of the copyleft projects that use them.
The problem is that a lot of users aren’t building a new machine for Linux, but converting an existing Windows laptop or desktop. In my case, I’d already bought an Nvidia card about a year before I decided to switch to Linux for gaming. Not ideal, of course, but it work a good 95% of the time and I can’t really afford to get a different card right now. I’ll definitely keep it in mind for my next pc upgrade, though.
I know this is just adding to your problem, but I wanna add to the majority and say go with Mint. It’s based on Ubuntu, which in turn is based on Debian, so most anything you can do on Debian, you can do on Mint. This is handy to know whenever you see a “.deb” file.
One of the things that makes it an easier transition from windows is that it’s a lot less strict about including proprietary drivers and codecs (though apparently Debian now includes a few by default). It also includes a few more GUI tools by default, like the package update manager.
I also have found Mint’s Cinnamon desktop environment to be the easiest transition from a Windows environment. KDE is also a good choice in that regard and it’s what I use now, but its plethora of options can be overwhelming for new users.
The distro wars can be pretty overwhelming, but I’d say pick whatever appeals most and go with it. If you get to a point where you can’t do something that you want to do, you can always come back and ask for advice and maybe switch up a different OS.
Honestly I still struggle a lot with this. I can click around a UI and feel what might confuse a user, but building a UI from scratch feels like such a shot in the dark.
I mean, there’s something to be said about adhering to an industry standard. Of course no project has to do so if they don’t want to, but people trying to get on with their work don’t want to spend a bunch of time relearning everything. I think Blender really thrived when they loosened up a little on their ideas of what a workflow should be and gave people industry standard options out of the gate.
Whether we like it or not, GIMP isn’t going to be most people’s first experience with image manipulation. Whether they had a free PS license through school/work, had a subscription at some point, or once got it through ahem alternative means, people will be coming into GIMP with certain expectation of what the workflow should look like and will get frustrated pretty quickly.
The truth is that most people don’t really care. A lot of them don’t even know what an OS is, they just need a machine that lets them browse the internet, write documents, and maybe play some games. An ad is maybe an annoyance to them, but not one that’s going to make them install a new OS. It’s not because they’re dumb or ignorant, it just doesn’t rank that high on their list of priorities (even if we think it should). I think being in these communities kind of makes us forget that a lot of people don’t think that much about tech.
I do think that easy to install/use Linux distros could one day start changing some minds, but that distro won’t be one that’s popular with current Linux users. You’d basically need something that very rarely requires you to touch a terminal, even for troubleshooting, because that’s where people will nope right out.
On the other hand, this is why stuff like that “look at all the data Google has on you” video are important. For us it’s a yeah duh moment, but the average Chromebook user probably has no idea and is rightly surprised about it. Reach people in terms they can understand.
It’s a rough balance when you’re trying to convince people unfamiliar with the internals (let alone non technical people) to make the switch. Saying “Linux is safe, but not bulletproof” may scare them back to the devil they know even if there’s no greater guarantee of safety there.
I have no horse in this race, I don’t have strong feelings about it either way as long as it works. But I can’t help but notice that OP skipped replying to me.
What is the benefit of no systemd?
I used to be like Jarvis here, but I’m a convert. I actually was tired of using my mouse all the time, so one day while writing up some docs, I decided to give Vim a try.
Honestly, I hate to say it but, I can’t go back. It’s so nice to be able to do so much from the keyboard alone.
I hang out in the Python discord quite a lot and it seems to work well for this purpose. I will say that Python’s core library and many of the most popular packages are well documented, so it’s definitely not a case where discord is the main source of knowledge and that’s a good thing. However, a lot of people on there are new to development and don’t know where to start, so we answer their beginner questions while teaching them how to search the docs for answers.
There’s many ways to point out the issues with the patch without being a jerk. The patch wouldn’t have made it in either way, and maybe there could’ve been more useful conversations about the concerns (re: tar) that were brought up in the previous message.
Meh, maintainability is king. Sticking to the letter of the style law is probably not necessary, but ignoring badly structured code now is going to bite you in the ass when it comes time to change any of it.
Joining via server invites that guide you through sign up, no dedicated server to host (I know, major downside for people who don’t want all their stuff centralized to Discord’s servers), GUI server admin tools, etc.
I think devs tend to vastly overestimate how tech-savvy the average person is. Bring up hosting, DNS, port forwarding, terminal, etc. and they’re going to nope out pretty quick. Provide an option that lets you do everything from a single GUI and they’ll use it. Enough people use it and eventually the tech-savvy folks have to follow because that’s where everyone is.
That’s absolutely not to say that it’s a good medium for documentation. I will always prefer well-written and organized docs first and searchable forums/issue trackers/SO second. But that second group has a lot of tech elitism and devs who are (perhaps justifiably) short on patience, so Discord seems a lot more accessible to newbies who are asking the most basic questions.
I’m trying to get my feet wet in FOSS by making small doc PRs since I’m way too scared to actually touch code. It’s not fun, but it is satisfying.
If it’s open source and the license allows it, I wouldn’t consider that stealing. If a fork gets more popular than the original, then it either addresses a major missing feature of the original or is simply more active. If this displeases the original dev, they can hopefully work it out with the maintainers of the fork. This is a feature of FOSS, not a bug.
I know it’s just a meme, but god damn I hate this format. Some men cry while watching the titanic, some (many) women use *nix.
It’s just the easiest distro to get into coming from windows/mac. It’s more lenient about the third party/closed source software that people might be familiar with, lots of GUI tools including the Software Center that makes it easy to install things, and plenty of flavors to suit whatever feels most natural to you. It’s got a nice GUI installer and live version that is sure to make people feel more comfortable about installing an OS if they’ve never done it before, and it’s not at all fussy about the hardware it runs on. It’s also rock solid as far as I’ve experienced. And, of course, it has the benefit of accessing the huge amount of software that supports debian. Also, owing to its popularity, the community is very active and welcoming to newbies.
When I was first getting into Linux, I was definitely more experimental and tried out Fedora just to get as far from Windows as I could. Now I’m not so adventurous and just want something that provides as similar a workflow as possible to the workflow I have to use at work with windows. So it goes that, when setting up a new laptop where I want an OS that just works, I reach for Linux Mint.
I don’t really consider myself a power user, so I’ll use flatpak if it’s easy to use and doesn’t block certain features. Otherwise I’ll just look for an appimage or debian package because I already know how to use those.
The biggest issue I see is big labels like “potentially unsafe” and “proprietary” on flathub that scare people away from popular, well trusted non-FOSS software like Discord. At the same time, FOSS-friendlyness is one of the selling points for many people. How can it appease both camps?
Plus, casual users aren’t going to flathub to download programs, they’re downloading from the software site. Since most of the most popular flattpak images are not officially verified by the software owners, nothing is linking to them to increase their popularity.
I think the rub here is that most developers aren’t developing/publishing their own software, but honing their skills on writing proprietary code while also putting food on the table. To that end, a permissively licensed library is better because the company will actually use it and the developer will gain experience with it that they can then use outside of the proprietary environment to contribute to FOSS projects (some of which may well use GPL). If a GPL end user product gets popular enough, it will eventually be able to use all of that gained experience to compete with the propriety alternatives, so I do think the two can work in tandem.