Thanks. I've been hanging around software for quite a long time, both commercial and open source, even if I say so myself. I've encountered some typical problems on both sides: often both sides are polar opposites, and it's holding both back.maksimKorzh wrote: ↑Thu Feb 25, 2021 7:00 am I enjoyed reading all of your posts within this thread.
Open source software:
- "All commercial software is evil." No, it's not. There's software that an open source community just can NOT write. You know "Content Aware" in Photoshop? A computer scientist and a mathematician got their Ph.D's with that. (And then, it still needed to be implemented.) That button cost hundreds of thousands of dollars, and took massive special expertise to develop. You're not going to get this done in open source. You're not getting two Ph.D-level people and a few developers working for 4 years on this for free.
- Often very technical. Just take a look at SCID, Arena, or XBoard. The possibilities are endless. The amount of confusion is, as well. (For a non-computer savvy user that is; computer people can figure it out.)
- Everything must work everywhere. That's a commendable sentiment, but it's almost impossible to get one piece of software to run on 200 distributions with 12 different desktops and 500 different library versions. It can be done with software that is open source, but to write commercial software for Linux is very hard. That is the reason why companies who do so, either write for the two great common denominators (Red Hat Enterprise, and Debian Stable), or they use something like Java so they don't have to write native code.
- Everyone uses the programming language they want. Before you know it, you have 7 runtimes, 12 compilers and 5 interpreters installed, and some programs use a lot of that. People are disinclined to work on projects with such huge learning curves.
- User interfaces aren't always the best. It's improving, but for most programs, it's certainly not on par with something like MacOS. (As much as I dislike Apple with regard to their mindset and company, I *love* OSX's user interface and how it looks.)
- ... I could go on for hours.
Commercial software:
- Often written only for Windows. If you're lucky, there's a Mac version. Linux? Blergh.
- Often written for the default settings. If you have your user interface set to anything but the default scaling, font sizes and colors, you're going to get into problems with dialogs not having the correct size, missing text or controls, or clashing colors. This is improving, but especially programs that have existed for a long time are still having problems with this.
- Draconian stuff like activation rules. "You can only activate this on 1-2 computers.", "If you deactivate the software on a computer, you can never activate it again on that computer." or the worst "You have 3 activation slots. Each installation takes one slot, even on the same computer if you re-install. If you want to reactivate more often, you will have to call our support to clear one or more slots." I'm not buying that shit. IF there is an activation, I only buy the software if:
* I don't mind losing it
* It has an "offline" activation mode, so I can go to the website, get the activation key, and save it on my computer; then I can do an "offline" activation using that key, even if the computer is not online. Examples of software like this are Catpure One and Pianoteq, at the time of writing.
* Everything else, and certainly DRM-ed software or "always online" software are off-limits.
- Where open source software is too technical and assumes a user is computer-savvy, commercial software often assumes the user is a dumb m****. I.e., no power user options. Clear, but cumbersome workflows with massive amounts of dialog screens.
- Not customizable. You work how the writer of the software thinks you should work, and nothing else.
- ... I could go on forever.
Open source software and commercial software can learn a lot from each other.
And, as I stated (somewhere, maybe this thread or one of the other Fritz threads), asking money for packaging open source software is NOT the problem. You can write a piece of software, such as a GUI, or even train a network for an open source engine, and then sell them for however much you like, bundling the (open source) engine with it, without problems... as long as you don't try to state that the open source engine is actually your work.