I have been watching the evolution of the Ubuntu Software Center for quite a while now. I had doubts about its interface and its speed, but I liked the fact that it offered an easy, down-to-earth interface that allowed users to install software easily. However, I have to say that the way the Ubuntu Software Center has evolved is worrying me -- a lot. I am not against the idea of selling software. What I am against, is confusing proprietary software with non-proprietary software, The Ubuntu Software Center seems to be doing just that.
(Score: 1, Disagree) by TLA on Monday June 08 2015, @06:59AM
No [gnu.org]. Is the short answer. You must distribute the source whether or not you also distribute the binary.
Excuse me, I think I need to reboot my horse. - NCommander
(Score: 2) by jasassin on Monday June 08 2015, @08:04AM
I think we are having a failure to communicate. I am asking if I write my own hello world program in C with whatever new idea also, and compile it under Linux using GCC can I sell the binary and not give out the source?
jasassin@gmail.com GPG Key ID: 0xE6462C68A9A3DB5A
(Score: 2) by TLA on Monday June 08 2015, @12:59PM
my bad, it was Dark O'Clock and I was misreading due exhaustion.
Excuse me, I think I need to reboot my horse. - NCommander
(Score: 2) by TheRaven on Monday June 08 2015, @08:11AM
sudo mod me up
(Score: 2) by hemocyanin on Monday June 08 2015, @08:17AM
Well first, C is just a language so it's use neither here nor there with respect to the GPL. Your own C code can be closed, open, or whatever you choose.
As for GCC, it's not quite so cut and dried as you make it sound: http://www.sitepoint.com/public-license-explained/ [sitepoint.com] (nice link from the comments here: http://stackoverflow.com/questions/2080588/can-i-legally-incorporate-gpl-software-in-a-proprietary-closed-source-web-app [stackoverflow.com] ) The discussion here is good too: https://lwn.net/Articles/583622/ [lwn.net] You do have to be careful however, not to integrate GPL software into your program when using GCC (LGPL however solves the problem and does not invoke the GPL).
Finally, you only have to release the source IF you distribute the code. If you make some changes to GPL'ed software and never distribute that software, you can keep those changes to yourself for all eternity.
Going back to GCC, imagine you wrote a novel using emacs -- do you really think that would mean you have to release the book free because of emacs? How about movie special effects done in Blender? It's GPL'ed -- did we all get free Spiderman-2 tickets?