Cool Code
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Peter Cooper on Aug 08, 2006
As the Ruby on Rails framework celebrates its second birthday, Apple has announced that Ruby on Rails is going to be included with both OS X Leopard Server and Client editions, due for release in early 2007. A demonstrative package has also been included with the developer preview build of Leopard given to developers today at Apple's developer's conference.
David Heinemeier Hansson, the creator of Ruby of Rails, hails this as a great acknowledgment from Apple, particularly as all of the core Rails development team is Apple based, along with a large share of Rails users. And in connection with Rails' second birthday, David presents his feelings on Ruby and Rails' growth over the past couple of years:
So for my (delayed) celebration of Rails turning two years old, I salute all early adopters who dared stick their neck out and be the subject of ridicule from their suspicious peers.
Let’s share a brief moment of guilty pleasure for proving them wrong, then move on to the longer lasting pleasure of simply sticking to it for our own sake. And have understanding for those conditioned by past disappointments to classify all that is new and ripe with passion to be uninteresting, to be all hype, no calories.
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
Mobile and the New Two-Tiered Web Architecture
SCM best practices for multiple processes, releases & distributed teams
What is the purpose to include RoR in OS? If you want to develop RoR-based application you can always download framework from the net and do it. It's really simple.
The only reason I could imagine is marketing:- Look, OS X is so developer friendly, isn't it?
- Wow! Cool, lets buy some for our team!
But, do you think it isn't a bit... silly? We aren't youngsters, we are professionals. I hope.
Note: I'm not against Apple nor OS X. I wish I could affor one of this smart notebooks ;-)
Cheers,
Tom
I may be wrong because I haven't used an Apple machine, but I heard that configuring everything needed to put RoR to work is not so trivial (and currently the recommended way to do it is published "somewhere" on the net).
./alex
--
.w( the_mindstorm )p.
I imagine for the same reason that they include Apache and PHP. Because there are people that want it, the OS is *nix based so it's easy to do...
Installing a bare-bones rails stack under any OS will take anywhere from 5-10 minutes to at least 30 minutes to grab the packages or compile if binaries are not available. On my MacBook Pro it probably took 45 minutes to get it all together and I have done it many times. For those that have never done it it will take longer.
Also if you read the post at weblog.rubyonrails.com/2006/8/7/ruby-on-rails-w... you will see that it will be part of the "Developer Tools" install under the client OS (ie not in the default install) and included in the server version.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
3 comments
Watch Thread Reply