My thoughts on Umbraco after Codegarden 2012

Sunday, June 17, 2012 by David Conlisk

On Wednesday last, Niels stood up in front of 380 Umbraco developers and announced that v5 was being dropped. It was quite a bombshell. You can read more about the details elsewhere (read a good description of what's going on, watch the keynote, or read the comments on the original blog post for a flavour of people's varied reactions to the announcement), so I'm not going to into that here. I'm just trying to share my thoughts as a freelancer whose business is based on Umbraco.

Firstly, an alternative description of what is happening was suggested to me at Codegarden: versions 4 and 5 of Umbraco are going to be merged over the next number of months. Perhaps Umbraco HQ's aversion to "spin" meant a brutally honest approach, but maybe the reactions wouldn't have been so extreme if the decision had been presented in a slightly different light.

Umbraco is returning to its roots by returning to the community, which has been sidelined over the past while due to the development of Umbraco version 5. Developers who had been waiting for version 5 to mature before starting on their next package or idea can now focus on version 4 (myself included). And all of the pending work with version 4 which had been put aside because it was due to be dropped can now be picked back up. Everyone can focus on version 4 and take it forward.

For a lot of developers, myself included, Umbraco version 5 was to be the next step in our professional development. We were going to get to use the latest technologies like razor and (especially) MVC. The idea of a ground-up rewrite with a beautiful architecture was certainly a seductive one. But it was just too hard to use compared to version 4. (You can also read about some of the technical issues with the codebase).

Shannon has already demo-ed a working version of MVC with Umbraco version 4. This isn't in the core just yet, but I'm expecting to see it there very soon. Razor is already a part of version 4, thanks mostly to lots of hard work by Gareth Evans on the razor engine. The XML cache is not going away, so XSLT is still available for those who use it (again, myself included). This means that there is even more choice for developers when creating websites with Umbraco - use the tools that you and your team are most comfortable with. Personally, I plan on getting into razor over the next few months, but I'm not dropping XSLT - for me it's the perfect tool for translating XML into HTML.

So my conclusions?

While I feel bad for those who put a lot of work into Umbraco version 5 only to have the rug pulled from under them, I am mostly relieved. Having built hive providers for version 5 and built a basic site using it also, I know how complex it is. Version 4 is much easier to use and simpler to understand. It's a proven product, and one that is only going to improve. The team have learned a lot from their experiences with developing version 5 and this is not lost - it will eventually lead to improvements in version 4. The best bits from version 5 will all end up in version 4. And meanwhile I can get back to doing what I love to do - create great websites and web applications using Umbraco.

While this may not be a popular thing to say in the Umbraco community: this is business. I have built my business on Umbraco, and while I contribute to the community where I can, my continued use of Umbraco boils down to it being the best and most profitable way I know of building great websites.

Umbraco makes my day job fun, it makes me money, and it keeps my clients happy. While that's true I'll continue to support it and use it as best I can.

Related links

Never rewrite the code from scratch

the single most important quality of code is maintainability


If you found this article useful, please click the +1 button!


4 comment(s) for “My thoughts on Umbraco after Codegarden 2012”

  1. Gravatar of Damian

    Damian says:

    Hi David,

    Good read and that article you linked at the end about not rewriting code from scratch is a cracking article! Wonder if Niels has read that!?? How well does that describe what happened to umbraco v5 !

    At least all is not lost and it looks like v5 has turned into a research project (well the last 3 years anyway).

    How did cg12 turn out after having the schedule trashed right before the start?
  1. Gravatar of David Conlisk

    David Conlisk says:

    Hi Damian,

    Thanks for your comments.

    The atmosphere at CG12 was a bit deflated after the keynote but it had perked up by the end of the open sessions. A lot of people were surprised and hurt by the announcement, but there was also relief I think. By the end of the conference a lot of folk were regaining their enthusiasm for v4 and I think we'll see a lot of good stuff coming over the next few months.

    All is not lost, Umbraco is still the great product it always has been, so let's just get back to doing what we do best!
  1. Gravatar of Damian

    Damian says:

    Myself included! I thought it was a wind up as they had decided to call it something else like UmbracoMVC.

    Luckily I hadn't invested too much time and no client work on it or I would have been even more peeved.

    Read some shocking reports on the forums of people worried about their jobs been on the line after recommending 5 and putting weeks or months of effort in new sites with it.

    MVC was they key thing for me in 5 and also a more consistent API. Looking forward to seeing things get back on course now after so much limbo.
  1. Gravatar of John McHugh

    John McHugh says:

    Hi David, great articles and both very relevant,
    I was an early adopter of Ektron, circa 1999 and all their problems came at the point they went from C# to .NET boy did we loose endless amounts of time trying to get that to work properly!
    As for Umbraco, again we were early adopters , I think our first UMbraco web site was 2004, so it has been with great interest to watch all this unfold.
    I too absolutely love Umbraco and I think rolling all the good bits from the unreleased V5 into V4 is a far more viable proposition than going backwards in any shape or form.
    Regards, John

Please leave a comment: