On 15 Mar 2006, at 18:20, Michael E. wrote:
In all it took probably 4 weeks to port both the user site and the
CMS back office application to Rails and it was all done with
smiles on our faces.
That made me remember something. A year ago I was getting so
miserable of coding, so fed up with IT, finding it so frustrating to
write anything in a reasonable timeframe, I considered quitting the
gig completely and going to study law.
Then I found Rails. Now I have my own company. And I smile every time
I open the laptop…
The fact that development has suddenly become fun again is probably
2/3rds down to Matz for making Ruby pleasurable, and 1/3rd DHH for
making it useable in a real-World environment in an easy and friendly
I know we all sound like fan-boys, but that smile on our face we all
have - it’s more priceless than all the Java development in the World.
By the end of the port we had significantly improved the
application while at the same time dropping roughly 15,000 lines of
code from the system which lowered the complexity of our
That’s one hell of an improvement. I was surprised myself the other
day when I was able to write an app that I’d guessed at 4,000+ lines
of PHP got implemented in about 600 lines plus user/login_engine.
At the end of the day, the risk that we took has paid off in
spades. My team is happy at work every day and we are pumping out
more code and features then I ever could have imagined was possible
with such a small team.
Cool, isn’t it? When you can wake up one morning, think of a new
feature your customers would like, and have it implemented and tested
by lunch, signed off by 2pm and deployed before hitting the bar for
post-work drinks. Who can’t love that?
Coding at the speed of thought. That’s what you have to love.
I think a lot of people worry about performance as did I. Until
we launched I was nervous about how this was going to scale but now
I feel like it’s going to scale very well and easily. As has been
said, the LAMP issue has been solved and with the application of a
memcached our site was hit with Siege with 50 simultaneous requests
and was delivering the hugely database centric pages in under 1
second all from one server. But under a more realistic heavy load
situation of 5 simultaneuous users
we are seeing 200-300 ms response times.
I keep on eyeing what is going on with all the work around ruby2c and
so on - I reckon within a year we might hit a point where we can
develop in Ruby and easily deploy as compiled native binaries that
run ridiculously quick. There’s going to be some big performance
improvements over the next year or two, so you might be able to get
that response time reduced considerably whilst handling much bigger
loads in the not-too-distant future.
Thanks again to this great community for making development fun