Posts tagged `Web 2.0`

Andrew Keen has no idea how open models work.

In his latest article, he pontificates that the recent economic downturn is a death knell for community-supported or community-built programs/sites/&c.

So how will today’s brutal economic climate change the Web 2.0 “free” economy? It will result in the rise of online media businesses that reward their contributors with cash; it will mean the success of Knol over Wikipedia, Mahalo over Google, TheAtlantic.com over the HuffingtonPost.com, iTunes over MySpace, Hulu over YouTube Inc., Playboy.com over Voyeurweb.com, TechCrunch over the blogosphere, CNN’s professional journalism over CNN’s iReporter citizen-journalism… The hungry and cold unemployed masses aren’t going to continue giving away their intellectual labor on the Internet in the speculative hope that they might get some “back end” revenue. “Free” doesn’t fill anyone’s belly; it doesn’t warm anyone up.

There are really two broad fallacies that need addressing here. The first is Keen’s use of the word “open source,” which here is a misnomer. He never mentions Linux, Apache, or other open source programs which always have and will continue to have a dedicated base of programmers, most of whom work on it in their spare time, without any remuneration except personal pride and the esteem of their peers. It need hardly be noted that an economic downtown is likely to increase interest in open-source software, as it likely reduces operating costs for businesses.

Read more…

§2907 · October 22, 2008 · 1 comment · Tags: , , , , , ,

Internet Explorer

Firefox

Safari

I personally think the friendly rivalry between the open-source Webkit engine (which powers Safari, among other things) and Mozilla (the Gecko engine, actually) is one of the best things to happen to browser development in years. The constant one-upsmanship can only lead to better browsers. Well, Internet Explorer will constantly be the limiting factor, but we can dream, can’t we?

The latest thing to hit browser source repos is javascript engine improvement based on something called “trace trees”: essentially, javascript gets translated into native bytecode. The Webkit engine made the announcement a few months ago, with code codenamed “Squirrelfish,” promising massive improvements. That article’s also got a pretty good writeup.

Open Source being what it is, it was only a matter of time before Mozilla announced their own version of a trace-tree-based javascript engine. John Resig has a good writeup, as done Brendan Eich.

Read more…