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.
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.
Ah, I see. I stop by seaside.st every once and a while, and it doesn't seem to have been updated with any new news for a long time. It would be cool to mention some of these developments on its front page.
"Startups identify with JavaScript. When you’re just starting out, you need to be dynamic. You need to be flexible. You need to be able to bust out a prototype that just works, and you need to be able to change it on a dime without recompiling your code. JavaScript was once the startup of the browser wars, and it crushed Java and Flash for the same reasons that startups have the ability to disrupt markets and displace the established players: agility and flexibility."
What nonsense.
1) " When you’re just starting out, you need to be dynamic. You need to be flexible. You need to be able to bust out a prototype that just works, and you need to be able to change it on a dime without recompiling your code."
Unlike Perl, PHP, Python, Ruby, any of the Lisps, Lua, etc.? The real reasons js is interesting on the server side is code sharing and node's (flawed) concurrency story.
2) "JavaScript was once the startup of the browser wars, and it crushed Java and Flash for the same reasons that startups have the ability to disrupt markets and displace the established players: agility and flexibility."
Comparing apples to oranges. Also, the term "browser wars" means browser vs. browser, not embedded scripting language vs. plugins.
Just curious, why can't you get a computer? You'd be better off with even a 10 year old model than an iPad, if for no other reason than having a keyboard.