Shock Horror Umbraco 5 Sinks
What a way to start your Thursday: a blog post circling the office proclaiming the keepers of the holy grail have decided the grail is, in actual fact, too heavy to lug about, and is better off left at the bus stop.
At least that’s how I glorified Umbraco 5. A CMS which elegantly decouples itself from its data source with incredible flexibility. It makes use of all the latest and greatest tools – MVC3 for ASP.NET 4, comprehensive unit testing, dependency injection (IoC), a uniform Javascript API and structure (wow!) making use of KnockoutJS, Razor with dynamics (the easiest Umbraco templating you ever saw) and a completely plugin based architecture where even the core trees are plugins.
And Umbraco 5 is nice. Take a tour in the Visual Studio debugger from an ajax request down to a database call and everything is as it should be, in its right place – there is nothing weird, shonky or unexplainable like what you might find in the Umbraco 4 codebase.
So if you were like me, you spent your Thursday asking yourself “how…what?...why!…because it’s slow!??” And that is the crux of it – as of 5.2 beta, Umbraco 5 has been decreed by Umbraco HQ as architecturally slow. Which means throwing clever brains against it will not make it fast. And hence it was canned.
Wiliam make fast websites. As such, our plans to adopt Umbraco 5 have taken a bit of a blow. We’re now on the lookout for the best ASP.NET MVC based CMS we can find. And if that means bending Umbraco 4 to our will, then that is what we’ll do.