unrelated to real life

[declasm]

OMG! I spent about 8-10 hours building a proof of concept J2EE struts web application - I was thinking that it was all going pretty well then someone comes along and starts talking about the 'ruby on rails' framework - I built an app with the same functionality in LESS THAN AN HOUR and I've never used ruby before in my life and I basically wrote

Comments

[jabbawokki]

wow darling, i have no idea what any of that meant, but i think i should be really impressed. you are a genius!

[threepymeepy]

lol, what a fantastic reaction :D

[jabbawokki]

haha! honesty is the key :p

[declasm]

thankyou my darling - it's a pity it's all unrelated to real life. mwah!

[declasm]

I was very suspicious about it - I also read the articles that said it was 10 times quicker than the other frameworks with complete dismissal and disbelief but give it a go - it'll only take up an hour of your time and you'll have a working web app at the end of it ;)

I think you may be right about losing control of the details of the app - ror seems to be like some kind of black magic even after seeing it but i'm going to investigate that side a bit more before I make my recommendation for the technology for the project we're working on. If speed is the only advantage that ror has - it won't be framework I recommend. I might well do another prototype in asp.net too but I think that would probably take a whole week to do and it would cost my department another .net license but it still wouldn't take as long as a php/C++ webapp!

[thinkstoomuch]

Everyone I know that's used Ruby on Rails (not very many) has raved about it. I do think that tools that used to be considered prototyping tools have in some cases matured (and processing has become so cheap!) that they can be used to produce a finished app.

Obviously J2EE has a lot more depth than ruby on rails. But if you don't need weird stuff, that's not an advantage. Ruby probably doesn't scale brilliantly, but again, probably does okay from what I've heard. Ruby is more computationally expensive, which isn't likely to be a problem unless you have a very serious app in mind. And you can offset the increased server cost out of hours of your salary saved.

Mind you, it could also be that RoR just has a different shaped learning curve - easy to learn to do the bottom end stuff quick (which if it does it well may still be a fantastic advantage).

Bah, I'm going to have to have a look at it at some point now :P

And yes, it means you can have the day off!