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

Announcing Meteor 1.2 – ES2015, Angular, React, and More

info.meteor.com

Post reply on HN
Print view View original

71–80 of 140 posts

Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More

#71

Post by mquandalle »

pinouchon wrote: post #66
akbar501 wrote: post #46

Earlier quoted context omitted.

Are you seeing 10 second rebuilds with incremental builds? Or is this 10 seconds for a complete rebuild?

With incremental builds. I have forked this project: https://github.com/wekan/wekan (~ medium size). On a 2014 macbook pro, reloading after a change in a template takes 10s. Not a dealbreaker, but this is frustrating. And this is with meteor 1.2. The slow build times may be due to the wierd frontend preprocessors (jade and stylus), but still.

Wekan author here. On my computer hot reload takes roughly 5s [Thinkpad T440s, ubuntu, 12go of RAM]. I'm not sure if the jade and stylus compilers add some time in the case I only modify JavaScript files, but anyway I plan to migrate these two package to support the new compiler API.

Still 5s is far from ideal considering the development experience with webpack and React hot loader.

Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More

#72

Post by hippich »

dustincoates wrote: post #38
hippich wrote: post #24

for people experienced with meteor - is there solid support for postgres backend? i really like it, but details on sql backends support is spotty

It's being worked on. There are some packages that provide postgres support ( https://atmospherejs.com/?q=postgres ) but not in core just yet.

wow... 5 different modules for postgres support. this will be hard to sell to sql folk just yet :)

Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More

#73

Post by daveroberts »

hn_user2 wrote: post #48
daveroberts wrote: post #30

Earlier quoted context omitted.

How often do you use npm packages which are not part of atmosphere? I remember this not working great. Have things changed?

Works great. Just isn't part of core. Meteor core is stubbornly trying to force use of atmosphere for everything. But everyine I know immediately installs https://github.com/meteorhacks/npm which allows for using regular npm packages. I think inevitably the meteor team will bring this into core, or something similar, and we will be able to have our mix of atmosphere and non libraries.

Thanks. Should any other packages be in core that are not?

Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More

#74

Post by gildas »

rofrol wrote: post #64
gildas wrote: post #27

Earlier quoted context omitted.

> isomorphic React apps render much quicker on first load source?

Maybe this? https://signalvnoise.com/posts/3112-how-basecamp-next-got-to...

Sorry if I sound pedantic but the major gain seems to be related to the use of a cache. It is never said that "React apps render much quicker on first load". Actually, the author almost admits that its application was taking 500ms to render a page on server-side.

Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More

#75

Post by ptttr »

There's one issue with Meteor that rarely gets mentioned. While you get hybrid mobile apps out of the box, you'll have hard time integrating native apps with Meteor backend. DDP clients are not official, and there's no minimongo on native clients so you lose critical part of Meteor's appeal. In the late game switching to native apps is more cumbersome compared to when you have a regular REST API backend. But still, Meteor is a amazing piece of technology and I'm happy to see this update.

Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More

#76

Post by debaserab2 »

emerongi wrote: post #3
arturadib wrote: post #2

I've been using Meteor for months. It's such a pleasure to work with. It's what Rails should've been if it was written today. They just keep on delivering on out-of-the-box functionality, compatibility with 3rd party libs, and more importantly - on a very solid architecture for real-time transport by guys who really know what they're doing. Kudos everyone.

Exact same experience. Development is easy and frustration-free. The team listens to the community AND delivers. The platform is not just for playing around anymore, it has matured really well. See the case studies[1] - I, for example, love Hansoft X[2]. I think I would feel frustrated to have to go back to any other framework. Meteor is what web-development should be like. I'm not sure if Meteor is going to be THE p…

Still waiting for the killer testimonial for meteor, until then I'd be too scared to try it with anything larger than a prototype or brochure site.

I don't want to be the first person attacking a completely new class of scaling problems using a proprietary tech stack that I may or may not have the ability to control.

Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More

#77

Post by coldtea »

diverightin63 wrote: post #68
coldtea wrote: post #55

Earlier quoted context omitted.

That's not data management. That's schema management (migration). And yes, you have to script a change to every document.

Right. And I see. Are these managed by something like migrations?

From my brief experience with Mongo no. But they are very easy to do in code.

Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More

#78

Post by mquandalle »

gmaster1440 wrote: post #62

One of the things still holding me back from using Meteor with React is the lack of support for a module loading system. It seems like if I want to define a component in a separate file, I'll have to assign it to a global variable if I'm going to compose it in another file.

Using global variables isn’t even the worst part. The big problem with this sharing model is that files are loaded in the alphabetical order, thus the only way to control that file a requires file b as a dependency is to give to b a file name that is before a in the alphabet (this is not true for Meteor packages where we can control the file order).

Thankfully MDG plan to address this issue soon.

Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More

#79

Post by gmaster1440 »

mquandalle wrote: post #78
gmaster1440 wrote: post #62

One of the things still holding me back from using Meteor with React is the lack of support for a module loading system. It seems like if I want to define a component in a separate file, I'll have to assign it to a global variable if I'm going to compose it in another file.

Using global variables isn’t even the worst part. The big problem with this sharing model is that files are loaded in the alphabetical order, thus the only way to control that file a requires file b as a dependency is to give to b a file name that is before a in the alphabet (this is not true for Meteor packages where we can control the file order). Thankfully MDG plan to address this issue soon.

Yeah, good to know.

Re: Announcing Meteor 1.2 – ES2015, Angular, React, and More

#80

Post by bvm »

gmaster1440 wrote: post #62

One of the things still holding me back from using Meteor with React is the lack of support for a module loading system. It seems like if I want to define a component in a separate file, I'll have to assign it to a global variable if I'm going to compose it in another file.

Tagging on to this, I assume we can't use all of ES2015 classes with react and meteor, as the mongo bit requires mixins.

Is there a fix in the works for this?

Post reply on HN