21–30 of 42 posts
I would like to see this with es6 components
Earlier quoted context omitted.
Meteor's story for backend rendering is the spiderable package, which works as follows: "When a spider requests an HTML snapshot of a page the Meteor server runs the client half of the application inside phantomjs, a headless browser, and returns the full HTML generated by the client code." That's not really a good solution for all the obvious reasons. (Speed, resource usage, dependencies.) Plus, by that logic every…
React integration should make implementing good server-side rendering much easier. There is already a discussion and community project around this: https://github.com/meteor/react-packages/issues/15
Earlier quoted context omitted.
Hi, I wrote this blog post. We were trying to keep our API surface area small with one way to load data into components, but you're right -- we should probably /also/ add a ES6 base class as a second option, and let the people choose which they prefer. A lot of React developers still prefer mixins -- react-router recently switched from mixins to ES6 classes and then changed their mind "until ES6 classes have better a…
That is very disappointing. Decorators already exist in Babel and they work perfectly. I don't know what they're waiting for
Interesting to see this implemented as a mixin when they just announced yesterday they are fully supporting es6. Looking forward to building some side projects with this and seeing how it compares to using react + flux.
The community is pretty divided and es6 classes are fairly controversial. Don't be too surprised to see a lot of people avoid them. On purpose. And it's not because they aren't familiar with OOP.
Extremely bold words as usual. I don't think I've ever seen any JS technology that manufactures as much hype as Meteor. Every single article from Meteor makes it sound like the best thing since sliced Jesus.
Are there any reliable numbers on Meteor adoption (and retention)? If you listen to people using Meteor it's already more popular than jQuery but everybody else seems apathetic at best. If you go by Stackoverflow numbers (which Meteor shows off on its homepage), it's merely 1/10th as popular as AngularJS (and roughly as popular as express, which never even came close in terms of hype).
Earlier quoted context omitted.
That may be the case with the node community, however AFAICT the React community seems much more open to fully utilizing ES6
Its the javascript community as a whole that is divided, generally between imperative/OOP and functional devs. Has nothing to do with Node or otherwise. Even if you like classical inheritance, the Class keyword is poorly implemented for it, from both a normal OOP language's point of view OR from a prototypal inheritance point of view. It's bad at both.
The primary reason a significant part of the community hates the ES6 classes is that the class keyword is misleading for people who don't understand prototypal inheritance.
The OOP vs FP divide is orthogonal to that as the FP devs in question generally disagree with the constructor+prototype pattern to begin with (and often shun prototypal inheritance entirely).
There's also the people who want JS to be more like Haskell/Lisp, but they've mostly moved to LiveScript and ClojureScript and only occasionally complain from the sidelines.
I would like to see this with es6 components
You mean web components? I'm not sure it's possible to pass in anything other then strings as values via their attribute changed callback. They simply aren't as well designed and powerful as React components.
Earlier quoted context omitted.
Hi, I wrote this blog post. We were trying to keep our API surface area small with one way to load data into components, but you're right -- we should probably /also/ add a ES6 base class as a second option, and let the people choose which they prefer. A lot of React developers still prefer mixins -- react-router recently switched from mixins to ES6 classes and then changed their mind "until ES6 classes have better a…
> we should probably /also/ add a ES6 base class as a second option, and let the people choose which they prefer. Please provide a higher-order component or ES7 decorator (assuming ES7 will be supported?), would rather not use inheritance.
Earlier quoted context omitted.
Its the javascript community as a whole that is divided, generally between imperative/OOP and functional devs. Has nothing to do with Node or otherwise. Even if you like classical inheritance, the Class keyword is poorly implemented for it, from both a normal OOP language's point of view OR from a prototypal inheritance point of view. It's bad at both.
Classes are fine if you understand they're just syntactic sugar for the already extremely widespread constructor+prototype pattern. The primary reason a significant part of the community hates the ES6 classes is that the class keyword is misleading for people who don't understand prototypal inheritance. The OOP vs FP divide is orthogonal to that as the FP devs in question generally disagree with the constructor+proto…
You forgot about Purescript:
> Meteor: the missing infrastructure for building great React apps Extremely bold words as usual. I don't think I've ever seen any JS technology that manufactures as much hype as Meteor. Every single article from Meteor makes it sound like the best thing since sliced Jesus. Are there any reliable numbers on Meteor adoption (and retention)? If you listen to people using Meteor it's already more popular than jQuery but…