Harmful is wanting to be paid for their work while expecting others to give their work for free.

It is plain impossible to live from selling desktop software with source code available, without having others in the first week come around and re-bundle it, Sourceforge style.

Most of the GNU/Linux desktop stuff is GNOME, and a lot of GNOME developers work at Red Hat, but not exclusively. If you want to work on free software desktop applications, I would consider working at a company like that.

A lot of desktop software is commodity stuff — mail clients, office suites, browsers, photo editing and the like. But there are some areas where we need to be better, such as video editing.

I gave up on that dream long time ago, I rather have paying customers.

This is essentially a byproduct of Red Hat selling stuff. Just take Filezilla, people don't donate, so the author used some shady stuff. Or look at gnupg.

Yes, it's pretty terrible if consenting adults choose to pay for software, isn't it?

I love FOSS, but people like you (yes, "fundamentalists") can't deal with the idea that some forms of software are probably better as paid transactions between well-informed parties. The laughable state of open source office suites and any serious competitor to most of Adobe's products suggests that this model has its limits.

> Yes, it's pretty terrible if consenting adults choose to pay for software, isn't it?

The thing I zero in on here is that I have literally zero problems paying for software. But I am wary of purchasing software that I don't get the rights to build, modify, and contribute to.

My worry with software like this is that vendors come and go, and people get their workflows destroyed because the software can't be "saved" when the business is gone (yes, when, not if! always plan for that "exit" that ruins people because the products are gone).

Would I prefer the software to be FOSS? Absolutely. I am also absolutely willing to pay for FOSS, and a good number of Linux users are too.

I'm even willing to take open-core style models if it means there's some FOSS code release, as much as I don't like the model.

I use a mixture of FOSS and proprietary software all the time, not because I want to, but because I _must_.

And in my workplace, FOSS solutions (even ones we pay for) are infinitely preferred over proprietary ones. Desktop Linux support is a must, as well.

Agreed on most of these points. But I've been on both sides of this transaction, on both sides of the proprietary/FOSS fence (to oversimplify and abstract the difference between Free and Open Source). From experience it is hard to get people to pay for FOSS; my hat is off to those who can manage it.

I do think that vendors should have to put things into some form of shared-source or open-source escrow (possibly shared as they might not have IP rights to open source everything they've done) with a kind of 'dead mans switch' arrangement (i.e. you walk away without updating or responding to bug fix requests, you trigger escrow).

I'm perennially concerned that the fundamentalist attitude to proprietary software is suppressing innovation in some areas: especially complex desktop software where there is (a) a heavy requirement for the kind of tedious UI work that FOSS projects clearly don't bother to do and (b) where most or all of the product is "right there in the code" (i.e. once you have Photoshop, you can go to town and edit stuff, and you're not really all that dependent on having access to some other product or service which can be monetized).

The attitude reaches its most extreme in software tools. Best expressed by Andy Gocke with his great tweet: https://twitter.com/andygocke/status/1017509689695715328

'Developer tools seemed like a good industry to be in, "sell shovels in the gold rush" and all, but it turns out developers prefer to dig for gold with their teeth.'

You assume I’m for open source. That’s the problem.

This isn't really germane to any point I made, but I presume this is the standard point in the discussion where you lob this particular bombshell ("I did so NOT see it coming that the guy who writes 'GNU/Linux' everywhere is a Free Software purist").

Whatever I wrote about the limits of "FOSS" software can be multiplied by a solid order of magnitude for "free only".

oh, the consenting adults argument, my ass. As if there aren't enough things consenting adults are banned from choosing like drugs or gambling. Some proprietary crap can be compared to both.

Could you please stop posting unsubstantive comments to Hacker News?

I don't think you have to be a foaming-at-the-mouth legalize everything libertarian to possibly accept the scandalous idea of someone, say, buying a closed-source office suite for money, but thanks for your input!

Good luck to that, reality doesn't seem to agree with you. The future seems firmly in the camp of a mix of FOSS with proprietary.

The most popular OSes are proprietary:

* Android (almost useless without the Google stuff, plus 99% of Android apps are unfortunately proprietary)

* Windows

* MacOS (I know about Darwin, everyone uses MacOS for the proprietary integration bits)

> Android (almost useless without the Google stuff, plus 99% of Android apps are unfortunately proprietary)

An open source GMS implementation exists, and might gain traction with the recent Android/Google antitrust lawsuit in EU. Have you tried LOS + microG recently? Have you seen the utter garbage frolicking around on Play Store? Quality, not quantity. At least with F-Droid, you know what you're getting. Same with Aurora, as it has Exodus support.

I feel similarly but not quite 100%.

For the core things the basic, inter-operable, standard should be fully open and free. This includes protocols, data formats, reference applications/servers/clients and anything similar.

A user should not need to pay to communicate. This is a natural right and one of the cornerstones of a free society.

However I don't mind proprietary products as OPTIONS that allow someone to do the above better or more effectively (while still following open standards for external APIs!), or for 'toy' tasks like games or fun. That's a premium feature or recreational extra.

For the logical retort about who should be funding the development and maintenance of the core items? In some cases (hardware APIs) manufacturers might want to form standards bodies (E.G. Khronos maintains OpenGL and Vulkan) and provide open standards. In other (most) cases governments maintaining civil infrastructure should contribute. I would love if every university had a course where existing code repos were examined by students for completeness and safety and the students actually signed off on their reviews and maybe even submitted patches (or at least bugs if the answer isn't obvious/requires architectural changes) for flaws.

I think combining it with some sort of code escrow could work. Keep it secret while you support it, if you go bust or stop support the source enters public domain.

So who do you expect to write all of this non proprietary software without any means of making money?

The same people who have been writing it in the past. And who said there are no means of making money? You're just assuming something which isn't true just because you can't come up with an explanation.

Who are those people? Most are paid or sponsored by corporations.

Well just let them continue to do so, then?

So either open source developers have to work for and enrich corporations or work on the side for free?

Why should software development be any different than any other profession where people get paid for their work?