Ask HN: Should I go for higher pay, older technology job offer?

I did that move many times in my 8 years in the enterprise field(I hold MCP, MCAD, MCTS), I won't be surprised if you have to work with more than just an old version of .NET. The PC market is full of legacy stuff, you go back to work with those .NET2.0-ish people and you end up by dealing with VBScript, COM+, ASP, VB6 and stuff like that. I personally think that you will not be entirely happy in an enterprise environment, so I would work with other more interesting technologies in my free time.<p>Also, for personal experience, take in count that companies working with old technologies rarely want to sponsor certifications for newer version of the platform(forget about C# 5 free exam vouchers) since their ".NET 2.0" infrastructure is working "just fine".

The age of the technology is not the same thing as the quality of the infrastructure. I wouldn't judge on that regard. However, the upgrade from .NET 2.0 is not difficult, in sane situations, so there's a question of what's going on there.

Think long term, would you still have fun with older tech in 2 years?

Would the new company be open to using newer technologies in the future, or at least in house?<p>I'd say go with the new job since change is good, and commutes are a killer.