Will the monkey ever catch up?

Note: this entry has moved.

Disclaimer (as if I need it): Although the following may sound like a rant, it is *not* a rant.

A few weeks ago I heard that Mono’s ASP.NET implementation is considered feature complete, which is great news. But Microsoft’s ASP.NET implementation is out since Feb. 2002, which means the ASP.NET team is working on v2.0 since -approximately- two years now. This looks like a considerable gap to me. I mean… while coding M1 of Mono’s ASP.NET Whidbey has just started, Microsoft is about to publicly launch Whidbey first beta; can you see the gap now?

While I was writing an article about ASP.NET Whidbey’s WebResource feature I decided to take a quick look at Mono’s Whidbey code to see how they were implementing this feature and possibly comment about it in the article. Nothing ever made into it because there was only a skeleton AssemblyResourceLoader.cs file with an ultrasimple implementation that wasn’t worth mentioning (it was missing key features like caching, security, ect). This, by the way, is totally understandable as Mono work on Whidbey has just started but I’m citing this just as practical example that a (considerable) gap exists.

To get an idea of when the Mono team plans to release an ASP.NET Whidbey implementation you can look at their roadmap. Scrolling down to title “Mono 1.2” you can read things like “…ASP.NET 2.0 improvements…” and “…This release will by default provide .NET 1.2 APIs...”. It is pretty clear by now that the next Mono version (v1.2) will try to provide the same feature set as Microsoft’s Whidbey (currently named version 1.2 and probably renamed to version 2.0).

No very big surprises up to here. When this Mono v1.2 will be available? The roadmap says “…Release target: Q4/2004…”. Ex-cu-se me?!, do you mean the fourth quarter of 2004?!, one year or less from now?! Wow… now that’s just sounds like an impossible goal. Want to bet?

And lastly… why in the world isn’t the Mono Official Website running on Mono’s ASP.NET? Is it just that they don’t like to eat their own dog food?

 

4 Comments

  • Consider one thing: Microsoft's work with ASP.NET 2.0 is as much research as development. You can see from different remarks that the ASP.NET PM's made that they have tried different options, looked at different issues, and developed up many alley's before coming up with the final ASP.NET implementation. Whereas Mono simply needs to implement what Microsoft has researched. Following tail-lights is a lot easier (and faster) than blazing a trail.

  • Chris: Even considering your point I still believe the planned date will be really hard to hit. Also, this brings up another point I had in mind but forgot to post: Is Mono about only cc .NET? I mean, zero research? zero innovation? I don't believe so; I know they've experimented in some areas (attributes handling, ect) with different results.



    Jeff: Thanks for the posted link but it seems like its currently offline.



    Gabriel (who posted about this post but on the comment section of the previous post): I mostly agree with your points.

  • Mono are playing catch up, thats the very nature of implementing an existing product. Does that mean that Linux users wishing to use ASP.NET will lag behind windows users, maybe. However the work on Mono goes at a pace by those fearless folks who are working hard on it, the more folk that help out the faster that features and implementations will happen. Maybe as community rather than worrying about if it will happen it we should be helping make it happen.

  • Well, Mono's always been playing catch-up. After all, MS announced .Net once they'd actually got something people could download and use. Shortly after, Miguel started discussing producing a platform independent version. To be honest, I'm surprised they're as far along as they are. After all, they seem to have surpassed the open source Java implementations in terms of feature parity with the "real thing" (correct me if I'm wrong).

Comments have been disabled for this content.