Will Open Source Lose the Battle for the Web?

snotty writes "A well written article by Ganesh Prasad over at linuxtoday arguing that the shift towards web services has reduced the attractiveness of the current generation of Open Source web products. He talks about the market share decrease in Apache. Also mentions how .NET, Microsoft, Sun, Java, and Open Source Software fit into the picture." I think that the decrease in Apache's share is a red herring, but the bigger picture of web services is a troubling one.

Comments

Re:The process of natural selection

[KlomDark]

WTMFH are you talking about? You get access to the Kernel and you're basically ROOT. And you say that's NOT a security breach? What's that you've been smoking? Give me direct access to kernel functions and see if you don't have a security breach on your hands.

Who's the troll here?

Worm food.

[jcr]

Apache's "market share" is irrelevant. There are plenty of people working on it, and tech support is incredibly easy to come by on IRC, USENET, or Linux users group.

What IS worrisome, is *any* increase in the number of IIS installations. This shit is just too dangerous to have on the net as a springboard for the next bit of malicious code. We need to start polling web servers, and treat any IIS instances that respond just like we treat open mail relays.

Any authors of web browsers out there, add a feature: if the browser hits an IIS server, it should automatically send a note to webmaster@clueless.newbie.still.running.iis.com, and tell them to switch to a securable web server RIGHT NOW.

-jcr

Re:Web services...

[MSBob]

Allright. Maybe PHP won't be optimal for the most demanding web applications but surely servlets and JavaBeans (as opposed to EJBs) should nicely do the trick. What does EJB offer that you can't get with plain servlets and beans? Clustering of your application boxes can be accomplished with tomcat. No need for stupid EJBs.

I used to work almost exclusively with CORBA which is over-engineered but at least it made sense as we had to interface lots of legacy code. But EJBs tie you to Java exlusively so integration with the legacy stuff is no longer so simple. What good are EJBs then? Everything they offer can be accomplished through simpler and more efficient solutions.