4 ms·
Can you be more specific about what you see in the "Stands" tab? I just see random OSS projects... What overlap are you concerned about? Why is that your ideal
by guerrilla 5y ago
Can you be more specific about what you see in the "Stands" tab? I just see random OSS projects... What overlap are you concerned about?
Why is that your ideal world? What's wrong with diversity and competition?
- gjsman-1000 5y agoLack of diversity is a bad thing. Too much diversity is also a bad thing. In my opinion, we have too many distributions for not enough people.
- guerrilla 5y agoWhy is that your opinion? Don't they exist because of demand for them? Why else would the exist? And why is too much diversity bad? What are the negative consequences here? The only thing I can think of is projects that you favor are lacking resources but if that's the case which ones do you even mean?
- gjsman-1000 5y agoI mean I in the context of being a developer for Linux. I’d love to support my apps on Linux… but it is hell. Flatpak seems like it will help immensely, but Flatpak has a ton of people on here who hate it. Secondly, a quality perspective. So many bugs remain because so much effort is going into patching the same bug in countless distributions, rather than using those resources to make a smaller collection of codebases more bug free. Thirdly, it intimidates newcomers, be they users or developers. Which distribution should I use? If I have a problem, is the distribution at fault? And so on.
- toyg 5y ago> but Flatpak has a ton of people on here who hate it. Not a Flatpak-related reply, but generally speaking: when it comes to tools for your work, don't listen to forums like this. Just use what you like and see how it works in the market. If Flatpak works for you, use it. Otherwise you'll end up tied into obscure LISP dialects and other stuff that really doesn't work well in the real world.
- ben-schaaf 5y ago> I’d love to support my apps on Linux… but it is hell. Flatpak seems like it will help immensely, but Flatpak has a ton of people on here who hate it. As someone who professionally writes native desktop software for all 3 major platforms I can't say I've had the same experience. Providing packages for the major packaging systems is fairly easy, though less so when cross-compiling to different architectures. These formats very rarely require any changes. Other distribution methods like flatpak can be provided by those that care. For Windows you require signatures, dealing with the registry and installer compilers that need wine to work outside of Windows. On macOS you need a signature and notarisation, and any new requirements they decide to add. Some of which you can't do without a mac.
- seba_dos1 5y agoAgreed. I have written some video games that work across several platforms and in my experience, GNU/Linux was the easiest platform to handle by far. > though less so when cross-compiling to different architectures If what you develop isn't very expensive to compile, cross-compiling can be super easy as well - you can just `docker run` a foreign architecture image with qemu-user and have it work exactly the same as it would natively (just much slower).
- jeltz 5y agoHaving developed commercial desktop software for Linux, Windows and Mac I would say the churn is a much bigger issue on Mac than either of the other two. Developing for Linux is mostly fine.