Tracking change and innovation in the enterprise software development community
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Free Book Offer
SOA Demystified
$40 Value
Posted by Jonathan Allen on Oct 31, 2007
Historically JavaScript compatibility has been a major problem for web developers. Variations between the official spec, the de-facto standard, and the various implementations have kept many a developer up all night. The end result is that many web pages don't work equally well, or at all, across browsers.
Microsoft's JScript team, keenly aware that they are part of the problem, write:
The point is that JavaScript developers shouldn’t have to detect and workaround such issues. JavaScript should work the same across all implementations. We believe this is the first step in making JavaScript better.
To make it possible to achieve such implementation conformance, the first step is knowing where the divergences are. We in the JScript team are looking into where various browser based implementations diverge, where our engine is incorrect in its interpretation of the specification, what if any de facto compatibility conventions have been reached, and the value of codifying such conventions into the standard. We’ve published the first draft of JScript Deviations from ES3 as a starting point.
The document's title, "JScript Deviations from ES3", is a bit of a misnomer. This document covers not only IE, but also the JavaScript implementations found in Firefox, Opera, and Safari. This is an in-depth study of the spec with a point by point comparison between what is suppose to happen and what actually does, for all four browsers.
Innovation in Your Data Centre
Right Collaboration Architecture Drives Business Transformation
Agile Development: A Manager's Roadmap for Success
The 5 Mandates of Software Development Teams - Presto Manifesto
What an ugly document. I don't think they used word 2007 to write this. Where the pretty new fonts? Where's Consolas? I was hoping to never have to see Courier New ever again. And no syntax highlighting?
Kvetching aside, seeing a document like this come from MS is a dream come true. Now they can continue this excellent trend by... releasing fixes for all of these problems in SP3 for XP and SP1 for Vista!
Kudos for Microsoft for taking a cooperative attitude here. Even better if it leads to real change.
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
2 comments
Watch Thread Reply