Ajax On Rails

mu-sly writes "Ajax and Rails - probably two of the biggest buzzwords in web development at the moment. In this article over at ONLamp, Curt Hibbs introduces the incredibly powerful Ajax support that is part of the Ruby on Rails web application framework. It's a great read, and serves as a gentle introduction to the cool stuff you can accomplish with ease using the Ajax features of Rails."

Comments

Well, let's see here.

[Anonymous Coward]

the "Traditional Web App" is still running, but the "Ajax Web App" is down.

This tells me everything I need to know about this amazing technology :-P

Memcached exists for a reason.

[Some Random Username]

Try it before talking out of your ass. Its not an ad-hoc network cache system, its a simple, VERY FAST cache that stores objects in RAM. If you are too stupid to grasp why this helps, go read about how it saved livejournal thousands of dollars that they would have had to spend buying a huge DB server and still had worse performance.

Seconded.

[leonbrooks]

Cyberax, you come across like a VB programmer bagging PHP or mod_perl. Your conversation resonates from keel to crowsnest of exactly the kind of tunnel-vision MoeDrippings mentions.

Would you care to give us a bit more context? Maybe a page or two on what you're actually trying to achieve, rather than just stating that specific features were absent (when they weren't) and then falling back on more bald statements that said features were inadequate. Something more convincing and complete?

Re:Ruby?

[Cthefuture]

Whatever... When building a system you should have goals. One of those goals should be performance related.

For example, if I had written Ruby one of my goals would be to have it run faster than the other systems I was basing it on. In this case that would mean at a minimum making it the same or faster than Perl. So as I was building the system I would constantly test performance to make sure it was meeting or beating the performance goals throughout the whole process. This requires no design work, just common sense.

Now they're going back and having to redo the entire thing. As a programmer I know how that goes. It's insanely difficult to stay motivated while redoing the same work as you did before (or even that someone else did before). Good designs are iterative in nature rather than massive re-writes. Ruby v2 has about as much chance of success as Perl 6... (ie. extremely unlikely)

Most programmers are idiots.