Jelle Druyts

If you're wondering why the blog and the website aren't written in ASP.NET - since I'm claiming to be a .NET consultant - then I must admit you have a point. Basically I've been using WAMP (Windows/Apache/MySQL/PHP) for quite some time already and I must say like the combination. I've been using it for all my personal web projects actually. But I've really been missing the coolest ASP.NET features lately: debugging, code-behind, OO, IntelliSense, ... in an integrated development environment. And I'd sure like to try out BlogX or whatever cool .NET blogservers are out there.

But still I stick to my WAMP. Why? Because it prevents a knowledge-lockin. What good is knowing an architecture if you can't compare it to others? I was new at html and scripting so I picked up a copy of Apache and PHP and built some sites. I learned about Java and acknowledged the power of OO. I came across .NET and loved its richness and power. But I never dropped anything else - maybe just diminished attention to it. So sticking to this legacy stuff keeps me awake - keeps my edge.

Any Windows programming I do however has been in .NET for a long time now, I really don't miss VB6 at that