Jesper Boeg on Priming Kanban
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jon Rose on Oct 29, 2007
Prism is an application that lets users split web applications out of their browser and run them directly on their desktop.The Mozilla Labs’ posting compares it to Adobe AIR and Microsoft Silverlight:
… Prism isn’t a new platform, it’s simply the web platform integrated into the desktop experience. Web developers don’t have to target it separately, because any application that can run in a modern standards-compliant web browser can run in Prism. Prism is built on Firefox, so it supports rich internet technologies like HTML, JavaScript, CSS, , and <canvas> and runs on Windows, Mac OS X, and Linux.
Unlike Adobe AIR and Microsoft Silverlight, we’re not building a proprietary platform to replace the web. We think the web is a powerful and open platform for this sort of innovation, so our goal is to identify and facilitate the development of enhancements that bring the advantages of desktop apps to the web platform.Mike Chambers of Adobe Systems responded in his blog to the AIR comparison in the Prism announcement, wondering about the “proprietary” label when he perceives the two products as very similar:
And while Prism focuses on how web apps can integrate into the desktop experience, we’re also working to increase the capabilities of those apps by adding functionality to the Web itself, such as providing support for offline data storage and access to 3D graphics hardware.
You could describe Adobe AIR in exactly the same way (just replace Prism with Adobe AIR and Firefox with Webkit).Mike Potter of Adobe joined the conversation, noting that Prism helps to validate the AIR/Desktop model:
So, I guess the thing I found odd was Mozilla appears to be building something very similar to Adobe AIR (which is fine and cool), but somehow it is inherently good when Mozilla does it, and inherently evil when Adobe does it.
However, some similarities certainly exist, and its nice to see people acknowledging the same problems - its good validation for what AIR does.The Mozilla announcement concludes on a positive note for all developers, describing a goal the entire software community shares of ‘improving the usability of web applications’:
Prism is just the first of many experiments we hope to conduct around improving the usability of web applications. It’s open source, like everything we do, and we’re interested in hearing from and working with anyone interested in further developing this concept.Ultimately, the developer community will validate or invalidate the programming model and the vendors who are working to provide the platforms.
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
A practical guide to choosing the right agile tools
Mobile and the New Two-Tiered Web Architecture
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
1 comment
Watch Thread Reply