At Innoveo Solutions we are using .NET and WPF for our Innoveo Skye® Editor application. Skye® Editor is a distribution channel editor targeting business people letting them edit and configure their insurance products.

From the beginning we have adopted the Model-View-ViewModel architecture. Having our solution growing we were facing the issue of having our ViewModels dependency growing too. Some ViewModel became too much dependent of others. This was obvious in our unit tests whose complexity to setup were growing too. It was time to find a solution to decouple the ViewModels.

The solution came out after a discussion with Laurent Bugnion, the famous author of MVVM Light Toolkit. At that time we used the V1 that already helped a lot in this decoupling.

Now with MVVM Light Toolkit V2 it is even better with the new Messenger API. What we also really appreciated in comparison to other frameworks is that it is really light and the ability to open and edit the user interface into Expression Blend.

So Thank you Laurent for this GREAT framework and I looking forward for V3!

I also would like to thank my managers at Innoveo Solutions who understand Open Source and the need to have people contributing to Open Source projects, even during their professional working time. A Win-Win situation and not just a one way benefit as often.

cross-posted on Laurent Kempé’s blog

VMware announced on August 10, 2009 its willingness to acquire SpringSource for $362 million in cash and equity, plus $58 million of unvested stock and options (press release). The process should be closed in Q3 2009.

How can this acquisition be interpreted? What are the goals of VMware/SpringSource?

Some interesting inputs and analysis found on Internet.

A post from Rod Johnson, CEO of SpringSource

About the merge itself

[…] We have signed a definitive agreement with VMware, who will acquire SpringSource. Subject to regulatory approval, we expect the transaction to close in Q3. SpringSource will become a division within VMware. I will continue to lead SpringSource, reporting to VMware CEO Paul Maritz.

About the opportunity

[…] But the broader transformation in IT goes beyond Java frameworks, tooling and runtime infrastructure. The way in which people think about software stacks is changing. Virtualization is reshaping the data center, and cloud computing is set to drive far-reaching changes. Significantly, cloud computing blurs the division between development and operations, bringing new power (and responsibility) to developer.

And so the question becomes, what is the most simple, powerful, pragmatic way of utilizing SpringSource technologies in the data center, and in the cloud?

About the vision

Working together with VMware we plan on creating a single, integrated, build-run-manage solution for the data center, private clouds, and public clouds. A solution that exploits knowledge of the application structure, and collaboration with middleware and management components, to ensure optimal efficiency and resiliency of the supporting virtual environment at deployment time and during runtime. A solution that will deliver a Platform as a Service (Paas) […]

About the vision (said in other words)

The next chapter of our work at SpringSource is tackling those challenges: Building on our Build/Run/Manage solution to provide the industry’s best solution from developer desktop to cloud deployment. Bringing Spring’s power and simplicity to enabling the millions of Java developers to benefit from the full power of cloud computing. […]

About the representation of this vision

About the open source community

Our commitment to open source practices, licenses and traditions will remain unchanged. We expect our contributions to open source to increase. Our open source projects will retain their commitment to enabling user choice. Spring will retain the portability between deployment environments that empowers users. […]

An analysis from 451 CAOS Theory

Part I

[…] VMware is clearly in need of a story beyond virtualization, even if we are still relatively early on in enterprise adoption. Still, looking into the future, it sees clear skies, and that does not fit with the multi-billion dollar opportunity shaping up in cloud computing. Thus, VMware is willing to invest a significant amount in SpringSource, which does represent a crossover in customers without much, if any, crossover in competition.

Part II

VMware is working to address its increasing competition from all sides. While it may seem somewhat odd for VMware to want to get involved in enterprise Java application development and deployment, it may want to take advantage of SpringSource’s relatively quick climb in the enterprise Java development and support business. VMware may also be looking to offset any gain in enterprise Java influence and control by Oracle, which may do so with its more than $7 billion acquisition of Sun Microsystems.

Part III

VMware is also facing increasing competition from OS vendors, including Microsoft, Novell and Red Hat, which is among SpringSource’s biggest competitors with its JBoss business. Again, SpringSource may not seem the most likely suitor for Java application development, but VMware may see this as an area where it can most effectively integrate its own technology and talent to differentiate in virtualization and cloud computing.[…]

Open source?

Although SpringSource’s open source nature has been critical to its developer reach and success, this is likely not as important to VMware, which may view SpringSource more as a subscription software company than as an open source software company. Either way, it seems VMware, similar to Oracle, may have somewhat limited vision when it comes to open source software, seeing it for its development and time-to-market advantages, but missing other community benefits — including user and customer communities, feedback and contributions — that help make things work.[…]

Disclosure: Innoveo Solutions is using Spring in its Innoveo Skye™ software product.

cross-posted on Didier Beck’s blog.

I am very proud to announce that Cédric Walter, one of our colleague and founding member of Innoveo, is nominated to the EOS Directory (Enterprise Open Source Directory) Advisory and Expert Board. Cédric is a very well-known contributor of the Joomla community since 2004.

EOS Directory is a great catalog of more than 350 open source projects, that are listed, described and analyzed. It is today the leading online platform to help enterprises and organizations identify and evaluate Open Source technologies. Initially launched by Optaros, about two years ago, the platform has been recently handed over by Bruno von Rotz, initial sponsor of the initiative, well known Open Source specialist, and one of our Innoveo Board Member.

In support to strengthen the neutral approach to ratings and selection of the technologies, the new EOS Directory Advisory and Expert Board has been established over the last weeks.

The Advisory and Expert Board will be both instrumental in guiding the future development of the EOS Directory Platform as well as in making sure that the content is accurate, relevant and fairly represented. (Source: EOS Directory Blog)

Congratulations to Cédric!

More Information on Cédric’s blog and the EOS Directory blog.

Cross-posted on Didier Beck Blog.

via 451 CAOS Theory

Great post about some impressive figures from the Linux kernel development.

• There have been almost 10,000 patches in each recent quarterly Linux kernel release.
• Releases include work from ~1,000 developers and ~100 companies.
• Since 2005, Linux has had more than 3,600 individual developers and more than 250 companies contributing to the kernel.
• The individual development community has tripled in the last three years.
• The top 10 developers have contributed 15% of changes, and the top 30 developers have contributed 30% of changes to the kernel.
• Linus Torvalds is 27th on the list of contributors with most changes over the last few years. He has 495 to his name.
• More than 11,500 or 14% of kernel changes have come from developers with no commercial entity backing their Linux development.
• Another 13% of changes come from developers with ‘unknown’ commercial affiliation.
• When we get to actual companies, Red Hat leads with 9,351 kernel changes, or 11.2%. Next is Novell with 8.9%, IBM with 8.3% and Intel with 4.1% of kernel changes.
• More than 70% of all kernel development is demonstrably done by developers who are being paid for their work.
• From the 2.6.11 kernel to the 2.6.24 release (1,140 days), there were an average of 2.8 accepted patches applied to the Linux kernel tree per hour.
• An average of more than 3,600 lines of code is added to the Linux kernel tree every day.
• Since 2005, the kernel has grown at a steady rate of 10% per year.

Gosh, if this is not showing the incredible health and dynamism of the Linux community!

cross-posted on didier beck's weblog.