Might have been different if they had chosen to embrace SQL, instead of just putting it on the roadmap and letting it rot.
I can't imagine how many enterprise sales they're losing because of lack of SQL support
The State of Meteor Part 2: What Happens Next
31–40 of 153 posts
Re: The State of Meteor Part 2: What Happens Next
#32Might have been different if they had chosen to embrace SQL, instead of just putting it on the roadmap and letting it rot.
This has been my feelings on meteor as well. It looked neat and I went through some of the tutorials and such, but really had no projects I could use it on. All my current projects interact with various sql database at some point. I realize that isn't as cool as all the nosql stuff, but I kept hoping they would get to it, and then kept getting disappointed.
It's a pretty narrow full stack to me if you don't have real support for sql databases. It's been sitting there for 3 years and has about the highest votes of all them. They had a post about experimental postgresql project in august(http://info.meteor.com/blog/an-early-look-at-sql-in-meteor), but it's mostly sat there with a few updates since then. It doesn't seem to be much of a priority.
Re: The State of Meteor Part 2: What Happens Next
#33> And Angular is… well, it’s not React. Can someone explain what this statement means in terms of the technical benefits of React over Angular?
I meant it's not so much about the technical merits of Angular and React, as just picking one (React) and sticking with it.
Re: The State of Meteor Part 2: What Happens Next
#34Earlier quoted context omitted.
Part of the reason this year has been a bit of a mess is because MDG has been focusing a lot of resources on the profit-generating component of their business: meteor hosting and support. They launched Galaxy (their hosting service) just a couple months ago so it's still too early to say how successful that will be, but it could easily be in their best interests to cannibalize some of their older features if it helps…
Not having to spend money on Blaze will make them more competitive as a hosting business. Frankly, when is the last time you saw a billion dollar unicorn hosting business? Or a hosting IPO? I doubt we will see SQL support. We will likely see something with GraphQL instead.
Digital Ocean is also getting there, started in 2011, currently valued at $683 million.
Re: The State of Meteor Part 2: What Happens Next
#35Can 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,…
I totally agree with you.
It took me lots of time just to figure out to write a 'PROPER' react application. There are too many modules to choose from for routing, data acess etc..
Then I tried with Angular 2, it look me less time to get up and running with forms, routing and everything...
Re: The State of Meteor Part 2: What Happens Next
#36Seeing the Discover Meteor and Kadira guys embrace React with Meteor is definitely making me want to dive back into the framework after being very hesitant over the past few months. It's great to see ~someone~ with a clear vision for the future.
Re: The State of Meteor Part 2: What Happens Next
#37what major production apps are build with Meteor? This might be the wrong place to ask but I figured it's worth a shot.
Re: The State of Meteor Part 2: What Happens Next
#38I predict that Meteor will won't go anywhere in 2016. I know this sounds negative so I'll try to explain. The surface area of Meteor is still too large. Keep in mind this is a venture backed company, people are getting big salaries to work on a framework. Look at what it's led to: in house tools like Blaze which even the creators are already tired of. At best Meteor will be 90% cannibalized and replaced with open sou…
Why would the post be business focused? The guy that wrote it doesn't run "Meteor the business", he just loves the framework itself. I am not even sure how a CMS got mentioned and compared here.
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 a lower level and configure things like you would on "bare metal" NPM!!!! Despite its easiness, this has scared away many developers from Meteor--especially the expert developers who would otherwise evangelize once they joined Meteor.
Therefore, Meteor just needs to provide a way to BOTH do things with sufficiently less boilerplate (like it's always done well), but also allow you to drop down to make lower level tweaks as you would on "bare metal" NPM. And perhaps even an intermediate tier in between for some features.
For example, Relay + GraphQL is great but there should be the "beginner's way to Relay."
So the killer feature in fact isn't a "feature" in the traditional sense, but rather a mechanism that only a full stack framework could provide. Being the only full stack framework that matters (and the only "reactive full stack framework" in existence), Meteor is well positioned to scoop up the entire NPM market if it plays its cards right!
Re: The State of Meteor Part 2: What Happens Next
#39Can 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…
Take a look at the trend line and React still has a long ways to go to catch Angular:
https://www.google.com/trends/explore#q=reactjs%2C%20angular...
Having stated that I am trying to get up to speed on React in order to make a knowledgeable comparison to Angular 2. I've got friends who are way better JavaScript programmers than I am, ones with VC backed startups built with Angular 1, who are really struggling to learn Angular 2.
Re: The State of Meteor Part 2: What Happens Next
#40Can 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,…
We've been using Angular on one project and for a new application we were considering using just React with Node or maybe those two with Angular 1 or 2 also. However, after getting started with Aurelia we may stick with it and never consider Angular again!