VMware Infrastructure 3 Book Excerpt and Author Interview
VMware Infrastructure 3: Advanced Technical Design Guide and Advanced Operations Guide provides a wealth of practical insights into setting up virtualization in todays corporate environments.
Tracking change and innovation in the enterprise software development community
Posted by Jon Rose on Oct 03, 2007 08:29 AM
Ted Patrick of Adobe Systems has been blogging over the last week on some of the exciting new additions and improvements coming in the Beta 2 release of Flex 3. He finished Monday, announcing the most noteworthy change for developers considering the adoption of Flex, a price drop for the Flex Builder IDE.Flex Builder 3 will ship in two editions: Flex Builder 3 Standard edition ($249 US) and Flex Builder 3 Professional edition ($699 US). Additionally on Nov. 1, we are repricing Flex 2 to align with Flex 3 and providing support upgrade options for Flex 3 starting at $99.
Flex Builder 3 Beta 2 has a new feature for generating server side code for data exchange with ASP.NET, PHP, and JAVA. Simply select a database, select the tables you want to edit, and presto, full CRUD, Create, Retrieve, Update, Delete.
To top that, we added WDSL Introspection to allow you to work with Web Services using Strong typing.
The first changes target the code navigation and are extensions/refinement around language intelligence (refactoring, search, code model). To enable this feature simple hold down CTRL and click on any property to navigate into its definition. We supported this before but now you can navigate seamlessly into the Flex SDK codebase for any class, property, style, or event.
The profiler is such a key addition to Flex and these refinements really make it essential. There is nothing worse than a profiler that points you in the wrong direction and the team has made some essential changes in how memory and performance are measured to make what is happening in your application clear.
Scale your applications without punishing your database
Spring App Platform, Java Concurrency/Multicore, Eclipse Mylyn and more @ QCon SF Nov 19-21
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
Introducing application infrastructure virtualization and WebSphere Virtual Enterprise
Guide to Calculating ROI with Terracotta Open Source JVM Clustering
When you write "...The Eclipse based development environment is the key tool for building Flex applications...." I must disagree. FlexBuilder2 (and v3 I think) is NOT supported on linux. But you can do flex development without it, and without much hasle. Simply compile with the maven plugin from israfil (http://www.israfil.net/projects/mojo/maven-flex2-plugin/index.html). Edit sources with your favourite xml/javascript editor. Then, all is free...
Just saw, that v3 has an alpha version of a plugin-only release of the builder for linux. Neat!
Yeah, the Linux support is good news; that was a stumbling block on adoption for us.
Flex Builder is still to expensive. If Adobe really wants developers to pick up flex, they need to bite the bullet and give the development tools away for free. (think eclipse/netbeans) This will do 2 things: 1) encourage people to try out flex development (since there is no cost) 2) increase adoption in IT organizations since it will be easier to find people who know how to develop flex apps. Adobe needs to learn that designers and developers are two different breeds.
Flex Builder is still to expensive.
If Adobe really wants developers to pick up flex, they need to bite the bullet and give the development tools away for free. (think eclipse/netbeans) This will do 2 things:
1) encourage people to try out flex development (since there is no cost)
2) increase adoption in IT organizations since it will be easier to find people who know how to develop flex apps.
Adobe needs to learn that designers and developers are two different breeds.
Yeah, but then Adobe becomes left with no revenue stream off of Flex.
When I evaluated Flex for use in a new product, the cost of the Builder and Charting package was not a factor. The fact that Flex was far superior to all of the alternatives we considered (and prototyped with) was.
Naturally we wanted to use the best RIA technology that has a wide uptake in order to achieve a high quality product.
VMware Infrastructure 3: Advanced Technical Design Guide and Advanced Operations Guide provides a wealth of practical insights into setting up virtualization in todays corporate environments.
Can a system that is so large it cannot be comprehended be "designed" in a conventional sense? The foundations of computing are about to change. In this talk, Richard P. Gabriel explores why and how.
Ruby 1.9's Fibers and non-blocking I/O are getting more attention - we talked to Mohammad A. Ali of the NeverBlock project and Tony Arcieri of the Revactor project.
Tim Mackinnon talks about the aspirations behind the Agile principles and practices, the desire to become efficient, to write quality code which does not end up being thrown away.
Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.
Often the hardest part of changing technologies is language syntax differences. This new article provides Java developers with a transition guide to Actionscript which forms the foundation of Flex.
Neal Ford talks about having multiple languages running on one of the two major platforms: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.
David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile consists in finding ways to implement its principles.
5 comments
Reply