Re:Our experience launching a paid, proprietary product on L...
by mjevans on Monday July 23, 2018 @06:48PM
(#17596663)
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.
Re:Our experience launching a paid, proprietary product on L...
by kaybe on Monday July 23, 2018 @07:42PM
(#17596960)
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.
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.