Blog Software in the .net world – still sad

I blogged in November 2007 about Open Source and .net, also talking about blog software. While I am happy to report that the general landscape looks a lot nicer now in April 2009, I am still sad by the state of blog software.
Back in 2007, I complained about complicated setup processes, the inability to run in common configurations (aka. “Medium Trust”) and generally low quality. 3 Weeks ago, I’ve had to setup another .net blog, so I looked at the landscape again.

It has improved. But not that much. Software like WordPress is still miles ahead, and I am not even talking that much about functionality here. I’m talking about some fundamental things like ease of installation. Or about the fact that Settings in the WordPress Control Panel are actually *explained*. Or the fact that I can put in RAW HTML into my postings WITHOUT WordPress destroying it. Sure, if I switch between WYSIWYG and HTML View, there may be a breaking conversations when using funky HTML, but if I stay in HTML, it just works. If I put in Garbage, then WP will output garbage.

I’m not even talking about the Theme and Plugin momentum that WordPress has. I am really just talking about a Software that is easy to install, runs on my hosted server and allows pushing of some Content. Is that asked too much? Sadly, yes. I don’t want to be too harsh, hence I will not name the tools I’ve tried (there were 4). I don’t want to blame developers who are really trying to do something for issues that lie within the framework. The ASP.net infrastructure has a lot of advantages over PHP, but as good as stuff like Web.config, Medium Trust and SQL Connection Strings is, it’s adding more complexity that developers seem to not try to take away from the end user.

I don’t know if this is the fault of the ASP.net Webforms model or if the .net OSS Community is smaller or whatever. I’ve now decided to tackle something that I have on my ToDo-List since writing that post in November 2007, I’ve decided to write my own blog software. I want to encounter the problems that the people who are creating it have, I want to run it in a production environment (Dogfooding, so to say). The recent release of ASP.net MVC was the final bit that removed all excuses for not doing it.

I will run into a lot of issues. I want to learn and use TDD, DI and ORM, and I have experience in none. I will do a lot of refactoring, and a lot of breaking changes and braindead mistakes. But I don’t want to be a complainer anymore when I have the opportunity to change it.

I don’t want to announce too much because it’s still in the early stages, but it will be open source (Ms-PL) and hosted on Codeplex.

So it will be SharePoint Server 2010…

Microsoft today announced the naming of the next SharePoint version, SharePoint “14” will officially be called Microsoft SharePoint Server 2010.

Looks like the more versions they make, the more stuff they drop out of the name. First it was “SharePoint Portal Server”, then “Office SharePoint Server”, and now just “SharePoint Server”. Makes sense to be fair, SharePoint is really a brand on it’s own, so why blur the lines too much. But the actual question will be: Is 2010 going to end this SPWeb.Dispose madness, that not only causes all sorts of weird issues, but is also inconsistent.

Really, SPWeb.Dispose is a big gun that is made for people to shoot themselves in the foot, and I’d love to see that improved more than anything else (Well, apart from CAML, that abomination of SQL).

The Filthy Pumpkin Show now got a Blog as well

Okay, I’ve just finished installing a Blog for FilthyPumpkin, available at http://blog.FilthyPumpkin.com. The purpose of this is to put in some teasers, articles and random stuff/scribbles online. We experiment a lot with stuff, but not everything gets made into a full project, hence the blog can serve as a place for this stuff. I will also use it for my Travel Diary and (if it happens) my GMT-1 Comic.

You can also follow FilthyPumpkin on Twitter. And because I forgot to link it before, here is Part 1 of Episode 1 of The Filthy Pumpkin Show:


The Filthy Pumpkin Show – Episode 1 Part 1 from Michael Stum on Vimeo.

I’m creating a Law…

Okay, I’ve seen LINQ to Active Directory. LINQ to iTunes (Well, sort of). LINQ to Google, LINQ to SharePoint, and now, there is even LINQ to Twitter.

Seeing all those LINQ Providers, I remembered Zawinski’s Law:

Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can

I would like to extend this law by creating a new Law:

Every technology will evolve to the point someone writes a LINQ Provier to it.