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
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