Comment by EGreg | Hacker News Reader

Comment by EGreg | Hacker News Reader

This all boils down to one key fact: Meteor is the only framework that controls the whole stack.

After all, the fact that no other company than MDG has even tried to make it happen should be proof enough that it’s not trivial.

I did it, over the last 4 years http://qbix.com/platform

Actually our platform aims to be an entire "Wordpress for social networks". We realized that identity, security, roles, permissions, consistency and realtime updates etc. are hard to get right and building a standardized platform will free up developers to focus on what their app does instead of reinventing the wheel, etc. Not only that, but it will allow interoperating and reusability of components across all the sites.

And yes, it does routing, pagination, components and more in a way that will give Angular and React a run for their money if you check it out.

Also it does a lot more: http://qbix.com/platform/features

PS: try loading all this on your smartphone!

This looks fantastic! Please could you write some words aimed at potential recruits to qbix? What to expect, what not to expect. I noticed, in scanning your site quickly (... I think all content should bear the 'scanning user' in mind, but that's another topic) that php is mentioned. What php knowledge is required? What JS knowledge is required? Make it easy for people (I mean really, visitors who are pre-tutorial) to decide if they have the wherewithal for it to be worth them making a modest commitment to take it for a test drive.

You can put together a site with hardly any PHP knowledge. Just place reusable componenets on pages, or widgets that connect to ready-made backends... but then you don't really need this framework.

But if you have some basic PHP knowledge, you'd create more pages, and perhaps some backend actions.

As far as the PHP and JS knowledge, see http://qbix.com/platform/guide

The more PHP and JS you know, the more you can do. Unlike React and Angular, though, everything is named in a super-straightforward way, like Q.page and Q.Tool and tool.children() etc. So you just go ahead and build your site and Qbix does a ton of things for you, like dynamically swapping out css/js as you navigate pages, takes care of history and routing, activates and removes tools and their associated events, lets you subscribe to exctly the events you need, and documents conventions you should use to play nice with everything else.

yours isn't a full stack reactive platform. great work though.

Reply on news.ycombinator.com