Slashdot Mirror
Apple Publishes Ruby On Rails Tutorial
bonch writes "Apple has noticed the high amount of Mac usage in the Ruby on Rails community and has posted an illustrated Ruby on Rails tutorial. The document goes into more concise detail in getting new users up to speed, from database schema to moving beyond scaffolding, all done with the favored Rails editor, Textmate."
Jobs: Ruby is groovy man. It's got like, vibe. We had to get in on that.
.NET offers more flexibility with less development worries and higher performance...
.NET can accomplish all the same....
.NET does all this! Why won't anyone listen? You believe me right?
Gates: C# with
Jobs: Man! Talk about Squaresville! Ruby is hip man! It's a love machine. A child of the earth.
Torvalds: Ruby is based on perl, which is in turn based on bash scripting, which I like.
Jobs: You see man! Ruby is a free spirit. It grows in like, the sunshine. It doesn't obey your rules!
Gates: But it's just another paradigm.
Jobs: On Rails man! Rails!!! It's like hyperspeed into the cosmos. And that's why its fit for Apple's attention. Now if you'll excuse me, I have to go get some podcasts over rss, browse some blogs, do some yoga. You dig?
***Jobs walk's away clicking fingers rhythmicly***
Gates: But it's all just flash and hype. Nothing really new is going on!
Torvalds: Look man. I really just don't give a shit.
May the Maths Be with you!
The authors of rails books need to stop writing tutorials and write some comprehensive documentation. Even the page is quite lacking.
:discard_year => true)
:discard_year so the whole exercise is quite fustrating when you do find the docs, but i can live with bugs that will be fixed)
For example, suppose you have a time field, not a date field, no year, just time. And you want to create that element in your webform.
If it were date, you'd use date_select, pass it the name of the object and the name of the field, and your done, you get a nice input box. Suppose you want the same thing for time, its still date select with a series of discard attributes, e.g.
date_select('meeting','starttime',
However, you as the person looking for the documentation for this are led on somewhat of a goose chase becuase your time input box information is not even close to what you'd expect (time_select perhaps?) and you should be looking under "date" for "time".
(Incidentally, Rails 1.0 has a bug where it seems to ignore
If religous zealots don't believe in Evolution, then why are they so worried about bird flu?
I've been spending quite some time working on it on an OS from Redmont. I'd reckon the experience can be compared to that on any *NIX/BSD you prefer.
o c111133460
The main things I have to say about tools is: I haven't found the right tool. Yet.
The scintilla-based editor that comes with rails is ok, but no more than that. I'd prefer an IDE, with some project management and such. It seems like there are some possibilities with eclipse. http://www.napcs.com/howto/railsonwindows.html#_T
But I still have to check that one out...
Because it's probably not fully tested to work with Tiger. The only system updates you get with Software Update and bug fixes and security fixes. Occasionally you'll get something else which works behind the scenes with an updated iApp as well (there have been minor CoreImage and other framework pieces updated this way).
This is just good sense, it's stability vs. cutting edge. Also it can be a very bad thing to update the system incrementally (Ask Microsoft who have been bitten by this many times... often updating one thing can have unexpected results on others.
Also, for a developers interested in using Rails, updating Ruby is fairly trivial. I would also add that often even if Apple includes the latest version of something you may want to compile it yourself anyway (Apache, PHP. MySQL are good examples of things that people will often *upgrade* right out of the box).
--- Nothing To See Here ---
See also this screencast for a comparison of Ruby on Rails, Zope (Plone), TurboGears, and Django. Oh, and J2EE which fares ... rather poorly in my opinion.
Warning: the screencast is 36 minutes long!
Hey, Guys! Get with the programm. Ruby on Rails is so last-season.
Django is where the musics at. And for good reasons too. It's more mature, easyer to use, faster in developement, less performance hungry, has a documentation that's up to date and has a grown up backend kit. It's only that they GPLd it last summer, that's why it hasn't gotten all the press yet.
And this is not to start a flamewar. Compare them both and you'll see what I mean.
The RoR and Django guys are good friends btw.
We suffer more in our imagination than in reality. - Seneca
i'm kind of bummed that they didn't mention Locomotive, which really makes getting started with Rails very very easy. it seems like every Rails tutorial starts with "OK compile Ruby, install Gems, install Rails, install and configure MySQL, and 10 hours later, you can use this really simple framework!" when with Locomotive and SQLite3, you can basically just download one app, click two buttons, and start typing.
Just raise the taxes on crack.
Umm, the guys who write Web development tutorials for Apple are probably not the same guys that code the OS and applications. This tutorial wasn't actually written by Apple, they are just distributing it. You know the guys in finance are still working on accounts and haven't stopped to try to fix bugs in code either. I've been annoyed by Apple's weird handling of metadata versus extensions since they announced it but you are way off base in complaining about this as if it had some relation to security issues.
No - it is a killer app for getting mentions on Slashdot. Having a development system with the relative lack of performance of Ruby, and the very close tie-in to the database and schema of Rails is more of a website killer than an killer app, I am afraid to report.
I'm with Decaff on this one. I drank the RoR kool-aid after one of the earlier posts to slashdot. The first few weeks was awesome. Then essentially what happened was I ended up trying to rip out every aspect of RoR until I was just left with Ruby... which had terrible performance.
If you're going to go with RoR, make sure you take the long view. While everyone says "it scales, because it has FastCGI", I'd really like to hear more about extreme high volume sites that are using it. How's it going for them?
I use it extensively (every day) to develop large, internally-focused applications. Our production environment is Linux Debian, while our development environment is (ugh) Windows.
We use Eclipse with the RDT plug-in for Ruby. It's quite nice. Not as great an IDE as IntelliJ IDEA, but pretty good. There's not much Ruby-specific functionality in Eclipse yet that I can see, but it's certainly better than a basic Windows editor.
We also use PostgreSQL, which has been very nice, stable, and fast. We've never had any problems with it and ROR. We use phpPgAdmin to administer it on production and pgAdmin III to administer it on development, both of which are fairly good database browser/query tools.
So far the experience has been great. More worrying than the tools is ActiveRecord, which has a lot of nice features, but a few really glaring holes.
I don't understand why someone would want to use Ruby on Rails on Mac OS X, when WebObjects comes with the developer tools, is an enterprise-class Java app server, and is way faster in both development and deployment (on Mac, Windows, Unix, or Linux) than anything else I've seen.
It really is the best kept secret in the web app world. If you've not tried it, you might want to give it a shot.
I have been going to WWDC for three years now. Every year during the feedback sessions people always ask the same things.
1) How come you hate webobjects developers so much.
2) When are you going to get a decent package management tool or formally adopt darwinports.
Every year the answers are the same.
1) We don't really hate you guys, we really love you, we neglect webobjects on purpose.
2) We are apple, neither darwinports nor pkgsrc, nor fink is good enough for us. One day we will write a really cool one just watch.
It would be funny if it wasn't so sad.
evil is as evil does
I'm in the middle of writing a fairly substantial website in Rails. The first iteration of the site, everyone could do everything to every bit of data. The second version? I added one line of code to the parent of my controllers:
:authorized? :except => ['show', 'list', 'index']
before_filter
The authorized? function redirects users to the login page if they're not already logged in. So the result is, it's trivial to add validation code before every single action that makes changes to the database. If I want to add a function that validates that the person making changes is the person who owns the object being changed, that's one more function and one more line of code. I haven't done it, because it's supposed to be a collaboration tool where people are encouraged to edit each others' work.
You can do similar things to the models, defining actions and checks that have to happen before a database entry can be changed.
I'm really not seeing the point of your rant. If you want security on Rails, it's easy to go from zero security to total lockdown, then back off until the app is functional.
You want the truthiness? You can't handle the truthiness!
"* Migrations are "database agnostic""
As long as your database is mysql. If it's anything else you have to take your chances. Postgres is supported pertty well, everybody else can go fuck themselves because it won't work at all.
evil is as evil does
Catalyst is the hot new Perl based Model-View-Controller framework. It's been out for about a year, it's production ready easy for any competent programmer to work with, and backed by massive collection of libraries on CPAN. It has a large friendly and active user community, which you can find via the website.
Me, I'm using it for lots of things - my project of the moment is gluing in some of the tasty AI modules on CPAN into it for automatic classification.
"...we should just trust our president in every decision that he makes and we should just support that." B.Spears 2003