Meteor is awesome, congrats to the Meteor team for their 1.0 release! I've been using Meteor for over a year now, and it is staggering how far it has come. They've addressed and continue to address just about any concerns the community has brought up, from security to speed to tools, etc. And where they haven't, the community has stepped up huge. Seriously, Meteor is amazing, but what makes it even better is the awesome community surrounding it. Congrats again.
Meteor hits 1.0
231–240 of 250 posts
Re: Meteor hits 1.0
#232What is the status of supporting Redis. I'd be more excited if I could use my favorite instead of Mongo.
I and another Core Dev Justin SB worked on the Redis support for a month: https://atmospherejs.com/slava/redis-livedata
It has seamless support for hashes and strings, miniredis, latency compensation, user input validations - similar features to MongoDB integration.
Right now you need to start the Redis server and set up the KV observations manually once for every Redis server you intend to use.
This support was experimental and we didn't develop it further from there. We told our community about it on a Meteor Devshop but there wasn't much interest. If there will be more interest, we will continue developing it.
Re: Meteor hits 1.0
#233FYI: this link gets me into a redirect loop (probably because of something NoScript related)
Don't expect to see meteor-based sites work with JS disabled.
Not a huge fan of this turn of events, either...
Re: Meteor hits 1.0
#234I'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…
I'm wondering if it's true usefullness is potentially in an Enterprise supplemental tool to cobble together some quick apps, maybe like what MS Access was used for a long time ago, except this time you get nice browser-based, reactive applications.
I'm not sure you'd use it to build the infrastructure of your startup on. Or a content heavy site. But I see building tools like for managing a lot of developer instances, internal tools for config, etc to possibly be pretty sweet for this.
Re: Meteor hits 1.0
#235I'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…
Meteor just hit 1.0 and is not the type of framework you can just start including in your stack. You really have to build a meteor app from the ground up, so it is hard for established tech companies to get into Meteor when they already have spent years coding on another stack. As new startups who use Meteor grow you will see those large-scale projects come about.
Actually, you can use Meteor as a frontend-only framework. Just have the Meteor server be the client for a standard REST API. I've built an app using this approach.
Re: Meteor hits 1.0
#236Earlier quoted context omitted.
I'm not really confident about new version the releasing of version 1 was too long. Also I do not see a strong open community that support them like Rails, Django o Node. Of course I wish them to grow in terms of contributors
There is a pretty distinct and active Meteor community, though from the outside it's hard to tell how much of that is just people who are interested in it because of the hype (kinda the problem MongoDB had) vs people who actually use it and know what they are doing. I wouldn't say the wait for 1.0 is a good indicator of stability or success, though. Node.js is still at 0.x and so is React. AngularJS took a long while…
There is this tiny detail about Meteor, that is has been funded $11.2 million.
- https://www.meteor.com/blog/2012/07/25/meteors-new-112-milli...
Re: Meteor hits 1.0
#237Earlier quoted context omitted.
Sky is the limit here. Low latency (real-time) can be an important part of effective and engaging communication. Sure, it's not for everything; I wouldn't want my email communicating word by word to my recipients as I typed. However, enterprises usually involve a lot of communication - with team members, stakeholders, and clients. - there are many opportunities to spice things up and make them more engaging & effecti…
In what specific industries are these needed? I'm curious as to how I can build an enterprise app in meteor.js.
You want a list of industries, that involve communication with team members, and customers?
I think you need to take your curiosity to google (or the real world), and do your own research.
Re: Meteor hits 1.0
#238Earlier quoted context omitted.
In what specific industries are these needed? I'm curious as to how I can build an enterprise app in meteor.js.
You want a list of industries, that involve communication with team members, and customers? I think you need to take your curiosity to google (or the real world), and do your own research.
okay I just wanted to get your opinion.
Re: Meteor hits 1.0
#239Earlier quoted context omitted.
I'm doing a rebuild of a personal project over the holidays and I spent some time looking into binding together React, Airbnb's Rendr, and JSX through Browserify and Grunt. It's possible, but it's a nightmare. Meteor definitely succeeds and just delivering that. (Not that that is the only requirement you might have.)
I'm using React. My server-side rendering is essentially `React.renderComponentToString(App(data))`. The only difference between how I invoke my app on the server vs on the client is that instead of `React.renderComponent` I use `React.renderComponentToString`. On the client, React just uses the pre-rendered HTML and binds itself to that without re-rendering a single DOM node. All my scripts are in `package.json`. I…
I agree with you that it probably is not easy to pick up, but I have to admit, there is significantly less to deal with. Meteor is the fullstack, and it even has sockets built into it. You definitely have to buy into one ecosystem, and that's convenient because you don't have to know a serverside ecosystem (e.g. Rails) and a frontend ecosystem (e.g. Angular, React, and Ember).
Re: Meteor hits 1.0
#240There's a lot to like about Meteor. Just compare setting up some kind of "dream team" of JavaScript: Rendr + React + Grunt + JSX = OMG WHERE DID MY FRIDAY NIGHT GO. Meter out of the box "just works," but it only works with Mongo for now, and it only works if you are all-in with the platform — on both the client and the server side. Those are two pretty big bets to make. I would say Meteor is ideal for learning, excep…
First of all, why is JSX in that list? It's essentially an ES6 transpiler with syntactic sugar for nested function calls. If you mean the additional build step it requires, that doesn't really make sense either: you should be bundling and minifying your client assets already and JSX is just another (fully transparent) link in the build chain. Secondly, why Rendr? Rendr was built for Backbone. The most recent info I c…
I am still using Grunt, and have been wondering how Gulp is. How do you like it? Why is it better?