The State of Meteor Part 2: What Happens Next
discovermeteor.com
The State of Meteor Part 2: What Happens Next
1–10 of 153 posts
Re: The State of Meteor Part 2: What Happens Next
#2It is kind of sad that this wonderful framework, from total awesomeness, came to this situation where I am not sure what will future bring and should I make my projects in Meteor.
Meteor started with huge advantage, it is auto reloading, it has data layer that is very simple to use, it syncs across clients. On top of that, you can package mobile apps with it.
One thing I really loved is Velocity, testing runner that would display a dot in the corner of the screen, it would run a testsuite, and if it turns red, you can click and learn what test failed.
I was hoping it will be more awesomeness, instead, they eliminated Velocity, testing is not clear cut, db layer that needed most attention is not getting enough, whole focus is on frontend.
React is awesome and adding it, it really brings a lot to Meteor, but I think Blaze was good enough.
Anyhow, now I am Elixir/Phoenix dev, don't feel the same pain I did before, but any positive news from Meteor would be very much welcome.
Re: The State of Meteor Part 2: What Happens Next
#3I 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 source tools (as this blog post is implying), and sit properly in the same place as other CMSes, which inherently don't get that popular. What's worrying about this post in particular is it's not business focused, and the only long term company goal mentioned is "meteor will be a back end solution that makes sense." To what end? Why wouldn't you do that in a non-profit or pure open source model?
Re: The State of Meteor Part 2: What Happens Next
#4It is kind of sad that this wonderful framework, from total awesomeness, came to this situation where I am not sure what will future bring and should I make my projects in Meteor. Meteor started with huge advantage, it is auto reloading, it has data layer that is very simple to use, it syncs across clients. On top of that, you can package mobile apps with it. One thing I really loved is Velocity, testing runner that…
Phoenix is the only other thing that really appeals to me as something I want to try that is fun. That was the great thing about Meteor, it got a lot of shit done, and it was fun. That's important.
What do you do to hook into Elixir? What's your tech-stack for the other side of the back-end?
I was looking into phoenix/elxir generating GraphQL but that seems pretty immature and at least a year out to be comparable with Minimongo/ddp.
Re: The State of Meteor Part 2: What Happens Next
#5Can 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 React.
Re: The State of Meteor Part 2: What Happens Next
#6I completely agree and I'm excited about this vision for Meteor. The dream would be to have a go-to choice with formidable standards that Just Works.
Personally, what I wish existed was a full-stack framework AND dev ops built with the "best" open source libraries. I'm fine with not having my favorite X if it means having a set of well supported, highly performant with lots of documentation and training materials services that work perfectly together.
Starting a new project the "right way" is a pain right now. Again, I would gladly trade my favorite libraries/tools for a great full-stack solution (including dev ops, continuous integration, roll-back deployment, scalable servers, etc etc.)
Software engineering is still a new field and it's hard to establish "best ways of doing things", but I'm wondering if it'll start converging to "The Proper Way". Similar to how building houses is pretty straightforward. Of course, part of the reason that it's hard to do in software engineering is because technology keep changing so fast.. I.e. Tools from a few years ago will most likely not play well with VR stuff.
Re: The State of Meteor Part 2: What Happens Next
#7It is kind of sad that this wonderful framework, from total awesomeness, came to this situation where I am not sure what will future bring and should I make my projects in Meteor. Meteor started with huge advantage, it is auto reloading, it has data layer that is very simple to use, it syncs across clients. On top of that, you can package mobile apps with it. One thing I really loved is Velocity, testing runner that…
Phoenix is the only other thing that really appeals to me as something I want to try that is fun. That was the great thing about Meteor, it got a lot of shit done, and it was fun. That's important. What do you do to hook into Elixir? What's your tech-stack for the other side of the back-end? I was looking into phoenix/elxir generating GraphQL but that seems pretty immature and at least a year out to be comparable wit…
I just use Phoenix/Elixir. I can wire it with React, but honestly I am starting to question this. Only if I really need React, I will actually use it.
So far I work on simpler stuff, api's and smaller apps.
Re: The State of Meteor Part 2: What Happens Next
#8[deleted]
Re: The State of Meteor Part 2: What Happens Next
#9Can 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 it did, but this is JS we are talking about and tide will turn quickly.
Re: The State of Meteor Part 2: What Happens Next
#10Can 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 modern single web application, I think React is the way to go. Or said differently, "Nobody will get fired for choosing React" ;)