Software Trends : Open Source

I just happened to reach Burnham's Beat, a wonderful blog on software tech and investing, via emergic. In his series of Software's Top 10 2005 Trends, Bill writes on Open Source:

One of the biggest questions facing the software industry in 2005 is whether or not Open Source will “jump the species barrier” and start to become a major factor in the enterprise applications space. A quick look at Sourceforge confirms that to date most Open Source efforts in the applications space have been confined to niche applications in the academic space, but there are now numerous efforts underway, such as SugarCRM, to try and create enterprise-ready Open Source applications. Whether these applications efforts are successful or not is one of the key issues keeping software company executives up at night.

For software executives, Open Source presents three major choices: beat it, join-it, or co-opt it. The conventional wisdom suggests that the way to beat Open Source is to “out-engineer” Open Source by providing a more stable, secure and feature rich product while at the same time “out-servicing” Open Source by providing robust 24/7 support.

Comments

Gmail Chat Disabled

The fact that it happened does not surprise me but that it took so long for our network administrators to figure it out does. And if you are wondering how do you disable Gmail's chat features on your network, you only need locking DNS lookups to chatenabled.mail.google.com , by returning 127.0.0.1 .

Advertising Billboards as Rain Covers

Advertising billboards are put to use as Pakistani refugees, left homeless after the October 8 earthquake, set up their tents in Muzaffarabad, Pakistan. [via SFGate ] Technorati Tags: Pakistan Earthquake

Community effort to create a single persistence model for the Java community

A community effort led by Sun Microsystems is aiming to create a single 'Plain Old Java Object' persistence model to provide a single object/relational mapping facility for Java app developers in J2SE and J2EE. Paul Krill writes In a letter to the “Java Technology Community” on Friday, specification leads on Java Specification Request (JSR) 220, which is the proposal for Enterprise JavaBeans 3.0, and JSR-243, for Java Data Objects, state that the two technologies feature divergent persistence models. “This divergence has caused confusion and debates among Java developers, and is not in the best of interest of the Java community,” said JSR-220 leader Linda DeMichiel who also is a Sun employee, and Craig Russell, a staff engineer at Sun who leads JSR-243. “In response to these requests [for an end to the unwanted divide], Sun Microsystems is leading a community effort to create a single POJO (Plain Old Java Object) persistence model for the Java community,” the letter said.

enginerd

Search This Blog