Glad to see that they went with Atmosphere. Meteor has done an incredible job at adopting 3rd party implementations as their official packages.
Introducing Meteor 0.9.0, the Meteor Package Server, and Isobuild
11–20 of 64 posts
Re: Introducing Meteor 0.9.0, the Meteor Package Server, and Isobuild
#12What is Isobuild? The blog post doesn't actually say, and Googling [meteor isobuild] just turns up the blog post. (Is Isobuild the tool that implements "proper single loading?")
In fact, it was explain in the post but was removed a few hours later (perhaps too much info on one news).
It was about the fact that you can code the same way on server, browser, mobile.
Example was that you can use Http package everywhere with the same function and have the same result.
And the other example was the Cordova integration. The build system can generate the code for the whole distributed system (not just the browser).
Re: Introducing Meteor 0.9.0, the Meteor Package Server, and Isobuild
#13Earlier quoted context omitted.
Live updates were implemented with listening to MongoDB replication log back on 0.7.0: https://www.meteor.com/blog/2013/12/17/meteor-070-scalable-d... This is a much more efficient way to get updates from the database and it also scales horizontally to multiple application servers (and multiple MongoDB replicas!) If you are curious how it works, this talk is a good start: https://www.youtube.com/watch?v=_dzX_LEbZyI
Very cool, thanks. Is server side rendering coming soon as well?
The roadmap of Meteor includes "Server-side rendering" planned after 1.0. https://trello.com/c/Lz07fBAm/7-server-side-rendering
In my opinion, server-side rendering is a bit overrated since Google knows how to crawl ajaxy apps. SEO is a big concern but you can always render your pages with phantomjs (also a popular approach in the Angular world) or rely on Google being smart.
For rendering the page to the end-user, Facebook is not rendering everything server-side, nor does Twitter. I don't have enough knowledge why, but one of the FB engineers told me that it is not really faster: you need to render it twice, send the same data possibly twice, it is hard to correctly chip into the events made on the page, etc.
Re: Introducing Meteor 0.9.0, the Meteor Package Server, and Isobuild
#14I cannot recommend Meteor enough for a large class of web applications. I've written 3 apps now using it and find it solves a good many of the problems inherent in more "typical" JS app app stack like rails + backbone.
Re: Introducing Meteor 0.9.0, the Meteor Package Server, and Isobuild
#15As a developer and maker, one of the most important things is to ship. And as someone who is not a self-professed [insert programming language] ninja or a full-stack this or that, I can safely say that Meteor has made it much easier for me to iterate and ship. I expect that as I grow, Meteor will continue to grow as well. Excited to see Meteor get closer to 1.0.
Re: Introducing Meteor 0.9.0, the Meteor Package Server, and Isobuild
#16If you're thinking about using Meteor for something important, now that they're at 0.9.0, don't.
Meteor still doesn't have a UI component API, so making reusable, reactive interface components is basically impossible (or far more difficult than it needs to be). There's a deliberately undocumented and incomplete API that's supposed to help a little bit, but you're basically out of luck if you don't want to write spaghetti code right now.
Instead of shipping an API we can use, they're holding out for the "perfect" one. I wish I could go a year back in time and build my project with Angular instead of Meteor.
Re: Introducing Meteor 0.9.0, the Meteor Package Server, and Isobuild
#17Earlier quoted context omitted.
Very cool, thanks. Is server side rendering coming soon as well?
The roadmap of Meteor includes "Server-side rendering" planned after 1.0. https://trello.com/c/Lz07fBAm/7-server-side-rendering In my opinion, server-side rendering is a bit overrated since Google knows how to crawl ajaxy apps. SEO is a big concern but you can always render your pages with phantomjs (also a popular approach in the Angular world) or rely on Google being smart. For rendering the page to the end-user, F…
I'm more concerned with end user page load speed than crawling. I find Facebook and Twitter pages annoyingly slow to load, personally. Sure, server side rendering is difficult but it's exactly the sort of hard problem that a framework ought to be able to solve for you.
Edit: actually I just went to twitter and it loaded pretty fast, so I looked at the network requests and they do server side rendering for your timeline.
Re: Introducing Meteor 0.9.0, the Meteor Package Server, and Isobuild
#18You can try and use Meteor 0.9.0 in a Terminal.com container. I just created a snapshot for it at https://www.terminal.com/tiny/cb3Rc2NLlE
Re: Introducing Meteor 0.9.0, the Meteor Package Server, and Isobuild
#19What is Isobuild? The blog post doesn't actually say, and Googling [meteor isobuild] just turns up the blog post. (Is Isobuild the tool that implements "proper single loading?")
In fact, it was explain in the post but was removed a few hours later (perhaps too much info on one news). It was about the fact that you can code the same way on server, browser, mobile. Example was that you can use Http package everywhere with the same function and have the same result. And the other example was the Cordova integration. The build system can generate the code for the whole distributed system (not ju…
(MDG-er here) Yup, we decided to break it into two parts! Expect a blog post on Isobuild very soon.
Re: Introducing Meteor 0.9.0, the Meteor Package Server, and Isobuild
#20What is Isobuild? The blog post doesn't actually say, and Googling [meteor isobuild] just turns up the blog post. (Is Isobuild the tool that implements "proper single loading?")
(MDG-er here) Expect a blog post on Isobuild very soon... :-)