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

51–60 of 153 posts

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

#51

Post by incepted »

apalmer wrote: post #16

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…

jQuery filled a need.

It's as simple as that.

Its success has nothing to do with looking in the other direction or not redefining Javascript: it solved a problem that a lot of Javascript developers were struggling with.

Now what's really fascinating to me now is that while one can safely say jQuery created a revolution in the Javascript world when it came out, it is today widely looked as a smell and avoided as much as possible in favor or frameworks that modify the model instead of the UI.

And this quick rise to success and fall to obscurity could very well happen to the successful frameworks we are currently using today (including React).

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

#52

Post by JDDunn9 »

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 think React won the HN front page, where anyone who criticizes it or promotes another technology gets down-voted. However outside this bubble, ReactJS has a very long way to go before adoption rates make it a contender for top library (http://trends.builtwith.com/javascript/javascript-library).

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

#53

Post by qaq »

faceyspacey wrote: post #38
joshowens wrote: post #15

Earlier quoted context omitted.

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…

Unless this comment is from SMM team at Meteor, WTF? What is NPM market :)? "Bare metal" npm? Name single sizable project that uses Meteor? You do realise that for 90% of enterprise projects it's a wrong tool. There is no usable universial/isomorphic option, you can't expose API for external consumption, if you have to consume services on the backend the only cool feature that Meteor has is gone. Not to mention long term risks of what will happen to the project when vc funding runs out.

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

#54

Post by faceyspacey »

incepted wrote: post #51
apalmer wrote: post #16

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…

jQuery filled a need. It's as simple as that. Its success has nothing to do with looking in the other direction or not redefining Javascript: it solved a problem that a lot of Javascript developers were struggling with. Now what's really fascinating to me now is that while one can safely say jQuery created a revolution in the Javascript world when it came out, it is today widely looked as a smell and avoided as much…

it wasn't "quick" though. React had a good run. One of the best "runs" you could hope for at the end of the day.

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

#55

Post by ef4 »

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…

> some big names (Amazon, Apple, Netflix, Yahoo) rallied to React

That's a bit of an overstatement. At least three of those four are also shipping major Ember apps and investing heavily in that ecosystem. (The only one I don't know for sure is Amazon.)

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

#56

Post by VeilEm »

JDDunn9 wrote: post #52
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 think React won the HN front page, where anyone who criticizes it or promotes another technology gets down-voted. However outside this bubble, ReactJS has a very long way to go before adoption rates make it a contender for top library ( http://trends.builtwith.com/javascript/javascript-library ).

React is probably too hard for casual scripters. I disagree with the OP's point about it being the new jQuery. It is however perfect for a solid engineering solution to building great web applications. It's for engineers who care about churning out a well tuned architecture and not for those who are just creating an CRUD app that just grows organically.

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

#57

Post by ZoF »

faceyspacey wrote: post #54
incepted wrote: post #51

Earlier quoted context omitted.

jQuery filled a need. It's as simple as that. Its success has nothing to do with looking in the other direction or not redefining Javascript: it solved a problem that a lot of Javascript developers were struggling with. Now what's really fascinating to me now is that while one can safely say jQuery created a revolution in the Javascript world when it came out, it is today widely looked as a smell and avoided as much…

it wasn't "quick" though. React had a good run. One of the best "runs" you could hope for at the end of the day.

You mean JQuery had a good run?

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

#58

Post by [deleted] »

faceyspacey wrote: post #54
incepted wrote: post #51

Earlier quoted context omitted.

jQuery filled a need. It's as simple as that. Its success has nothing to do with looking in the other direction or not redefining Javascript: it solved a problem that a lot of Javascript developers were struggling with. Now what's really fascinating to me now is that while one can safely say jQuery created a revolution in the Javascript world when it came out, it is today widely looked as a smell and avoided as much…

it wasn't "quick" though. React had a good run. One of the best "runs" you could hope for at the end of the day.

[deleted]

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

#59

Post by jorgecurio »

sergiotapia wrote: post #45

My thoughts: Meteor got popular enough that the Javascript loons started pecking at it and infesting it with the general lunacy that accompanies NPM and it's ecosystem. MDG adding easy React support was a definite win and I think using Meteor with React is -the- way to write Meteor apps. But they need to start ignoring the crazies out there and focus on their vision.

laravel is fine too

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

#60

Post by EGreg »

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!

Post reply on HN