Why NoSQL Matters
" NoSQL" is a label which encompasses a wave of innovation now happening in the database space. The NoSQL movement has sparked a whirlwind of discussion, debate, and excitement in the technical community. Why is NoSQL generating so much buzz? What does it mean for you, the application developer? And what place does NoSQL have for apps running on the Heroku platform?
SQL (the language) and SQL RDBMS implementations ( MySQL, PostgreSQL, Oracle…
Second, the alternative implementations may not give you the low level access you need. For example, my file-temp library does not work with JRuby even though it uses FFI because JRuby cannot deal with low level file descriptors . That kills a lot of low level systems programming right out of the gate.
Third, the up front declarations, combined with cross platform support, are proving to be extremely burdensome. Consider a simple interface for the getpwent() function. …
…based on individual student needs. The topics we picked were " Ruby Versions and Implementations", " Metaprogramming", " Testing", and "Style and Substance". Though these may seem a bit amorphous on first sight, they do a pretty good job of covering four key topics that a budding Rubyist must understand and come to appreciate.
Here are just a few thoughts from each of the modules, after seeing how things played out in class.
Ruby Versions …
Last we've got a comparison of Rails 3 across four implementations ( Ruby 1.8, Ruby 1.9, Rubinius, and JRuby):
You can see that Rails 3 is significantly faster than Rails 2.3 across the board, and that all implementations (including Rubinius!) are significantly improved over Ruby 1.8. All in all, a great year for Ruby!
Next post, I'll talk about improvements in the Rails 3 API for plugin authors—keep an eye out, and as always, leave your comments!
…Haml and Sass instead of the usual ERB since I find those DSL implementations a bit more succinct.
More importantly, in this application I was faced with data that would steadily increase in size. I wanted to make sure that application performance remained constant, without becoming steadily worse as the size of data increased. With AT&T's current network woes, the last thing I wanted was to cause users to wait extra time for their app to load because of slow delivery speed …