I’ve decided to keep the default title the WordPress gives to the post it autocreates on new installations. I think it’s fitting; what better way to signify the conversion from BlogEngine.net to WordPress?
But first things first.
In the beginning…
… there was me, being web unsocial [sic]. Then, I thought to myself “wouldn’t it be nice to have a blog to share occasional bits of useful information that I might encounter”? It was rather common for me to want to share a solution to an obscure problem (that wasn’t mentioned or properly analysed elsewhere on the internet), or share a library that I had developed, or even voice an opinion on a matter.
Being a .net developer first and above all, BlogEngine.net was the natural conclusion at that time. And admittedly, it served me rather well, albeit with a few minor problems.
The need for a change.
There was something that bugged me for quite some time. Having worked on so many WordPress applications for clients, I began to appreciate the platform gradually shifting my initial impression about it. That got me thinking “why did I really choose into BlogEngine.net in the first place?”
Was it performance? Initially yes (even without precompilation, BlogEngine.net was faster than WordPress), but then the Quick cache plugin solved that matter.
Was it the “.net”? Again, initially that was true. I wanted to contribute to the new .net project and help with its growth. Oh, and while at it, develop something clever on it and combine it with our other projects. Then I discovered that my time is limited and my blogging is sparse, so there goes that idea.
Then I thought that “You know what? Upgrading was a bit of a pain. And what about the authoring text box? It’s so small, I had to zoom in with the browser. Not to forget to mention some issues with the themes: few choices and the ones I liked were not compatible with the latest editions. Then I had to combat spam and my choices were again limited and so on…”
While the saying goes that “the grass is greener on the other side of the fence”, in this case that was a reality. WordPress has solved most of these problems primarily by maturing enough through the years and by having a large community that provides solutions to almost every aspect of it. Need spam protection? Bam, you have a ton of different options. Image galleries? Check. Lots and lots of themes? Check. And so on…
Where to from now?
You might assume from the above comments that I don’t like (or even that I despise) BlogEngine.net. That would be far from the truth. The project has gone a long way since the days I tried it and support is growing stronger. As a .net developer, I wish them the best of luck. However WordPress is a far more mature project and admittedly easier to use. It covers 99.9% of my and my clients’ needs and in the end that’s what matters.
At this point, I’m counting my “losses”. I’ve lost all my comments (they were hosted by Disqus and I don’t want to implement it here), my tags and my images. Most posts are here and the formatting is preserved with no issues.