Sorry, I keyed off of the words “web framework” and made assumptions.
I agree, I’d very much like to see a quality Meteor-based blog…
Actually, maybe I don’t precisely agree. WordPress has grown far beyond a blog. Most sites written with it are not blogs.
I prototyped an app in WordPress that had blogging, event scheduling, albums, forums, and a few other niceties in about 3 days. I then realized that I would never be able to get that to work in a polished, cohesive way - largely because the components were all flaky in some fashion. I looked into the causes and decided that the platform has just gone through too much evolution without revolution. Also, the components weren’t very exciting, the client loads were always north of a megabyte, and I couldn’t find a way to twist their multisite mode to support my site’s requirements to have a single site with groups that each have their own page with the above features and have relationships to other groups.
So, I would very much like to see WordPress’s replacement implemented on Meteor. I see this as being in reach with Meteor 1.5 + Apollo. I think Meteor is going to start stabilizing after that point and a framework trying to garner a community of theme/plugin developers needs some stability.
Hopefully, it will be possible at that point to develop an application framework that
- allows theme and plugin developers to choose the view layer of their preference, be it React, Blaze, or whatever,
- cleanly mix their products with other plugins using other preferences,
- choose the degree of reactivity that their components need independently of each other,
- meet their database needs with SQL, NoSQL or any mix the problem being solved requires,
- allows for core components such as accounts management and permissions management to be plugins instead of hard-wired into the framework to create better competition and ease growth there,
- never thinks of itself as just a blog tool but instead a site building tool that anyone can use to build and deploy an exciting site with state-of-the-art components whether they be blogs, chat rooms, messaging centers, forums, store fronts, business fronts, event managers, or whatever else you can think of in hours,
- provides a tool for novice users to pick themes and plugins, lay them out, and configure them,
- provides a portal for those to be picked from (npm could perhaps store them but they’d need to be findable in a system that lets you see what they look like, has novices in mind, and supports both free and paid components),
- builds all of that using automatic code splitting to keep sizes down,
- and builds and deploys apps with all of that for the phone, the web, or the PC that simply work without being debugged by someone knowledgeable of JS.
I think all of that and more is possible on top of Meteor. It just needs clear and hard standards for the interfaces that the different component types are written too and a framework (as thin as possible) that glues components written to those standards together with a few tools. The basic pieces are probably already out there but need to be pulled together and made uniform.
So, my answer to the article’s question is that I believe that Meteor is now a good option for building a blogging platform for 2017 and beyond and that that platform, if done right, could become a great option for building lots of sites, not just blogs. But, Meteor itself is not a good option for the typical blog builder (my mother who is an ex-English teacher blogging in retirement) or or an efficient option for experienced developers to build a blog nor do I believe it ever will be or was ever intended to be.