Domain: robbyonrails.com
Stories and comments across the archive that link to robbyonrails.com.
Comments · 9
-
Re:The OS maketh the Mac?
When it's completely painless and everything "just works" I might agree with you.
I'd be careful about defining a system's Mac/not-Mac status in terms of things "just working". OSX on Apple's approved hardware configs will work without problems for most day to day tasks - but I've seen plenty of tasks where naive assumptions can and will stop things from working.
Unless a Mac intended to run Supercollider and Quarks or MySQL (for instance) ceases to be a Mac in your definition, I think you'd be on safer ground simply arguing that "Macness" requires both OSX and Apple-approved hardware. -
Re:Good old RubyOnRails
Community all depends on whether you're doing things The Rails Way or not. (In fact, one of two books I've read to teach myself Rails was called "The Rails Way.")
But just look at a couple examples of why people run away from the community. (For those who don't know, the second example is DHH, creator of Rails.) -
Software sucks because there isn't enough Dialogue
This is an area of software development that I drool over. I'm so fascinated with all the variables that go into the success of a project. Beyond the technical aspects, the human to human problems that arise seem to be the biggest problem in software development. What's the problem? Oddly enough, I posted the following this article on my blog yesterday. I think something can be done about it. I believe it starts by seriously acknowledging that there is a problem.
-
PHP, or Ruby?
Seems like Ruby on Rails is competing for web apps too - lots of comparisons are floating around out there. Some large sites are converting over, too, like Derek Siver's "CD Baby" - he blogged on the conversion here.
I've certainly found Rails to be a good fit with interfacing with a Jabber PostgreSQL backend. Good times! -
Re:Ruby on Rails only works on MySQL
PostgreSQL works with Ruby on Rails!
If it didn't, I wouldn't be so in love with it :-)
-
Rails and legacy databases
Quite a few people have dismissed Ruby on Rails because they think that it enforces a set of rules about how to structure your database. I am currently writing, Programming Rails for O'Reilly and have posted numerous articles on my blog on the topic of Rails and Legacy database systems. Rails can be molded to fit your existing infrastructure with very little effort. It's all I have been using for new projects since last spring... and that was when I started learning Ruby as well.
PostgreSQL + Ruby + Rails = the next (lamp)
PRR, RPR, RRP... we need a cool acronym -
Rails and legacy databases
Quite a few people have dismissed Ruby on Rails because they think that it enforces a set of rules about how to structure your database. I am currently writing, Programming Rails for O'Reilly and have posted numerous articles on my blog on the topic of Rails and Legacy database systems. Rails can be molded to fit your existing infrastructure with very little effort. It's all I have been using for new projects since last spring... and that was when I started learning Ruby as well.
PostgreSQL + Ruby + Rails = the next (lamp)
PRR, RPR, RRP... we need a cool acronym -
Stored Procedures!
Above all things... this is one of my favorite features of PostgreSQL. MySQL has nothing of the sort. Procedural Languages... yum. I recently showed on my blog how I could interact with an instance of DRb from inside of PostgreSQL. How cool is that? MySQL has nothing like this. I'd also guess that a majority of the applications that use MySQL could use SQLite instead and as soon as that becomes more popular, we'll see less MySQL usage.
-
Some demos to try
A bunch of people posted specific projects to try out on my blog:
rails day projects to try