Comprehensive solution for crafting and managing sophisticated digital experiences
Build engaging websites with intuitive web content management
Leverage a complete UI toolbox for web, mobile and desktop development
Build, protect and deploy apps across any platform and mobile device
Build mobile apps for iOS, Android and Windows Phone
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate UI, load and performance testing for web, desktop and mobile
Host, deploy and scale Node.js, Java and .NET Core apps on premise or in the cloud
Optimize data integration with high-performance connectivity
Automate decision processes with a no-code business rules engine
Transform your businesses in order to survive in a completely digitized and connected world driven by software innovation.
Globally scale websites with innovative content management and infrastructure approaches
Content-focused web and mobile solution for empowering marketers
Faster, tailored mobile experiences for any device and data source
UX and app modernization to powerfully navigate today's digital landscape
Fuel agility with ever-ready applications, built in the cloud
Danny Coward does a great job of capturing everything that comprises the Java 6 and highlighting the key features. Rick Ross gives his established and authoritative perspective on the release in his posting on JavaLobby; he is also able to unpeel some of the less publicized features that allows your to attach a variety of performance and monitoring processes without re-building a debug of your application... very cool.
Later this evening, I'll have some time to look at the response to Java 6 in the Microsoft discussion groups; I expect interoperability to be a major theme, and it should be interesting to see how the .NET community are digesting this having enjoyed a recent platform upgrade of their own.
Looking at both the recent releases of the .NET Framework 3.0 and Java 6, one question that inevitably gets the chattering masses going is when a wholesale migration might occur. Sigh. This is a well worn question and frankly somewhat of a red herring. Whether or not people jump to the a new development platform immediately, adopting a new platform could be fraught with unforeseen pitfalls. While it is nice to consider the bells and whistles that come with these releases, I'd recommend a more pragmatic approach: look at your project needs, current and future, weigh the advantages and risk and make sure you do whats best for your application and/or business.
View all posts from Jonathan Bruce on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2016, Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.