What's In A Name? That Which We Call Qt, By Any Other Name Would Code As Well...
Renaming a company can be a torturous process. Developing the new brand, getting the word out, and answering questions can be long and grueling, and at least some customers are bound to be upset, and possibly quite vocal about it. Not everyone is willing to brave these waters, though Nokia obviously is, as it announced today the renaming of its corporate Qt division, Qt Software.
Those that have been following the Qt toolkit for some time will know that Qt Software was not the original name of the project's corporate arm. Qt's first corporate parent was Trolltech, founded in 1994 by the original Qt developers, Haavard Nord and Eirik Chambe-Eng. In January of 2008, cellphone-giant Nokia bought Trolltech for $153 million, and when the deal was finished in October, the company was renamed Qt Software.
In January, just months after the renaming, Nokia put to a final end one of the great sagas of the Open Source world by announcing that, from version 4.5 — the current release — Qt would be tri-licensed, adding the LGPL to its own proprietary license and the GPL, added in 2005. Those involved with Linux from the early days will recall that the GNOME desktop environment sprang out of the KDE/Qt licensing controversies of the mid-1990s.
Nokia has now decided that Qt Software isn't quite the right appellation, and as of today, has renamed the division Qt Development Frameworks. Along with the new name comes a new website, qt.nokia.com, with information about both Qt's Open-Source development and the commercial support and licensing options offered by Qt Development Frameworks. Nokia's Director of Global Sales, Marketing, and Services, Daniel Kihlberg, shared the rationale behind the change:
We want to increase the use of Qt by mobile developers and to achieve this we've strengthened our name's link to the Nokia brand. The progress of our new Qt for S60 product and our future involvement in Maemo are examples of how Qt will reach out to mobile developers in addition to desktop and web developers.
We selected Qt Development Frameworks because at the end of the day, our goal is to provide developers with the best framework: Qt.
Rest assured, nothing is changing with the Qt framework itself — just the name of the people backing it. If you're looking to grab your own copy, though, or to send someone else to pick up theirs, be sure to take note of the forwarding address.
Justin Ryan is a Contributing Editor for Linux Journal.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide