The State of Meteor Part 2: What Happens Next • Hacker News Board

Re: The State of Meteor Part 2: What Happens Next

#151

Post by d357r0y3r » Fri, Jan 22, 2016, 5:36 PM UTC

silviogutierrez wrote: post #23

NhanH wrote: post #5

Can someone chime in as to whether React won the frontend war? As in the super majority of new project will be developed in React. I'm not that well-versed in the Node ecosystem (I got my news from ... HN). But from little I've seen, I found it hard to believe that React would be able to react the place where jQuery was (is?). Heck, we even have a post staying on the front page today lamenting the inferiority of Reac…

I was about to abandon Angular 1 for future projects and go all in on React. And it looked fairly promising, except everything is its own little module. Good for UNIX, but not so good for modules that change so often. Then I started catching up on Angular 2 and TypeScript. It looks like the right mix between new and opinionated. I just don't have time to research a module for data, one for building, one for testing,…

Try Aurelia + TypeScript. I've used Angular 1, Angular 2, and Aurelia, and I think Aurelia is the best choice between those right now.

React is fundamentally different, but Aurelia (and its predecessor, Durandal) were always about making component-oriented apps.

Re: The State of Meteor Part 2: What Happens Next

#152

Post by justaaron » Sat, Jan 23, 2016, 3:54 PM UTC

kainolophobia wrote: post #146

faceyspacey wrote: post #38

Earlier quoted context omitted.

Meteor has as a better chance than ever, ESPECIALLY if 90% of what you can do in Meteor you can do in "bare metal" NPM! Meteor doesn't have to provide that many "features" to win over the NPM crowd that it has struggled to acquire thus far. It's so damn complex to implement all this stuff that most developers need help doing it. Meteor's problem thus far has been it makes it easy but provides no way to "drop down" to…

"allow you to drop down to make lower level tweaks as you would on 'bare metal' NPM" Meteor is entirely open-source and I've had no trouble diving into the lower levels to accomplish what I need to accomplish. Everything is split into reasonable packages and is relatively easy to traverse. If anything, the Meteor team hasn't done a good enough job showing their true value (realtime via oplog->client updates, etc). Mo…

this. and like most trends, it's shortsighted (and based upon the whims of contemporary front-end web dev fashion and not the needs of the meteor eco-system)

Re: The State of Meteor Part 2: What Happens Next

#153

Post by EGreg » Sun, Jan 24, 2016, 9:14 AM UTC

strongai wrote: post #119

EGreg wrote: post #60

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, con…

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) t…

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.