293
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Aug 2024
293 points (88.7% liked)
Cool Guides
4659 readers
1 users here now
Rules for Posting Guides on Our Community
1. Defining a Guide Guides are comprehensive reference materials, how-tos, or comparison tables. A guide must be well-organized both in content and layout. Information should be easily accessible without unnecessary navigation. Guides can include flowcharts, step-by-step instructions, or visual references that compare different elements side by side.
2. Infographic Guidelines Infographics are permitted if they are educational and informative. They should aim to convey complex information visually and clearly. However, infographics that primarily serve as visual essays without structured guidance will be subject to removal.
3. Grey Area Moderators may use discretion when deciding to remove posts. If in doubt, message us or use downvotes for content you find inappropriate.
4. Source Attribution If you know the original source of a guide, share it in the comments to credit the creators.
5. Diverse Content To keep our community engaging, avoid saturating the feed with similar topics. Excessive posts on a single topic may be moderated to maintain diversity.
6. Verify in Comments Always check the comments for additional insights or corrections. Moderators rely on community expertise for accuracy.
Community Guidelines
-
Direct Image Links Only Only direct links to .png, .jpg, and .jpeg image formats are permitted.
-
Educational Infographics Only Infographics must aim to educate and inform with structured content. Purely narrative or non-informative infographics may be removed.
-
Serious Guides Only Nonserious or comedy-based guides will be removed.
-
No Harmful Content Guides promoting dangerous or harmful activities/materials will be removed. This includes content intended to cause harm to others.
By following these rules, we can maintain a diverse and informative community. If you have any questions or concerns, feel free to reach out to the moderators. Thank you for contributing responsibly!
founded 1 year ago
MODERATORS
This guide is misleading. Sure, the product functionalities overlap, but if you have a mature workflow, you will not be able to switch without investing a LOT of effort in relearning your workflow on the new product stack. This is one of my MAIN reasons I hate the "I tried to switch to Linux and failed" genre of content. You're not going to find identical like-for-like replacements in Linux world that won't require significant effort to relearn. It's something us Linux users through and through need to bear in mind.
Also, we need to be cognisant that "just switching to Linux" narratives, fueled off infographics like this, will lead to frustration and dismissal.
No, I don't know how to change this - and morphing e.g. gimp to be a clone of Photoshop isn't the answer either.
It's not saying that it's a drop in plug and play alternative. It's saying it's an alternative software to get you the same result.
Hey now! The effort required to change workflows is how some of us have fun! Some of us derive joy in discovering new tools and new ways of doing things 😁
Think about it: How many people who switched to Linux at this point because they like learning new shit and fucking around? To them, a new tool that does something an old tool does in a new way is like being given a new flavor of ice cream to try! 🤣
It's why old time Linux users "just don't understand the resistance" people put up when it comes to changing apps... "WTF is your problem? If I can learn a new programming language in like two weeks surely you can learn the locations of a few new menu entries‽ I bet the new thing does stuff your old tool couldn't do! If you just poke around you might be surprised..."
Normal people's response: "Yeah... Fuck that. Spending that much effort to learn new things is what I call a waste of my time."
I agree with your fundamental point, learning new shit is definitely fun for me. But there's lots of different people and some just don't. I can definitely sympathize with someone who's income depends on one of these workflows, and why they can't disrupt that for "fun learning sake". There's only so many hours in a day and some people have different priorities.
This is such a classic Linux user response. Instead of taking the time to understand the many valid issues users have with Linux, you instead come to the same tired old smug conclusion that basically breaks down to "only smart people use Linux, like me!", and I say this as a Linux user.
Old time Linux users don't understand why people avoid Linux because they're not actually interested in listening and understanding peoples' issues. Perhaps these people like learning lots of new stuff and spending hours troubleshooting, but just not with their computer. If there was a Linux equivalent of a car, it's not hard to see why most people would just want the thing to work without bothering to become a mechanic for their car to work.
I'm sure there's things you've avoided learning because you consider it to be a waste of time-- does that mean you're unwilling to learn stuff, or would you agree that's probably an inaccurate characterization of you? Most Linux users I've met are in terrible physical shape or mediocre at best. As someone in pretty decent shape, I appreciate the benefits and struggles of exercise but it's just plain silly to basically shame others as lazy for the many reasons they could have for not exercising regularly.
I don't think pretty much anybody actually cares about their OS, they'll just use whatever is installed on their computer and install their favourite applications.
There's 2 things that need to be solved here:
To solve this we'd need mostly laptop manufacturers to install Linux by default, this is in no way happening soon, but might happen when point 2 is satisfied.
There's 2 ways to solve this, A. Somehow get companies like Adobe on board with Linux and develop for it. B. Make open source applications actually good. We need people to want to use open source applications, before they even switch to Linux. That means the applications need to rival, or even surpass their closed source counterparts. Most of the Foss creative/professional applications simply don't do that yet.
Solving these issues is not an easy task and will take a long long time, but most people simply will not want to switch to Linux and have to relearn every application at the same time, so I believe it is necessary
Your second point is key. In an ideal world, open source could rival and even beat the best paid offerings (see: blender). But in most cases it just doesn't. There's not a dedicated team working on the open source products, working with HCI experts and designers on every detail of the product. It doesn't preclude the open source being better (see, again: blender), but it does push a LOT of workload onto a bunch of hobbyist developers working in their spare time. The resultant burnout is typically why you see these projects sputtering along for years and years. I don't know how to solve those problems either, but they're your real "roadblocks".
I suppose it all comes down to money, Blender is an exception rather than the rule. They get a lot of donations from big companies, so they can afford to have a lot of people working on the project full-time. Most projects don't have that luxury, so they get stuck like you said.
To be honest, I don't know if there is a way to solve this, if there is it certainly isn't easy
Calling it a guide is misleading. It's labeled as a list of alternatives and that's what it is. Audio books are an alternative to reading, but it's definitely not the same experience.