4 ms·

Wow, thanks, Guys. If I were still working on that project I'd probably pick your brains a bit more. And, I think that you hit the nail on the head about ab

Wow, thanks, Guys. If I were still working on that project I'd probably pick your brains a bit more. And, I think that you hit the nail on the head about abstracting everything out for me. In the short ammount of time, I just couldn't grokk it, but I knew I didn't like it. It seemed like ASP.NET was a purposefull movement away from typical web development. And, I'm sure that Microsoft was trying to fix problems that they say with typical web dev. I just think that there are better solutions out there than ASP.NET. But, if you're a windows guy and used to coding in Visual Studio, and you can already use the languages that you are used to, it might be a really good idea.

hello_moto 19y ago
Better solution depends largely on how your brain works. Some people brain map better with LISP, some work better with OOP/Java.
johnb 19y ago
I found that ASP.NET was a good stop off point between writing desktop apps and writing web apps. All the event handling logic and the postback thing meant I could bring most of my desktop thinking across and be productive immediately. The problem I had was once I had been working on the web a while I realised the abstractions were broken but the framework didn't leave me anywhere to go.