You know that Walmart, and gas stations, and bodegas sell these already right? That's why this is a bad idea. Not only is this less anonymous from buying from Walmart, but it's more expensive as well.
To expand a bit on with tikhonj is saying, consider the type signature of map:
map :: [a] -> (a -> b) -> [b]
In an implementation of map with this signature, the only way to get a list of b's is to use the function passed in. So, there's no way to do the array unwrapping shenanigans from the js example.
Almost no-one really needs to write code like your “bad”
example today, and even if they do, it’s the sort of thing
you only do once and wrap up in your own library so you
can reuse exactly the ideas you need and optimise it using
the same tools as any other JS you write.
If you're going to do that, it'd be good to open source it so other people can take advantage of it. Maybe abstract out some other cross browser stuff as well. Also, it would cool if it made the DOM api nicer to work with.
Have you experimented with typed channels (http://doc.akka.io/docs/akka/snapshot/scala/typed-channels.h...) at all? I've played around with them, and they seem to work pretty well, but don't seem to compose with the other "extensions" (e.g. the FSM one)
So, I just tried this out. I think it would be a lot more user friendly if you could see what "spells" are available when making a new spell (i.e. have auto completion in the text editor). It's a pain to have to look at the spell book, and limits experimentation.
We took inspiration from the great work Tom and Mike did on Meteorite; several of 0.6.0's features are essentially versions of what Meteorite let you do, except for much more deeply integrated into the core. For now, Meteorite is still a great tool for installing packages from Atmosphere into your app... a fully integrated third-party package repository is in the works but isn't part of 0.6.0.
If you wanted to implement a package that uses something Meteor specific (aka another Meteor package like Meteor.Accounts) you would still want to create a meteorite/atmosphere package instead of a node package right?
It's absolutely insane if they are using Mongo as their source of truth (and not say some kind of caching layer). If there is one thing that should be ACID, it's financial transactions.
