DamienG

Moving home

I have been planning on moving my blog off my little Windows Shuttle PC at home onto a hosted service for some time and the latest flurry of activity followed by DSL line meltdown was enough to give me the nudge I needed to get the job done.

Rob Conery provided a useful .NET/Subsonic app to make the transition from Subtext about as painless as possible bar the obvious one of going with a PHP based solution when I know .NET is a better technology.

I simply felt the .NET blogging engines didn’t give me what I want right now and yes, I know I should be contributing to them to get them where I want them but I’m just so busy on various projects that if I was coding a blog in the evenings I wouldn’t be writing on it. Hopefully the great, and no doubt equally busy, guys behind those engines will forgive my little foray into WordPress for a while.

The non-blog parts of the web site (yes, there are some, with downloads, fonts, cursors, little tools and a mini-biography) will be integrated with the site shortly and the theme will probably gradually change to something more me. I also want to add a few extra things, the tag cloud and identicons for a start.

The title of this post also has a second meaning… yes, I’ve put an offer in on a house and will hopefully be taking possession in around 6 weeks providing nothing goes wrong.

Your invite to the house warming party will be in the post…

[)amien

1 response to Moving home

  1. Avatar for

    Information is only used to show your comment. See my Privacy Policy.

  2. Avatar for steve
    steve

    One thing I’ve learned during my time in IT is that the best technology is not the most important thing, the number of people using it in a given context can make a huge difference. Betamax anyone?

    I guess with .Net whilst there are a lot of people using it, the culture is such that there are less people releasing stuff openly than in environments that are themselves open and thus it’s an established part of the culture. Microsoft never really promotes an ‘openness’ and seems happy to alter the API / patterns however they like, whenever they like, whatever helps drive their own products. I think this sets a tone that ripples around the community.

    Java is a funny one — whilst it was proprietary tech it still had an ‘open’ culture because of the vendor independence and the long-running Java Community Process (JCP) that let experienced people influence the API direction. I think that led directly or indirectly to a large number of quality open source projects, like Hibernate, Struts, Spring, Eclipse. I think this shows that even your tech doesn’t need to be open so long as your process and attitude is (of course, Java is open too now), to promote the same thing out in the community.