1. AJ

    See what crazy licensing does!

    Anyone remembers Movable Type from SixApart? I started using that back when WordPress was new and WP did the smart thing while Movable Type was charging insane prices for their licensing and had so many restrictions.

    Look where Movable Type is now. It’s a shame because I found MT was actually better than WordPress. But, look what happened to them in the end.

    As for ExpressionEngine, will have to see if this move gives potential.


  2. Scott

    Hi Sarah, interesting info. However, EllisLab founder Rick Ellis is quoted as saying that “over 90% of the CMS market is open source.” And according to w3techs, WordPress has a CMS market share of 59.5%. So how much of the CMS market would be open source w/o WordPress?

    The somewhat successful Concrete5 has been open source since 2008 but its CMS market share is still a paltry 0.2% according to w3techs – even worse than ExpressionEngine’s 0.3% market share.

    Plus several non open source CMS options have much higher market share than open source Concrete5 (Squarespace, Weebly, Wix, etc).

    So being open source is only one of several factors to consider. For example, according to techspot.com, open source Android has 61% of the US smartphone market, and iOS has 38.7%. But I doubt many people believe iOS is a failure and Apple should make iOS open source (plus most people seem to agree that iOS provides a better and safer user experience).

    In other words, ExpressionEngine apparently failed at competing with non open source CMS competitors. So now it’s so desperate it’s going open source thinking it can take on the biggest CMS in the world? Do they know something others such as Joomla, Drupal and Concrete5 don’t know? I wish ExpressionEngine great success, but they’re definitely facing long odds.


    • Marko

      “over 90% of the CMS market is open source.”

      Maybe it was meant that 90% of CMS systems that are out there are open source, not evaluating their market share? Just that 90% of CMS systems that exist are open source. Maybe I misunderstood that.


  3. David Jung

    There is a lot you can do with EE that you can’t with WP. It’s a great tool for a mid range custom site. I hope this is a successful move for them.


    • Konstantin Dankov

      Can I request an example or two of things you can’t do with WP and can with EE. Seriously, asking for information, not to be annoying.


      • Cade Halada

        It’s been years since I used EE but I remember it being a lot more versatile for creating any content you wanted. WP started as a blogging platform which became a CMS through Advanced Custom Fields. EE was a CMS that you could use to make a blogging site or any other type of content site. The biggest difference now will be in the database where EE is going to make tables for content types and WP is going to save everything as a post type. EE will probably be more efficient on the backend. For 99% of sites, it doesn’t matter.

        EE lost out because they started charging too much and WP became more attractive with the giant community of plugins. EE had a free version and they took it away over time and became more restrictive. They pushed the small time web people to leave. The plugins for it became expensive and they still are even if they are going to open source the main software. All the plugin developers wanted a piece of the pie. They have made their model so inclusive that Craft is now overtaking them by basicly being the cheaper version of EE.


  4. Daniel James

    It’s funny how a software that most have never heard of wants more market share and only now in 2018 has decided to go open source. This doesn’t seem like it was ever deemed ‘the right thing to do‘, more of a move to grab more money wherever possible.

    It’s great another CMS has chosen to go open source, but I’m struggling to see how they’ve only just realised open source is a big player in the open web. It’s been this way for nearly a decade, arguably more than that in fact.

    I think it’s probably still a little too late though, albeit better than nothing. Those licencing terms are pretty passive aggressive, no wonder they decided to remove them.


  5. Her

    WP still my overall best CMS. Also the community behind is way greater than all the plugin makers for prestashop and drupal.


  6. Ankara Web Tasarım

    It’s great another CMS has chosen to go open source, but I’m struggling to see how they’ve only just realised open source is a big player in the open web. It’s been this way for nearly a decade, arguably more than that in fact.


  7. Nicholas

    Too little, too late.


  8. Bryan Chalker

    I was a dev/designer with EE years ago (before I ever did a WP site). The community was small then. This is a too-little-too-late scenario, and I feel for those out there who wanted it well before now. It turned me to WordPress.


  9. Brent R Toderash

    “Although open source was a viable licensing model when we launched our first CMS back in 2002, it was not apparent then just how dominant open source would become on the web,” Ellis said. “It wasn’t until Eric Raymond wrote The Cathedral & The Bazaar that open source would even begin to enter the general public’s consciousness. Since then we’ve watched the open source market grow rapidly and continuously.

    ESR wrote CatB and published it online in 1997. The book was published in 1999. Have to call BS on the above quote. If they knew it was a viable model in 2002, they HAD to know about CatB before rejecting a FOSS model. If they didn’t, they were grossly uninformed about the FOSS community that was already very significant at the time.


Comments are closed.

%d bloggers like this: