http://weblog.rubyonrails.org/2011/5/22/rails-3-1-release-ca...
69 karma · joined March 4, 2010
http://weblog.rubyonrails.org/2011/5/22/rails-3-1-release-ca...
ERB helpers seem to be the only way currently.
> {"JSON":"rocks!"}
I don't think this is such a good point. While the example is not a valid expression, it is a perfectly good JS value/statement, like (almost) all other JSON. Wikipedia might go a bit too far in saying that all JSON formatted text is legal JS code, but (IMHO) it still is a perfectly good subset.The unicode part is a clear error and should be fixed.
http://www.whatwg.org/specs/web-apps/current-work/multipage/...
First, HipHop doesn't support create_function, which is used in the example.
Second, feature mismatch between Ruby and PHP will make efficient compilation quite hard and most likely be far from optimal. The languages doesn't seem to be very easily optimizable either.
HipHop isn't a silver bullet either: sometimes it seems to be faster than cached PHP bytecode, but not always.
I wish my iPhone would be able to do this too, but it is probably a bit too much of configuration for Steve. Also, depending on your configuration, it could lead in breaking the semantics of the physical ringer switch.
For Mac OS X, there is an app which does pretty much what Locale does: MarcoPolo. I found it very useful when I needed to change SMTP server based on where I was.
Distributing binaries isn't feasible as they aren't portable. Chrome would like to address this by distributing LLVM bitcode[1] and then compile this to native binary using LLVM. Portable Native Clients were introduced as an idea one year ago, but AFAIK there hasn't been much development, mostly because LLVM itself isn't very portable.
If native clients would be the path for future web apps, we can't reasonably expect the whole world to switch to LLVM in one night. There would have to be some fallback. As both Portable Native Clients and Emscripten work on LLVM bitcode, Emscripten would be the natural choice.
[1] LLVM's name for their intermediate language, low-level bytecode
Simple recurring billing works quite well, except that you have no control over the subscription. Only thing you can do is to cancel it via PayPal interface. Multiple plans become quickly painful.
There's also Adaptive Payments API, which is available for non-US companies. PayPal doesn't really trust you: subscriptions are limited to one year in length, but you have the control of when and how much is billed (within limits of the "preapproval"). Adaptive Payments API is quite painful to use and is challenging from UX point of view. It's probably cheaper to incorporate in the US and use some other merchant gateway than to implement PayPal Adaptive Payments in your software.
While 24-bit audio won't directly help with bad mastering practices, it might indirectly encourage producing of records with higher dynamic range. And, 24-bits should also be enough to reach limits of human hearing in dynamic range, although I personally don't feel the need of reaching the threshold of pain.
Adaptive Payments was chosen as the standard recurring billing API doesn't allow us to automatically manage subscriptions, which becomes an issue if you have multiple plans. However, we had to implement billing scheduling ourselves. PayPal was for us the only option which didn't require us to store CC information on our servers.