Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The State of Meteor Part 2: What Happens Next

discovermeteor.com

Post reply on HN
Print view View original

11–20 of 153 posts

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

#11

Post by apalmer »

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…

No,

Or to rephrase, No React has not won the frontend war in the way and scale that jQuery won the front end war. At one point something like over 50% of all new (at the time of its peak) web applications big and small included it? No. I mean jQuery actually really lost its stranglehold primarily because the browsers actually started incorporating most of its core ideas into themselves to a point where it wasn't 'necessary' anymore.

However as far as alpha geek mindshare, react has definitely overtaken everything else in the frontend world. At least from what I can tell.

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

#13

Post by forax »

stevebmark wrote: post #3

I 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…

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 to grow their userbase. For example, not having to spend developer resources on Blaze might enable them to get SQL support out the door sooner. I'm cautiously optimistic for them but wouldn't be too surprised either if they were still struggling next year.

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

#15

Post by joshowens »

stevebmark wrote: post #3

I 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.

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

#16

Post by apalmer »

I am amazed by how the article attempts to look forward to what the future will hold with JavaScript frameworks... and yet seems to be completely both dismiss or misunderstand (perhaps willfully) why previous frameworks have succeeded.

jQuery did not succeed because it was a 'good enough' competitor to dojo or prototype or mootools or extjs... it succeeded because it went completely the opposite direction. it did not attempt to be a fundamental ui framework like those guys, it didn't try to be full featured, it didn't try to change javascript to look like another language and didn't try to shift the paradigm of the front end development world.

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

#17

Post by joshowens »

forax wrote: post #13
stevebmark wrote: post #3

I 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…

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.

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

#18

Post by epmatsw »

joeblau wrote: post #14

> 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?

Probably just means that Angular (at least seems to be) losing momentum and marketshare to React. It's hard to go a day without seeing something cool or exciting about React on the front page here, but all you see about Angular is either nothing or articles about the upcoming(?) transition to 2.0.

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

#19

Post by yazaddaruvala »

d0m wrote: post #10
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…

One interesting thing about React is how some big names (Amazon, Apple, Netflix, Yahoo) rallied to React instead of creating their own libraries, whereas they all had their own-cooked libraries before. Also, which is more of a personal opinion, but I've tried a lot of frameworks/libraries and React is the first one that really "clicked" with the way I work and design. I don't think it will "replace jQuery", but for m…

I have read blog posts by Yahoo and Netflix.

While I believe you, I'm just curious how they are being used by Amazon or Apple. Do you have references about this?

Post reply on HN