Can you run Node packages on Meteor yet?
The decision to be incompatible with the vast number of Node/npm modules is what originally turned me off from Meteor, and I hope it's resolved.
Announcing Meteor 1.2 – ES2015, Angular, React, and More
51–60 of 140 posts
Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More
#52So, one thing holding me back from using MongoDB (and thus Meteor) is a lack of understanding how schema can be managed.
Say in MongoDB you are storing documents in a collection such as { property: "" }, and decide you want to change that to { property2: "" }. Does that mean you have to script a change to every document to convert these objects?
Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More
#53I'm blown away by Meteor. Using Meteor and React is just buttery smooth. More and more companies are using React now in the startup space, and it's one of the most popular services on StackShare: http://stackshare.io/meteor React integration is a first-class citizen: http://sergiotapia.me/2015/09/18/react-and-meteor-match-made... No weird hacks, lib includes and other nonsense you shouldn't really care about. And you…
I'll jump on when they have first-class support for a DB that isn't Mongo.
Give me postgres support and I'll definitely consider switching what I have in the short term.
I'm happy to wait until then!
Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More
#54I'm blown away by Meteor. Using Meteor and React is just buttery smooth. More and more companies are using React now in the startup space, and it's one of the most popular services on StackShare: http://stackshare.io/meteor React integration is a first-class citizen: http://sergiotapia.me/2015/09/18/react-and-meteor-match-made... No weird hacks, lib includes and other nonsense you shouldn't really care about. And you…
I'll jump on when they have first-class support for a DB that isn't Mongo.
Microservices to the rescue?
Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More
#55So, one thing holding me back from using MongoDB (and thus Meteor) is a lack of understanding how schema can be managed. Say in MongoDB you are storing documents in a collection such as { property: "" }, and decide you want to change that to { property2: "" }. Does that mean you have to script a change to every document to convert these objects?
That's not data management. That's schema management (migration).
And yes, you have to script a change to every document.
Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More
#56My go to stack for personal projects is React Node Postgres, while Meteor looks great I just can't live without the sweet built in postgres features like trigger functions. I'm on the lookout for a rails like framework because right now I tend to code everything by hand. Will give it an honest try once they support MySQL or pgSQL.
Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More
#57Earlier quoted context omitted.
I'm curious - do you think there is room for someone to come along with the right combination of stuff to become the "de facto platform for all web development"? It's interesting also that people always talk about Rails but don't mention JSP and .NET, which I think are actually a lot more popular last time I looked around. I guess it depends on who you ask. I feel like JavaScript is in a sweet spot right now because…
Good question. I think Meteor is certainly the closest of such platform at the moment, but you don't have to go far to find a developer who really hates JavaScript and will never switch over. Such hate may or may not be justified, but you won't easily change their minds. At the same time, there are people - including me - who only develop with JS with no real need to switch over to something else. I wish I had a more…
Has anyone built an Ecommerce platform in Meteor? Meteor is just this months hotness for building a specific type of web product, namely web apps. It's not going to become the defacto standard of anything else.
Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More
#58So, one thing holding me back from using MongoDB (and thus Meteor) is a lack of understanding how schema can be managed. Say in MongoDB you are storing documents in a collection such as { property: "" }, and decide you want to change that to { property2: "" }. Does that mean you have to script a change to every document to convert these objects?
As far as I know, this is an issue for every database, no? What are you currently using?
Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More
#59Earlier quoted context omitted.
> isomorphic React apps render much quicker on first load source?
Evaluate + Layout + Render is not likely to be faster than Layout + Render for equivalent content.
More apt would be Fetch body + Fetch content + Evaluate + Layout + Render vs. Fetch body + Layout + Render
Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More
#60Can't wait to start learning this language. Are there any great resources like how the Laravel community has Laracasts, but for Meteor?