Re:Meteor 0.4.0: Introducing Spark
by rbn on Saturday September 01, 2012 @02:34AM
(#4462851)
You guys should focus on authentication. Because this thing is practically useless without it. I'm aware of the authentication branch but this update broke it.
Re:Meteor 0.4.0: Introducing Spark
by edtechdev on Saturday September 01, 2012 @05:57AM
(#4463264)
There's no link to examples or a direct link to the relevant documentation. You have to figure out the difference between 'constant' and 'preserve'.
And one of their principles states: "One Language. Write both the client and the server parts of your interface in JavaScript."
Yet you still have to learn a separate template language, deal with the DOM, browser inconsistencies, etc.
To be fair, if you did do everything in javascript including the user interface, it ends up looking like java (see dojo, google closure, dart, qooxdoo). Javascript isn't well suited for a user interface or template language, but there are dozens of alternatives, some of which are more friendly to declarative UIs: https://github.com/jashkenas/coffee-script/wiki/List-of-lang...
Frankly, not having to write HTML/CSS and still getting Core Animation-style hardware-accelerated transitions and a normal Core Graphics-style `render()` function is really, really nice.
Re:Meteor 0.4.0: Introducing Spark
by tumultco on Friday August 31, 2012 @09:13PM
(#4462336)
It is probably named the same as many other popular products; "spark" is a common english word. With 7 billion people on this planet it is impossible to avoid naming collisions if you're going to use something from the dictionary.
Re:Meteor 0.4.0: Introducing Spark
by nmb on Saturday September 01, 2012 @01:29AM
(#4462742)
I agree that the name should be changed. If someone said they built their product "using Spark", it would be fairly ambiguous as to which one they meant, especially if their product has a data mining component.
Re:Meteor 0.4.0: Introducing Spark
by wylie on Friday August 31, 2012 @07:39PM
(#4462157)
From the linked article: "Spark weighs in at 8k gzipped and minified, including all of its dependencies, and it's easily separable from the rest of Meteor."
Re:Meteor 0.4.0: Introducing Spark
by bialecki on Friday August 31, 2012 @08:21PM
(#4462250)
I just looked at the Spark wiki page[1], and Sizzle is a dependency (although they say it can be removed if you're willing to ignore IE 7). So it is separable, but might not be that small depending on your audience.
Re:Meteor 0.4.0: Introducing Spark
by tiglionabbit on Friday August 31, 2012 @06:14PM
(#4461915)
Yay, more data binding libraries. This one needs some better examples before I'll be able to understand at a glance how it works. I currently do my data binding with AngularJS.
Re:Meteor 0.4.0: Introducing Spark
by jjaques on Friday August 31, 2012 @07:23PM
(#4462118)
You're right, it runs on Node. However as the poster above pointed out, there would be little practical use in combining this with another framework. Meteor is really it's own platform. The whole point is the unification of the client and server codebase.
I'm not sure about Ember, as I believe it tends to be more opinionated about how much of the page it controls, but Knockout and Backbone are generally pretty easy to use for just a portion of the page.
Steve Sanderson (creator of Knockout) has a really good overview of the most popular client side options (both libraries and frameworks).
I'll never use anything made by people so careless yet so self-aggrandizing about their own work.
And one of their principles states: "One Language. Write both the client and the server parts of your interface in JavaScript."
Yet you still have to learn a separate template language, deal with the DOM, browser inconsistencies, etc.
To be fair, if you did do everything in javascript including the user interface, it ends up looking like java (see dojo, google closure, dart, qooxdoo). Javascript isn't well suited for a user interface or template language, but there are dozens of alternatives, some of which are more friendly to declarative UIs: https://github.com/jashkenas/coffee-script/wiki/List-of-lang...
Or iOS, see Blossom: https://github.com/fohr/blossom
Frankly, not having to write HTML/CSS and still getting Core Animation-style hardware-accelerated transitions and a normal Core Graphics-style `render()` function is really, really nice.
[http://www.spark-project.org/]
Meteor Spark looks pretty nice though; look forward to trying it out.
[1] https://github.com/meteor/meteor/wiki/Spark
Btw, this feature sort of already exists in jQuery. http://api.jquery.com/link/
I like the realtime concept/behavior but I want to keep developing in django.
It doesn't do live templating, though.
How does rails fit into that picture at all?
Backbone.js and Ember.js are already great for working with rails/REST apps...
Maybe this is an ignorant question -- but how would you integrate it into a Rails app?
I'm not sure about Ember, as I believe it tends to be more opinionated about how much of the page it controls, but Knockout and Backbone are generally pretty easy to use for just a portion of the page.
Steve Sanderson (creator of Knockout) has a really good overview of the most popular client side options (both libraries and frameworks).
http://blog.stevensanderson.com/2012/08/01/rich-javascript-a...
https://github.com/dkastner/nodeify