--- Steve Jones <[EMAIL PROTECTED]> wrote: > > 5. Create tools that help people reach data agreement. That's > always > > been the real problem. Go nuts... collaborative tools, modeling > tools, > > semantic tools, development tools, user tools, repositories. > > Its been part of the problem , data semantics are a challenge, but > function semantics are a much bigger one. Agreeing on what data > pieces mean is trivial (IME) in comparison with the meaning of > interaction.
Sounds reasonable. > > 8. Languages, frameworks, and tools must robust in the face of > change > > and indeterminacy. Static typing and code generation are > brittle. > > I'm still REALLY not convinced on that one, mainly because my > background is Ada and Eiffel and I worry about system maintenance as > much as development. Static typing for me is a very good thing, > paticularly when trying to cope with change. Code generation can be > a > problem, but isn't always, and dynamic models are often complete pigs > to debug. Without getting into a type system argument, I completely agree that *strong* typing is a very good thing. I think there's room for innovation in how one also enables low cost evolution and change of a type. > How about another option? Lets try and commoditise the hell out of > the infrastructure and develop a new mechanism which works at the > enterprise and application level, rather than trying to optimise what > a programmer does why not optimise the project? Sounds good to me! In fact, from my perspective, is the difference in emphasis between a network hypermedia-based information system and a message-exchange based system, when the goal is integration. Hypermedia about commoditizing the infrastructure into universal agreements and working at the level of information pervasively across the infrastructure, from presentation down to processing logic, subject to certain architectural constraints. Message-exchange systems are about providing composable protocols & tools for programmers to create a system that will do the former under almost any scenario. Anyway, Gervas' question was about what can vendors do to promote REST developer's prod included it because many arguments about integration tend to involve the developer's perspective, even though the overall priority is not to optimize their experience, but to share information globally. Cheers Stu ____________________________________________________________________________________ Cheap talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. http://voice.yahoo.com
