Rochus

History is usually written by some underpaid scientists or journalists. They are rarely among the winners. And yes, a development often takes a long time.

It's not always immediately obvious - even in retrospect - why one technology was preferred over another. Perhaps the price was the decisive factor, or perhaps the additional effort required to a…

The author compares himself with the prophet and apparently believes that the acceptance of functional programming languages requires intensive missionary work - just like with an ideology or religion…

Thanks. It was quite different when I looked at it a year ago. Maybe the new activity is because of Qt 6.

I'm sure you'll have a couple of shysters in tow trying to turn it this way. But at the end of the day (i.e. in court) only the effective will of the parties counts, no matter what (possibly…

And all of them have cancelled their license contracts in the last days or announced that they will not buy any more licenses after Corona?

No. Look closer.

You just got my arguments all wrong. We're talking at cross purposes.

> There was never such a thing. https://en.wikipedia.org/wiki/MeeGo which evolved to http://merproject.org/ and https://sailfishos.org/ after…

> In my opinion there is nothing inherently wrong with dual-licensing It significantly hampers cooperation. No company in its right mind would make a large investment for free in the development of…

You're getting close ;-)

Just have a look with what they earn money. The other stuff is just holding on to an illusion.

Just look at other essetial, widely used frameworks like OpenCV, Skia, Chromium, LibreOffice, just to name a few. In each such open source project a couple of companies are involved who can affort to …

Revenue of what?

That would be much too complicated. Just imagine such a model with OpenCV or some of the other big C++ frameworks. Selling framework licenses is just an outdated business model. It would make more sen…

Ok, a bit more than last year. One should also analyze what parts were commited. There is a significant difference in the commits by company to the core framework and the new 3D tools and other parts …

Nokia was not interested in license revenues but in popularizing the platform, especially their open source OS based on Qt. That's why they spent that much money to buy Qt ($150 mio) and then rel…

I'm sure you'll get it.

Nobody claims that. The problem today is that The Company only contributes a fraction to the maintenance and sells licences which includes work done by others. That's a pain point, isn't it?

Oh, a side blow ;-) Don't worry, I also studied law. What The Company can or can't from this contract is not granted unless you have supreme court judgments for the points in question. Other…

You won't get any support of the "big money" unless the library is at least LGPL so it can be used in closed source applications. GPL is primarily for the idealists, not for business.

> IMHO, if they lose this ... If The Qt Company discontinued the FOSS version of Qt, the Qt framework would become available under the BSD license, and there would no longer be a contributor licenc…

I think most developers get along pretty well with only the parts available under LGPL; that's not the issue. It's more of an issue that the The Company only represents a fraction of the com…

They lost long before Corona because the business model doesn't work.

Software development business is among the least affected by Corona. But Corona is a good opportunity for many managers to use it to justify previous misconduct.

Here is a good background article: https://www.embeddeduse.com/2019/12/21/safe-guarding-the-lgp... And here the email to which Qt Comany reacts: https://mail…

It shows the acknowledged state of the art and thus offers an alternative for people who do not always want to start from scratch. I am well aware that there is a generation that questions everything …

No, it's free. Just download it from https://standards.iso.org/ittf/PubliclyAvailableStandards/c0... .…

ISO/IEC/IEEE 24765 3.3810 software engineering 1. systematic application of scientific and technological knowledge, methods, and experience to the design, implementation, testing, and docum…

It's still very suitable for configurations. The statements can be used e.g. to configure rules.