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

What's coming in Meteor 1.2, and beyond

info.meteor.com

Post reply on HN
Print view View original

61–70 of 98 posts

Re: What's coming in Meteor 1.2, and beyond

#61

Post by kidsil »

Rezo wrote: post #47

It is highly encouraging to me that Meteor is acknowledging the larger trends in the Javascript ecosystem and promoting React to an officical frontend layer instead of doubling down on their homegrown solution. Likewise for seamless Babel integration and planning the move to official ES6 modules. Buying into a full-stack solution like Meteor is a scary proposition; you're giving up a large amount of control for a pro…

Honestly I'm very likely to stick with Blaze for the time being, as I've found it easier to follow & understand than Angular (haven't tried React yet).

I just like the sticking with general modularity approach (that really reminds me of Ruby).

I don't think the Meteor proposition is any scarier than getting into Rails, Django, or even Laravel. You're basically trusting a growing ecosystem that will prevent you from re-inventing the wheel.

Re: What's coming in Meteor 1.2, and beyond

#62

Post by jkarneges »

kidsil wrote: post #61
Rezo wrote: post #47

It is highly encouraging to me that Meteor is acknowledging the larger trends in the Javascript ecosystem and promoting React to an officical frontend layer instead of doubling down on their homegrown solution. Likewise for seamless Babel integration and planning the move to official ES6 modules. Buying into a full-stack solution like Meteor is a scary proposition; you're giving up a large amount of control for a pro…

Honestly I'm very likely to stick with Blaze for the time being, as I've found it easier to follow & understand than Angular (haven't tried React yet). I just like the sticking with general modularity approach (that really reminds me of Ruby). I don't think the Meteor proposition is any scarier than getting into Rails, Django, or even Laravel. You're basically trusting a growing ecosystem that will prevent you from r…

Rails, Django, and Laravel are all server-side frameworks. You could replace one with another, without having to rewrite any client code.

Meteor is all-encompassing, covering both the client and server. That means you have much less agility in terms of swapping out components, but of course its convenience is unparalleled.

Actually this has me wondering, is there anything else out there like Meteor that covers both client and server development at the same time? Maybe GWT?

Re: What's coming in Meteor 1.2, and beyond

#63

Post by pmontra »

jkarneges wrote: post #62
kidsil wrote: post #61

Earlier quoted context omitted.

Honestly I'm very likely to stick with Blaze for the time being, as I've found it easier to follow & understand than Angular (haven't tried React yet). I just like the sticking with general modularity approach (that really reminds me of Ruby). I don't think the Meteor proposition is any scarier than getting into Rails, Django, or even Laravel. You're basically trusting a growing ecosystem that will prevent you from r…

Rails, Django, and Laravel are all server-side frameworks. You could replace one with another, without having to rewrite any client code. Meteor is all-encompassing, covering both the client and server. That means you have much less agility in terms of swapping out components, but of course its convenience is unparalleled. Actually this has me wondering, is there anything else out there like Meteor that covers both c…

Maybe Volt http://voltframework.com/ but I didn't use it and it's hardly mainstream.

Re: What's coming in Meteor 1.2, and beyond

#64

Post by sanderjd »

davnicwil wrote: post #53
sanderjd wrote: post #46

Earlier quoted context omitted.

You ask a really good question. With all the myriad javascript libraries coming out weekly, you'd think we would all know of four different optimistic synch libraries off the tops of our heads, but I don't think I've seen any. Perhaps that's because in order to get it to work, Meteor has a bunch of code that (I think) watches Mongo's write-ahead-log, so you can't just make a front-end library for it. I think this is…

I had a good look for a library that does this for the app I'm currently working on, before giving up and creating a custom solution myself. My implementation is very much custom-fitted to my particular backend api and the way I'm rendering the view layer with React. I think a large part of the reason such standalone libraries might not exist yet, is that it's really difficult to make a general, flexible, tech agnost…

That's basically my take on it, and we also have a bunch of custom code to do similar things piecemeal, but it doesn't work very well and I envy Meteor's solution, while remaining unprepared to jump onto the framework in its entirety. But lots of "really difficult" things have been accomplished in the past, so I'm still hoping to come across a "general, flexible, tech agnostic solution to this problem" at some point!

Re: What's coming in Meteor 1.2, and beyond

#65

Post by pmontra »

leeleelee wrote: post #57

Anyone out there using Angular and Firebase? That's been my go-to "stack" for achieving 3-way binding of the UI, javascript model, and remote database. The only downside is that you're locked into using firebase as a service, can't host it locally, and you're limited to what their API supports. It's amazingly fast in terms of ability to churn out features. Meteor seems to be the only thing that comes close to giving…

I did the design of a project that used Angular inside Ionic with Firebase as backend. They integrated well, no particular problem. Just be careful not to keep websockets open unless those you really need. Close the others. They'll keep the CPU busy and bleed the battery.

The only major problem was with Firebase itself, when we had to start duplicating data because it's a tree and it doesn't have joins. But it would be unfair to complain because it's like that by design and we knew what was expecting us. Is there any service like Firebase but with joins?

Re: What's coming in Meteor 1.2, and beyond

#66

Post by pdkl95 »

So when is Meteor going to start sending actual web pages? I ask here, because seeing a blank page that consists of
Isn't very useful. ES6 is nice... when javascript is available. I know it's current popular to pretend that progressive enhancement is too much work, but that doesn't change the fact that your site doesn't even have an error mesaage when javascript is filtered at the firewall.

Re: What's coming in Meteor 1.2, and beyond

#67

Post by honest_joe »

Siyfion wrote: post #33
honest_joe wrote: post #11

Earlier quoted context omitted.

How is the performance ? For me something like Atom feels very sloppy compared to Textmate / Sublime

Have you tried Atom since they shipped version 1.0? It's been sped up a LOT. However, I don't really think that this topic has much to do with React / Meteor, as Meteor is a full-stack web-solution, Atom is a desktop text-editor built with web technologies (and specifically React)... It's like saying my Ferrari goes faster than your boat, yup, on land.

I know but i have commented on a guy's post talking about building desktop web apps.

Also yes i have tried the latest Atom's version. I am not bashing it's just that i feel that the performance is still worse than the native solution (obviously).

Re: What's coming in Meteor 1.2, and beyond

#68

Post by liadmat »

Really glad to see React Native mentioned here, albeit briefly. Hybrid mobile apps like the ones currently supported by Meteor always feel kind of clunky, and the 3rd party implementations of DDP for iOS/Android feel like a workaround and not the Meteor-way of doing things. Would be interesting to see how React Native is integrated into Meteor. Though what I really want to see is Blaze Native.

Re: What's coming in Meteor 1.2, and beyond

#70

Post by jxm262 »

Awesome!! never saw this link they've mentioned - http://react-in-meteor.readthedocs.org/en/latest/

I've been playing with meteor just recently and am totally loving it. I really like Blaze, but love React's component system, so not really sure which way I want to turn now... I'm almost thinking of just implementing a React-like dictionary in Blaze to keep it more 'component' like , because I really dislike the jsx transpiling.

Anyway these announcements are definitely making me more convinced that I should try Meteor in a production app. I see many good things coming for this project.

Post reply on HN