+972 52-548-6969
Asp.net on steroids
time to read 1 min | 151 words
Eber Irigoyen replied to Jeremy's and my testability posts:
Jeremy Miller started a conversation on .NET testability (or the lack there of), Ayende agrees with him. I can definitely see this, I have suffered from this... but!
I don't think the problem is with the tools, in any case the problem would be of the TDD community, Ruby on Rails is open source, why can't we create asp.net on steroids?
seems like we know exactly what we want, the concept is there, the code is there, just needs to be implemented in .NET
I don't think the problem is with the tools, in any case the problem would be of the TDD community, Ruby on Rails is open source, why can't we create asp.net on steroids?
seems like we know exactly what we want, the concept is there, the code is there, just needs to be implemented in .NET
One word: MonoRail
Comments
I haven't looked at that, how is that project going?
There is a strong community behind it, and I am starting to see more and more people using it.
I think that the overwhelming majority of the .net developers don't see open source or, more genericly, non-MS offerings with the same appeal level that other developer communities see.
It's just a sad part of or history to wait and only use what comes out of Redmond.
I side with you on many of your opinions and I admire people that embrace community-driven solutions, like MonoRail, NDoc, and NHibernate, to name a few. But I don't see a lot of hope that any of these tools, as great as they really are, can ever achieve a critical mass compared to any half-baked alternative with the MS stamp on it.
As much as I like ASP.NET (I honestly do), I find it surprising that there's no other .net-based web framework that is not built on top of asp.net. I know it would be a monstruous task to dismiss System.Web.UI but we see many of these alternatives in the J2EE/Apache side and even RoR to some extent.
@Sergio,
MonoRail threw out the entire System.Web.UI stuff.
The ASP.Net internals stuff are beautiful, extensible, performant, etc.
There is a big distinction between ASP.Net and WebForms. I don't think that I can say a bad thing about ASP.Net itself.
Comment preview