Just started using Meteor + Telescope on my site TravelMo.re and love it so far. Really easy to use, kind of a pain in the butt to deploy.
Meteor hits 1.0
71–80 of 250 posts
Re: Meteor hits 1.0
#72Just started using Meteor + Telescope on my site TravelMo.re and love it so far. Really easy to use, kind of a pain in the butt to deploy.
Could you elaborate on why it is a pain to deploy? I've never used Meteor but I thought one of the selling points is ease of deploy, hot code pushes, stuff like that.
Re: Meteor hits 1.0
#73I'm still a bit unclear on what the target market for Meteor is. Is this just for small to medium sized projects, or is it intended to be used for large-scale projects as well? Since it seems like everyone wants to think of themselves as doing something huge, I'm sure the answer can't be 'no' to the second question — but I don't see any examples of significant projects being built on the platform. Actually, with that…
It's definitely a win for hackathons and getting a MVP out there that needs real time features. I can't speak much for large scale projects since I haven't had the fortune of reaching that scale yet with meteor, but I'd imagine it will be ideal for that eventually simply by extrapolating the current growth and improvement trends of the framework.
In terms of complexity, the software I'm developing in Meteor has a lot of moving parts (animation, physics, artificial intelligence, and hardware integrations) and Meteor has handled it all tremendously well. In terms of user scale, I haven't had much experience, due to the nature of the project. It has made our development team tremendously happy, and provided a tremendous amount of flexibility compared to other approaches we've tried in the past including Objective-C and Java.
Re: Meteor hits 1.0
#74Re: Meteor hits 1.0
#75I haven't looked at Meteor in a while, but am really impressed with how the vision of Meteor and the code (and of course the website) have evolved. Meteor looks extremely simple to get up and started with, and I was thoroughly impressed by the implicit modularity of it all ("meteor create" makes like 3 files, I think that's awesome) They really try (and succeed) to rid ourselves of the duplication on server and clien…
Phonegap development is still phonegap development, even with Meteor. That said, I built a prototype chat app and deployed to iOS in about an hour. It really was that easy, and the app runs terrifically well. The "write once, run anywhere" mantra is a little more real with Meteor than with other approaches I've used before.
Re: Meteor hits 1.0
#76Earlier quoted context omitted.
At last months devshop in SF a speaker discussed straining the system and reaching the limits of Meteor with just hundreds of simultaneous connections: https://www.youtube.com/watch?v=cJbGNpmE7f0&t=8m30s Hundreds isn't really exactly "webscale", but I'm sure they'll iron it out, or it could have just been the application that was at fault. It's one data point however on how meteor scales.
[I work at Meteor and contributed to the MongoDB realtime driver] Scaling low-latency data synchronization is a challenge for scalability for sure! We are gradually building better and better drivers with persistence to MongoDB. The scalability can vary greatly depending on your application's data schema, usage patterns and amount of writes. If you watch the mentioned talk carefully, the speaker describes a collabora…
The "running from a single box" at the end seems like it could be the most important part of the equation. Would you agree? Or rather, would that be the recommended place to start optimizing if your app runs into scaling problems?
Re: Meteor hits 1.0
#77First of all - absolutely love meteor. Couchbase/CouchDB support would be fantastic! More (NoSQL) database support would be fantastic. I worry that it's so MongoDB specific now and the "scale" technologies are MongoDB specific (Oplog tailing only) that adding other databases in the future will become a lot more difficult.
Re: Meteor hits 1.0
#78Here's the official blog post announcement for Meteor 1.0: https://www.meteor.com/blog/2014/10/28/meteor-1-0
Re: Meteor hits 1.0
#79Kudos, Meteor team! Now, SQL, please...
You can have SQL already, use ddp methods to query a database on the backend. It's not reactive, but it enables you to use SQL.
The data isn't reactively loaded in realtime, but Meteor itself is still reactive. What I mean to point out is that even if you're depending on say classic JSON APIs, the meteor app within itself can still do reactive-features (templates, local collections, etc). And depending how you implement things, you could still take advantage of push capabilities for your data from a legacy endpoint.
But yes, I agree, it's not ideal until a SQL adapter is available.
Re: Meteor hits 1.0
#80Earlier quoted context omitted.
Basically, yes to all. In terms of scope it's roughly as encompassing as something like Rails - it's full stack.
Ah thanks. But if Rails is my coding platform of choice how does this integrate into it?
It doesn't, this is a separate coding platform. If your coding platform is Rails, you don't integrate Django into it.