The Web Developer Extension (Beta 0.9.9)
U.S hegemony on software, even on Open Source
Lisbon Agenda and Open Source
Paul Everitt, Zope Europe Association
The EU's Lisbon Agenda calls for European planning to produce the world's leading knowledge economy by 2010. Indicators show, though, that U.S. hegemony is increasing in the primary software sector. Even FLOSS seems to start in Europe and finish in the U.S.
Via the
Silent Penguin
See the
presentation
and
Paul's blog postUdell about user innovation and the evolving bazaar
I put these two excerpts side to side because I think that
Jon demonstrates here something which got missed in the whole open source = proprietary discussion. It's not about the source, it's about how your users (I don't like that word though) get the most value out of a software.
Open source is a big leap forward and had the benefit of changing how we looked at software and software companies. But as long as the software was used as product - on the client's server - the benefits for the user were still marginal.
With software as service and the "network" model, the value for the user is much higher. Naturally not all problems are resolved yet, but the steep improvements and the extraordinary blossoming of cool (software) projects (
Del.icio.us,
Flickr,
Google Maps,
Audioscrobbler/last.fm,
Odeo to name but a few well known ones) in the last two years let's me get quite excited about future developments.
User innovation toolkits and continous improvement
Discussions of software as a service tend to focus on its obvious benefits: zero-footprint deployment and seamless incremental upgrades. Less noticed, but equally valuable, is the constant flow of interaction data. The back-and-forth chatter between an application and its host environment can be a drag when connectivity is marginal and it precludes offline use. But when this communication flows freely, it paints a moving picture that shows how individuals and groups are using the software.
The changing cathedral and the evolving bazaar
The bazaar is learning that fit and finish, coupled with pervasive consistency, are worthy engineering challenges to which its tactics of open and scalable collaboration can fruitfully be applied.
Five hundred years ago the cathedral and the bazaar were divided cultures. But this network we're all building and using is a machine for cultural transmission and transformation. So I regard nothing about past behavior as a certain predictor of the future.
Open Web = Tinkerability
Joe Kraus from Jotspot: There's been a lot of hype around open source, and there are people who believe that open web means open source and anything less than open source is not open web. I don't believe this. Open source is a really important movement—it's powerful in many ways, and we certainly benefit from it and contribute to it—but there are also a lot of interesting examples of late that take a different view of open web. These examples point to open data, not open source.
Take Flickr: Its code is closed, but there are enough APIs in and out of it that you have this tremendous ability to tinker, even if you don't control it. JotSpot, too, is very much an open-data-style service. Just as with Flickr, there are tons of APIs in and out. You can manipulate content inside of JotSpot even if you don't have source-code control.
To me, open web really refers to how tinkerable it is. It's really a spectrum of tinkerability. Some people believe the only way you can tinker is via open source, but I believe the new trend (especially in web-based services that are hosted by somebody else) is to facilitate tinkerability even without open source. That's why I think Google is not actually totally closed: They offer APIs into their service. Now, they could offer more ...
And is the shift due to the
shortage of big open source thinkers?
Anyway if you have ideas to make KAYWA weblogs more tinkerable, let me know.