.NET technology stacks for web apps

[d000hg]

Personally on the Java side I'm quite happy using servlets+JSP/JSTL and writing DAOs so I don't fundamentally disagree about using new tech. On a small project I wouldn't use all that enterprise stuff probably unless I wanted to use it for the experience.

But as the last poster says, you have to be aware you're thinking this way lest you end up inflexible. You see people who refused to learn Java and JSP because C++/CGI or VB/ASP "worked just fine". It's a bit of a tightrope act to be open to new technologies without hopping from fad to fad.

[doodab]

Personally on the Java side I'm quite happy using servlets+JSP/JSTL and writing DAOs so I don't fundamentally disagree about using new tech. On a small project I wouldn't use all that enterprise stuff probably unless I wanted to use it for the experience.

But as the last poster says, you have to be aware you're thinking this way lest you end up inflexible. You see people who refused to learn Java and JSP because C++/CGI or VB/ASP "worked just fine". It's a bit of a tightrope act to be open to new technologies without hopping from fad to fad.

I'm lucky in that I usually have a lot of leeway to do things how I see fit. I do try to weave new things into what I'm doing as and when they appear to be useful and getting widely adopted, but I avoid jumping on every new thing that comes along, simply because I know 90% of it will fall by the wayside. Generally I decide whether something is worth my time based on whether it seems simple, well thought out and easy to get to grips with, and avoid anything that seems to make life unnecessarily complicated. I'm basically lazy.