This quote about Oslo & SOA is over the top:
Because the software infrastructure that supports your business
model is not based on some gobbledygook that only the guy with the pocket
protector and horn rimmed glasses understands. The software that supports your
business model is based on models and these models are aligned with business
capabilities that bring value to the organization and these models are also
aligned with standards based, interoperable and reusable webservices that
represent your software infrastructure.
Puh-leeze. Only uber-”pocket
protector and horn rimmed glasses” guy is going to be capable of utilizing Oslo effectively to create that clean business facing language in the first place. And again, only the geeky programmer is going to have the slightest clue about how that spiffy new DSL is actually translated into real functionality. Having a “Model” that’s just a lump of data isn’t all that useful. Something has to actually make the “Model” be executable, and I nominate the guy with the pocket protector.
Oslo potentially == a new way to integrate external DSL’s into the .Net ecosystem != non-programmers “writing” software. Let’s set our sights just a little bit lower. Just being able to write code that closely reflects the business domain is a huge win. Getting business experts able to write the actual code, even in a DSL, isn’t going to happen.
C’mon here. I’m very interested in Oslo too, but I can’t see any way in which Oslo is a game changer.