ProductsDesktop Server Red Hat Enterprise Linux OpenStack Platform For IBM POWER For IBM System z For SAP Business Applications Satellite Management For Scientific ComputingExtended Update Support High Availability High Performance Network Load Balancer Resilient Storage Scalable File System Smart Management Extended Lifecycle SupportAccelerate Automate Integrate Red Hat JBoss BPM Suite Red Hat JBoss Developer Studio Portfolio Edition Web Framework Kit Application Platform Web Server Data Grid Portal Fuse Red Hat JBoss A-MQ BRMS Red Hat JBoss Fuse Service Works JBoss Operations Network JBoss Community or JBoss enterprise Red Hat JBoss Data Virtualization
SolutionsWhy Red Hat Why open hybrid cloud? The new IT Public cloud Cloud resource library Private cloud Infrastructure-as-a-Service (IaaS) Platform-as-a-Service (PaaS) Cloud applications and workloadsSolaris to Red Hat Enterprise Linux Migration overview Migrate from your UNIX platform How to migrate to Red Hat Enterprise Linux Upgrade to the latest Red Hat Enterprise Linux release JBoss Enterprise Middleware Benefits of migrating to Red Hat Enterprise Linux Migration services Start a conversation with Red Hat
TrainingPopular and new courses Red Hat JBoss Administration curriculum Core System Administration curriculum Red Hat JBoss Middleware Development curriculum Advanced System Administration curriculum Linux Development curriculum Cloud Computing, Virtualization, and Storage curriculum
ConsultingSOA and integration Business process management Cloud and virtualization Custom Software Development Enterprise Data and Storage Systems management Migrations
Driving Developer Preference
April 24, 2007
by Shaun Connolly
The success of JBoss has hinged on grassroots adoption by developers and users of our open source technologies. Thank you for your support over the years! With our relaunch of JBoss.org, we are hoping to fuel that innovative spirit further and keep our users informed and excited about our new technologies and directions.
There are many types of developers, of course. While many will download our open source components and tools and support themselves via our forums and wikis, many corporate developers just want a set of solid tools they can use and a well tested platform to develop and deploy on. While they may think innovation is cool–and will factor it into future applications–stability is what gets deployed today. They have a job to do and want vendors like Red Hat to make their lives simpler.
At Red Hat, we are focused on driving preference for our Open Source Architecture as early in the development lifecycle as possible. So, we are building on the grassroots relationship JBoss has with developers and consolidating our developer-related efforts into a single strategy across all of Red Hat.
Towards that end, we have launched the following new subscriptions:
- Red Hat Developer Professional is designed for corporate developers and individuals.
- Red Hat Developer Enterprise is designed for Independent Software Vendors, larger development organizations and mission critical development projects.
- Red Hat Developer Studio is an Eclipse-based development tools environment that integrates tools for Linux, Java, and Web 2.0 application development.
The first two offerings provide full access and developer support for ALL Red Hat certified products (Red Hat Enterprise Linux, JBoss Enterprise Middleware, etc.) under a single subscription. We want to make it as easy as possible for developers to get access to any/all of our certified bits and support them in the use of those bits as they’re developing their applications.
The Developer Studio subscription is due out in the summer timeframe and will integrate all of our Eclipse-based tools, including the Exadel Studio Pro and Ajax technologies, into a development environment that works well with and includes our certified platforms. So, developers will not only get the tools but also access to our certified Red Hat Enterprise Linux and JBoss platforms.
This is a first step, of course, and as always, if you have cool ideas of other things we should be doing to help developers, let us know.