Cool Guides
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!
view the rest of the comments
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.
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.