It’s basically a SUPER SECRET invitation-only (150 ppl) 3 day camp out near O’Reillys headquarters in Sebastapol, California.
I am most definitely going to try my best to make it down for this. Camping + Free Wifi + Cool Geeks = Foo Camp!
No seriously, a guy from Micro$oft called me today. I was a bit afraid at first, had to remind myself that yes, I run Linux and OSX, I’m safe… I think. ;-)
Actually, in late July, they are helping host Portland Code Camp 2005, which is basically 2 days of FREE developer conferences.. but in a classroom setting. It will be held at Reed College (where Lucas just graduated from). It’s typically, .NET, MS SQL, etc related… the main group behind it is the Portland Area .NET Users Group (PADNUG). Basically, a bunch of stuff that I’m generally not too involved with unless its assisting with a migration away from their platforms. ;-)
It turns out that there has been some buzz about the Ruby on Rails hype and they’re interested in having me (or someone) come and give a presentation at the event. I have not said an officially yes or no, as I’m supposed to be going down to California towards the end of the month to visit family.
While I was talking with the guy from Microsoft (they are covering the costs for the venue…), he asked if I knew of any body that might also be interested in speaking on subjects such as open source databases (mysql, postgresql, etc..), Python, etc. They want to keep things local… so if you’re in the Portland area, shoot me an email and I’ll put you in contact with the right guy to talk to.
One thing that kind of amused me was some content on their site.
To create a little structure, we’ve proposed a variety of one- and two-day tracks including Hobbyists, Mobile and Tablet PC, Architecture and Patterns, Databases, Web Development, Client Development, Games Development, Tools, Methodology, XML and Web, and “Alternative Lifestyles” (Ruby on Rails, Python, Squeak, etc.)
Heh, Alternative Lifestyles. Not the worst label.. but when I think about .NET versus Rails, I feel like those folks are the ones who enjoy the pain. ;-)
Is .NET a fetish and is Ruby on Rails a fad?
If you haven’t seen this before, gmame has a nice graph of the Rails list.
Ruby on Rails:
versus… okay, I’m stretching here.. but the PHP-general list
Yes, Rails is a framework and PHP is a language, but it’s interesting how the PHP list hasn’t grown much in a few years (and doesn’t appear to be getting a whole lot more traffic than the Ruby on Rails list these days.)
The Rails community is growing quickly and I think that’s pretty cool to see. :-)
Every once in a while, there is a short debate about using MySQL or PostgreSQL with Ruby on Rails as a database server. If you know me at all, you’ll know that I am a strong proponent of using PostgreSQL. Putting some logic in the database is something that my last few jobs have completely trained me to do.
For example, I try to develop applications under the assumption that it will never be the only interface to the data set that it uses. In a way, I use the database as a part of the model and don’t put the reliance on the model in my Rails application.
For example, take the following example of updating a bunch of records that meet a certain requirement.
Items.find(:all, :conditions => "type_id='2'") do |item| item.x = "foo" item.save end
Is this method quicker than running a simple UPDATE query on the database? With a smaller data set, this might not be big enough of a concern. But, what if your database has a million rows that meets this criteria? Does it make sense to find them all first and then loop through the recordset one million times and call one million updates? A few problems might occur, one big potential issue is that it is likely that your application might go beyond the timeout of your server and there is no rollback with this transaction.
So, what is the best Rails-way to solve this problem?
If the request takes too long and times out, how do you ROLLBACK your updates automatically? I know how to do this with PostgreSQL (quite simply), but am curious as to how this is addressed by MySQL proponents.
Let’s take another scenario. Perhaps you have a table called foobars. Every time you INSERT or UPDATE this table, you want to add a record into table foobarlogs that shows what was added or what fields were specifically changed. With PostgreSQL, you could build a trigger that compares the existing record with the new values and then adds the differences into the foobarlogs table. This might not be something that people encounter, but for some systems, it’s vital that you know when something happened, by whom, and what exactly happened.
Step forward into the future. Client needs a new interface built for desktop usage. Yes, you could use Ruby with wxWidgets and build a nice multi-platform application. In your code, you deal with the same database. With your trigger in place, you don’t need to do anything but call it like you did with Rails.
Yes, MySQL is getting advanced features, but its still a while before you’re going to get to use pl/Ruby for building your database functions.
Wouldn’t this follow more along the lines of the DRY principal than doing this in the Rails code?
- A curious PostgreSQL-fan
PostgreSQL, all the features you need next year, available last year.
On a side note, here is a good explanation of how PostgreSQL is useful for certain application requirements.
A friend asked me earlier after he read some background on MVC... “According to the MVC pattern, a view should never know anything about the users input.”
He was reading this PDF.
Conversely, a view should never know about user input, such as mouse operations and keystrokes.
Thoughts on how to respond to him with a good answer?
It’s obvious that we use AJAX with controllers, but what about on a simple Toggle.display() ?