Group items tagged

Consequently, it is not reasonable to expect us to make sound business or technical decisions on behalf of the customers, or to resolve conflicting requirements supplied by different end users, or to set priorities for the many requirements that might be collected.

We have finally reached the state where if no project champion can be found to see that the right system is built, we cancel the project.

The consequence of not explicitly discussing these quality tradeoffs is a surprise upon delivery, when the customer finds that his implicit quality attribute requirements have not been achieved

Everyone will benefit, even the Java community: Now that there's competition again, new constructs are—surprise!—again being considered for Java

Do languages have to sacrifice anything?

.NET goes much further: A routine written in a language L1 may call another routine written in a different language L2. A module in L1 may declare a variable whose type is a class declared in L2, and then call the corresponding L2 routines on that variable. If both languages are object oriented, a class in L1 can inherit from a class in L2. Exceptions triggered by a routine written in L1 and not handled on the L1 side will be passed to the caller, which—if written in L2—will process it using L2's own exception-handling mechanism. During a debugging session, you may move freely and seamlessly across modules written in L1 and L2. I don't know about you, but I've never seen anything coming even close to this level of interoperability.

Provide a hook for other view engines from MonoRail, etc

The default URL scheme will look something like this: /<RouteName>/<Action>/<Param1>/<Param2>

MonoRail is more than just the MVC part.  I wouldn't be surprised if MonoRail were refactored to take advantage of the ASP.NET MVC HttpHandler just as a means to reduce the codebase a bit.