I'd love to sign up and check it out but your signup page is using HTTP (no ssl), and I'd prefer not send a password over the internets in clear text. Throw some SSL on that baby and I'll come back.
It's not about opening up safari or chrome. HTML5 "apps" are simply a browser window and the guts are implemented in HTML/Javascript/CSS. This is how LinkedIn's app used to work and it is the basis for Phonegap (which powers most HTML5 based apps).
The memory management bit Prasad references is a big deal too. Can you imagine not being able to release a feature that you've invested a lot of money into because you've got a performance problem or crashing issue that the tooling is not good enough to let you solve?
The BBC calls him a scammer. I call him an entrepreneur!
Corporate life doesn't agree with this fellow. Assuming he's not facing any lawsuits it sounds like a great time to launch his own software firm (where he outsources the work of course).
Or - he could go into consulting to show companies how to effectively do outsourcing.
update your Gemfile and set the version you want. In my case:
gem 'rails', '3.2.10'
locally, run
'bundle update rails' which will update your Gemfile.lock
check-in and deploy your code. If you are using capistranso, the default 'deploy' task should handle everything for you. Otherwise, run 'bundle update rails' on your production server.
Which is in fact why it's probably wiser to list `gem 'rails', '~> 3.2.10'` (or 3.2.0 or anything) instead, and then `bundle update rials` will update you to latest 3.2.x (but never 3.3.x), in this case 3.2.11, instead of only to the exact version you specified (3.2.10, incorrectly).
The advisory also provides several workarounds that dont' require you to update Rails, all pretty simple ("drop a file into config/initializers and reload) which also work.
Having just finished upgrading my production rails because of today's news I thought I would pass along a how-to for rails 3.x
update your Gemfile and set the version you want. In my case:
gem 'rails', '3.2.10'
locally, run
'bundle update rails'
which will update your Gemfile.lock
check-in and deploy your code. If you are using capistranso, the default 'deploy' task should handle everything for you. Otherwise, run 'bundle update rails' on your production server.
