News for hackers. Stuff that matters.
Re:Qt 5.7 released by Aissen on Thursday June 16, 2016 @08:38AM (#11915669)
With LGPLv3, the Qt company is sending a clear signal it's time to pay if you want to use Qt in a device (the industry being clearly anti-(L)GPLv3). It could be the chance for GTK, if they weren't also busy digging their own grave :-/ http://lwn.net/Articles/691131
Re:Qt 5.7 released by Nokinside on Thursday June 16, 2016 @10:02AM (#11916146)
What's wrong with paying for an extremely high quality GUI toolkit?

Btw. It's very easy to comply LGPLv3 in proprietary project if you want.

1) If you don't modify the Qt library and link dynamically there is no problem whatsoever.

2) If you modify the Qt library or link statically, it's enough to provide modified version of the Qt library and combined object files that make it possible to relink the application to different version.

Industry loves Qt. You either pay a little or spend little extra effort.

Re:Qt 5.7 released by pjmlp on Thursday June 16, 2016 @10:53AM (#11916511)
Many developers feel entitled to get their tools for free, but expect to be able to charge for their stuff, it seems.

This is what made RoboVM go comercial AFAIK, as they could hardly make a living from contributions.

Re:Qt 5.7 released by zerr on Thursday June 16, 2016 @02:19PM (#11917890)
Actually, it is "pay upfront" that scares many, I believe. Developers are experimenters - love to play and test many things and in case of commercial success, I think it will be a no-brainier to pay. So I think models such as "pay after your first 10K (or 100K) revenue" work.
Re:Qt 5.7 released by dman on Thursday June 16, 2016 @03:11PM (#11918190)
Discussions in posts about commercial libraries / tools developers often have extensive discussion about pricing and free alternatives (Threads about SublimeText come to mind). I wonder if the current sad state of developer tooling (stuck in the 70s in many cases) is because of our reluctance to pay for our tools. Would love to hear what others have to say about this.
Re:Qt 5.7 released by pjmlp on Thursday June 16, 2016 @03:48PM (#11918399)
I belong to a generation that had to pay for its tools.

My first Turbo Pascal for Windows was bought after a few months of saving. Same with other tools.

Even open source, I used to pay for the Walnut Creek CD-Roms.

Nowadays I still buy software tools and do occasional donations.

So I cannot understand how the millenials expect to get their tools for free on one side, but then complain that unless they are selling services or SaaS software no one pays them.

Re:Qt 5.7 released by sangnoir on Thursday June 16, 2016 @05:40PM (#11919087)
> So I cannot understand how the millenials expect to get their tools for free

I'm a (senior) millennial and I'm prepared to pay for tools that are worth it. However, Free (as in freedom) software has come a long way, I won't pay for tooling that is at par or less capable than, with Free software. I think the rise of GPL/Open source - GCC, Linux and Free DBs & languages (and their ecosystems) are to blame; not millennials.

Re:Qt 5.7 released by pjmlp on Friday June 17, 2016 @01:42AM (#11920879)
Such tools already existed back then, they were called freeware and Public Domain, or came as gifts in magazine listings or tapes.

Also some people would keep on re-installing them past the demo deadline, or crack them, just to avoid paying.

But not on the scale that happens today.

Linux and GCC would not be as developed as they are if it wasn't for the companies that sell hardware and are willing to pay engineer time to improve them.

During GCC early days, most contributors were the ones not wanting to pay for the Solaris SDK, so its development was as fast as Hurd still is today.

Regarding languages, that is why commercial tools get all the nice goodies, no one can make a living of selling improved tooling to FOSS developers.

Hence why many watch a talk from Bret Viktor and are amazed of his presentations, but we already had such tools in 90's, they just had the sin of being commercial.

Re:Qt 5.7 released by sangnoir on Saturday June 18, 2016 @12:45PM (#11929342)
> Regarding languages, that is why commercial tools get all the nice goodies

I mostly don't need the "nice goodies" - which why I don't but them (and I am prepared to buy when I do, or to show support to the developer. I love JetBrains).

> no one can make a living of selling improved tooling to FOSS developers

Good thing FOSS developers can improve their own tooling; they are developers after all. Freeware and Demoware are hardly comparable to Free & Open Source Software except on price. As a developer, I am empowered when I can fix bugs in my tools and submit a pull request upstream (happened to me 3 times this year alone). What do you do if you run into a bug in Borland Turbo Pascal or QBasic? If you have the energy, submit a bug report and hope it get fixed 4 versions down the line.

Re:Qt 5.7 released by pjmlp on Sunday June 19, 2016 @12:10PM (#11933423)
I rather spend the hours on the job making the customer happy and off-job hours enjoying my time on earth with family and friends.
Re:Qt 5.7 released by dman on Friday June 17, 2016 @11:33AM (#11923225)
Is there any way out of this local optimum?
Re:Qt 5.7 released by pjmlp on Saturday June 18, 2016 @05:08AM (#11927678)
No if people are willing to live by "worse is better" instead of shell out money to support those selling their tools.

You don't see this entitlement to free tools in other professions.

Re:Qt 5.7 released by dman on Thursday June 16, 2016 @04:00PM (#11918484)
I strongly empathize with you on this. It seems that most of us want to believe that the only value add should happen at layer of the software stack we are working on, everything below and above should be a complete (free) commodity.
Re:Qt 5.7 released by Avshalom on Thursday June 16, 2016 @06:04PM (#11919225)
Well then Qt is great because it's free, you can ship your app using Qt with out paying a nickel and it keeps being free no matter what your revenue. It only costs money if you want to ship your app with different legal terms.
Re:Qt 5.7 released by lallysingh on Friday June 17, 2016 @09:21AM (#11922460)
Yeah. Qt is far beyond reasonable, and I categorically can't understand the motivations for people who'd rather pay substantially more, with higher risk, to write their own version.
Re:Qt 5.7 released by coldtea on Thursday June 16, 2016 @01:04PM (#11917384)
That's why we can't have nice things...
Re:Qt 5.7 released by lallysingh on Thursday June 16, 2016 @01:52PM (#11917714)
You'd think their managers would see the benefits of paying a fixed cost instead of doing their own hacking/development.
Re:Qt 5.7 released by salicideblock on Thursday June 16, 2016 @03:02PM (#11918148)
You are forgetting that section 6 of GPLv3 still applies. That's the so-called "anti-Tivoization clause" that states that you must give the device owner "Installation information", allowing him to install and execute modified forms on this device.

I understand why you would license your software under this if you want to give end users the SW freedoms developers enjoy. I also understand why many makers of safety-critical devices avoid it like the plague.

Case in point, the automotive industry. Coincidentally, the Qt company has in past few years started engaging automotive companies [1][2]. The move to (L)GPLv3 can be valid and has other reasons besides pushing commercial licensing. But you can't say it doesn't have any impact on the industry.

[1] https://www.qt.io/qt-news/qt-company-launches-automotive-sui... [2] Spot the gauge needles and car body models in the announcement http://www.qt.io/qt5-7/

Re:Qt 5.7 released by AceJohnny2 on Thursday June 16, 2016 @04:35PM (#11918683)
This is also the reason OS X ships with ancient versions of bash, make, and other common GNU tools: those were the last versions to be available under GPLv2.

(Why they ship many of the more optional ones at all instead of embracing external providers like Homebrew or Macport continues to mystify and frustrate me)

Re:Qt 5.7 released by salicideblock on Thursday June 16, 2016 @05:15PM (#11918924)
Is it the same reason? Doesn't OS X allow you to replace the system bash?

If someone breaks their init with this replacement, Apple can always say "reinstall the OS". But if you're talking about a car that has crashed that's a different PR problem...

Re:Qt 5.7 released by baldfat on Thursday June 16, 2016 @11:13AM (#11916661)
Apache 2.0 is not compatible with LGPLv2.1 is the reason back in 2014 and QT has continued to grow during this time.

http://blog.qt.io/blog/2014/08/20/adding-lgpl-v3-to-qt/

> We also consider locked-down consumer devices using the LGPL’ed version of Qt to be harmful for the Qt ecosystem. ... Because of this, we are now adding LGPL v3 as a licensing option to Qt 5.4 in addition to LGPL v2.1. All modules that are part of Qt 5.3 are currently released under LGPL v2.1, GPL v3 and the commercial license. Starting with Qt 5.4, they will be released under LGPL v2.1, LGPL v3 and the commercial license. ... In Qt 5.4, the new Qt WebEngine module will be released under LGPL v3 in the open source version and under a LGPLv2.1/commercial combination for Qt Enterprise customers. ...

Adding LGPLv3 will also allow us to release a few other add-ons that Digia before intended to make available solely under the enterprise license. ... The first module, called Qt Canvas3D, will give us full WebGL support inside Qt Quick. ... The second module is a lightweight WebView module ... There is a final add-on that will get released under LGPL v3. This module will give native look and feel to the Qt Quick Controls on Android. This module can’t be released under LGPL v2.1, as it has to use code that is licensed under Apache 2.0, a license that is incompatible with LGPL v2.1, but compatible with LGPL v3.

Re:Qt 5.7 released by joshvm on Thursday June 16, 2016 @09:02AM (#11915785)
If you're fine with dynamic linking, then commercial development is still very much possible (though you lose Qt Charts).

The only major pain is that you have to supply a copy of the Qt Source if requested - the pain being that a link to the official repo is not enough, you have to be in control of the code. However, I would imagine if you gave someone the option of (a) downloading from the website or (b) paying postage and handling for a disc with the same thing, that would satisfy the license.

Re:Qt 5.7 released by distances on Thursday June 16, 2016 @01:52PM (#11917717)
> you have to supply a copy of the Qt Source if requested - the pain being that a link to the official repo is not enough

I don't think this this is true. My googling is now failing me as I just get results about linking of libraries, but I remember reading it's enough to point to the source if it's unmodified in your application.

Re:Qt 5.7 released by joshvm on Thursday June 16, 2016 @07:44PM (#11919802)
http://www.qt.io/FAQ/#_Toc453700716

The Qt FAQ specifically says that their copy isn't sufficient, but as you say perhaps it only counts if you've made modifications (which would make sense).

Re:Qt 5.7 released by Natanael_L on Thursday June 16, 2016 @02:28PM (#11917955)
Your responsibility is to make sure they can get the code for a certain amount of time after you distributed it to them.

So you can point to the origin source if you feel confident that it will remain available for long enough, and if you know you can provide an alternative way to access it if that site goes down (so just keep a local copy, and if somebody tells you that the link is broken then you just share that copy).

Re:Qt 5.7 released by kbenson on Thursday June 16, 2016 @11:14AM (#11916671)
Seems like there should be a company willing to handle that for you. Take $X for for specific hosting and delivery costs up to Y for particular open source projects you've listed, for Z years.
Re:Qt 5.7 released by oconnore on Thursday June 16, 2016 @02:32PM (#11917979)
Have you heard of this sweet version control provider called Github? I hear they might provide a solution for this sort of thing, for free.
Re:Qt 5.7 released by kbenson on Friday June 17, 2016 @11:52AM (#11923349)
That doesn't satisfy the legal requirements. First, that repo may go away at some point, and you need it guaranteed, and second, they aren't doing to mail you a physical copy for cost, which is also a stipulation of some of these licenses.
Re:Qt 5.7 released by rsp1984 on Thursday June 16, 2016 @08:50AM (#11915722)
Why is the industry anti-LGPLv3? In Layman's terms what are the key differences between LGPL v2.1 and v3?
Re:Qt 5.7 released by maheart on Thursday June 16, 2016 @09:09AM (#11915812)
The (L)GPL3 disallows Tivoization[1]. Unfortunately, device manufacturers (including Apple) have avoided upgrading to the latest version of certain software (e.g. Bash, Samba, GCC) to avoid the (L)GPL3.

[1] https://en.wikipedia.org/wiki/Tivoization

Re:Qt 5.7 released by zanny on Thursday June 16, 2016 @11:24AM (#11916742)
So the LGPL is fulfilling its promise and doing its job by protecting its users from tonka toy hardware they can't control.
Re:Qt 5.7 released by Matthias247 on Thursday June 16, 2016 @03:36PM (#11918327)
I don't see any help in protecting auser, if he can see some parts of code and (in case of [L]GPL3 exchange them) but not everything. The "malicous" parts (whatever that means in that context) can still be in the proprietary software parts.
Re:Qt 5.7 released by bertit on Thursday June 16, 2016 @09:25AM (#11915877)
AFAIK, the reason Apple avoid (L)GPL3 is because of the patents clauses. Not because of the Tivoization
Re:Qt 5.7 released by _pmf_ on Thursday June 16, 2016 @09:20AM (#11915858)
> It could be the chance for GTK, if they weren't also busy digging their own grave

They have a fleet of excavators lined up.

Especially for non-X systems, GTK should be considered dead. I kind of liked GTK's C-only approach with simple call backs.