Originally Posted by wmarone

The threat's been there for years, and it's used by many vendors deliberately to avoid platform lock-in and increase cross-platform availability (Xilinx, for instance, uses Qt for their tools.) If it wasn't a threat before it won't be a threat going forward.

Originally Posted by wmarone

No, for people who use Qt. There is no real worst case scenario for Microsoft, since at least on WP7 they bar all non .NET/CLR code (including "managed c++").

Originally Posted by rm42

I wonder if a class action suit is in order for misleading businesses into investing in the wrong direction:

http://www.nokia.com/press/press-rel...newsid=1453894

FORWARD-LOOKING STATEMENTS
It should be noted that certain statements herein which are not historical facts are forward-looking statements, including, without limitation, those regarding: A) the timing of the deliveries of our products and services and their combinations; B) our ability to develop, implement and commercialize new technologies, products and services and their combinations; C) expectations regarding market developments and structural changes; D) expectations and targets regarding our industry volumes, market share, prices, net sales and margins of products and services and their combinations; E) expectations and targets regarding our operational priorities and results of operations; F) the outcome of pending and threatened litigation; G) expectations regarding the successful completion of acquisitions or restructurings on a timely basis and our ability to achieve the financial and operational targets set in connection with any such acquisition or restructuring; and H) statements preceded by "believe," "expect," "anticipate," "foresee," "target," "estimate," "designed," "plans," "will" or similar expressions. These statements are based on management's best assumptions and beliefs in light of the information currently available to it. Because they involve risks and uncertainties, actual results may differ materially from the results that we currently expect. Factors that could cause these differences include, but are not limited to: 1) the competitiveness and quality of our portfolio of products and services and their combinations; 2) our ability to timely and successfully develop or otherwise acquire the appropriate technologies and commercialize them as new advanced products and services and their combinations, including our ability to attract application developers and content providers to develop applications and provide content for use in our devices; 3) our ability to effectively, timely and profitably adapt our business and operations to the requirements of the converged mobile device market and the services market; 4) the intensity of competition in the various markets where we do business and our ability to maintain or improve our market position or respond successfully to changes in the competitive environment; 5) the occurrence of any actual or even alleged defects or other quality, safety or security issues in our products and services and their combinations; 6) the development of the mobile and fixed communications industry and general economic conditions globally and regionally; 7) our ability to successfully manage costs; 8) exchange rate fluctuations, including, in particular, fluctuations between the euro, which is our reporting currency, and the US dollar, the Japanese yen and the Chinese yuan, as well as certain other currencies; 9) the success, financial condition and performance of our suppliers, collaboration partners and customers; 10) our ability to source sufficient amounts of fully functional components, sub-assemblies, software, applications and content without interruption and at acceptable prices and quality; 11) our success in collaboration arrangements with third parties relating to the development of new technologies, products and services, including applications and content; 12) our ability to manage efficiently our manufacturing and logistics, as well as to ensure the quality, safety, security and timely delivery of our products and services and their combinations; 13) our ability to manage our inventory and timely adapt our supply to meet changing demands for our products; 14) our ability to protect the complex technologies, which we or others develop or that we license, from claims that we have infringed third parties' intellectual property rights, as well as our unrestricted use on commercially acceptable terms of certain technologies in our products and services and their combinations; 15) our ability to protect numerous Nokia, NAVTEQ and Nokia Siemens Networks patented, standardized or proprietary technologies from third-party infringement or actions to invalidate the intellectual property rights of these technologies; 16) the impact of changes in government policies, trade policies, laws or regulations and economic or political turmoil in countries where our assets are located and we do business; 17) any disruption to information technology systems and networks that our operations rely on; 18) our ability to retain, motivate, develop and recruit appropriately skilled employees; 19) unfavorable outcome of litigations; 20) allegations of possible health risks from electromagnetic fields generated by base stations and mobile devices and lawsuits related to them, regardless of merit; 21) our ability to achieve targeted costs reductions and increase profitability in Nokia Siemens Networks and to effectively and timely execute related restructuring measures; 22) developments under large, multi-year contracts or in relation to major customers in the networks infrastructure and related services business; 23) the management of our customer financing exposure, particularly in the networks infrastructure and related services business; 24) whether ongoing or any additional governmental investigations into alleged violations of law by some former employees of Siemens AG ("Siemens") may involve and affect the carrier-related assets and employees transferred by Siemens to Nokia Siemens Networks; 25) any impairment of Nokia Siemens Networks customer relationships resulting from ongoing or any additional governmental investigations involving the Siemens carrier-related operations transferred to Nokia Siemens Networks; as well as the risk factors specified on pages 11-32 of Nokia's annual report Form 20-F for the year ended December 31, 2009 under Item 3D. "Risk Factors." Other unknown or unpredictable factors or underlying assumptions subsequently proving to be incorrect could cause actual results to differ materially from those in the forward-looking statements. Nokia does not undertake any obligation to publicly update or revise forward-looking statements, whether as a result of new information, future events or otherwise, except to the extent legally required.

Originally Posted by ericsson

I really don't think so because : ...


LOL

Originally Posted by rm42

I wonder if a class action suit is in order for misleading businesses into investing in the wrong direction:

http://www.nokia.com/press/press-rel...newsid=1453894

Originally Posted by rm42

So do you think Qt represents a significant threat for MS or not? I'd say that it must represent a very significant threat if they are willing to spend "billions" in trying to derail it.

Why would it be the worst case scenario for KDE to fork Qt? I don't think you are making any sense. It would much worst if Qt is allowed to stagnate without any one picking it up.

As for MS, the worst case scenario is for Qt to become even stronger outside of Nokia's control. I personally think that is what is going to happen.

Originally Posted by wmarone

And as I said earlier, if Qt was truly going to be a threat it would have been obvious years ago. However, in the grand scheme of things, a toolkit alone (even as advanced as Qt) is not a threat. Especially not when it works quite well on your OS.

Originally Posted by cBeam

Qt is not dead, according to this article.

http://www.pcmag.com/article2/0,2817,2380331,00.asp

"Unequivocally, Qt is not dead," Aron Kozak, head of the Web and Community group at Nokia's Qt Development Frameworks, wrote in a Monday blog post. He acknowledged that it's "not the finest time in the history of Qt for sure, but also not the death of Qt that some of you are predicting either."

Well, if I were head of Qt I would say the same...