Comments on: Living In A Post Rails World http://kurt.karmalab.org/2009/02/14/living-in-a-post-rails-world/ Schrade.Blog Fri, 09 Jul 2010 06:07:11 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: elliottcable http://kurt.karmalab.org/2009/02/14/living-in-a-post-rails-world/comment-page-1/#comment-349 elliottcable Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-349 I came to Ruby a few years ago, intending to get "a firm base" in the parent language before hitting Rails, my real goal. I fell so much in love with Ruby - real, pure Ruby - that I never ended up doing anything with Rails. I'm glad of it. Rails is dead, or will be soon enough. Long live Ruby! I came to Ruby a few years ago, intending to get “a firm base” in the parent language before hitting Rails, my real goal. I fell so much in love with Ruby – real, pure Ruby – that I never ended up doing anything with Rails. I’m glad of it.

Rails is dead, or will be soon enough. Long live Ruby!

]]> By: Jerome http://kurt.karmalab.org/2009/02/14/living-in-a-post-rails-world/comment-page-1/#comment-350 Jerome Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-350 Great article, I also thought of seperating parts of my applications, like the authentication system and others. At some point I could build applications which relate very well if they use the same tiny applications/databases. @elliottcable: Rails is far from dead, come on! It's being developer for, upon and with! Great article, I also thought of seperating parts of my applications, like the authentication system and others. At some point I could build applications which relate very well if they use the same tiny applications/databases.

@elliottcable: Rails is far from dead, come on! It’s being developer for, upon and with!

]]> By: zerohalo http://kurt.karmalab.org/2009/02/14/living-in-a-post-rails-world/comment-page-1/#comment-351 zerohalo Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-351 I agree with/like the concept of small apps talking to each other rather than one big one. Easier to maintain/upgrade/reuse the individual components. But I see no reason to ditch Rails in order to achieve that. (No need to be stuck in Rails either, of course.) I agree with/like the concept of small apps talking to each other rather than one big one. Easier to maintain/upgrade/reuse the individual components. But I see no reason to ditch Rails in order to achieve that. (No need to be stuck in Rails either, of course.)

]]> By: Sean http://kurt.karmalab.org/2009/02/14/living-in-a-post-rails-world/comment-page-1/#comment-352 Sean Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-352 I'm not sure if I can wrap my head around this... can you provide an actual example of one these tiny-app systems? @elliottcable: Just because you don't use Rails doesn't mean it's dead. Get real. I’m not sure if I can wrap my head around this… can you provide an actual example of one these tiny-app systems?

@elliottcable: Just because you don’t use Rails doesn’t mean it’s dead. Get real.

]]> By: ferrisoxide@gmail.com http://kurt.karmalab.org/2009/02/14/living-in-a-post-rails-world/comment-page-1/#comment-353 ferrisoxide@gmail.com Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-353 Weirdly enough, this is the very direction Rails seems to be headed anyway. With support for Rack - via Rails Metal - the opportunities to write tiny apps that stick together is huge. Have a look here for a couple of examples of where this is headed: http://weblog.rubyonrails.org/2008/12/17/introducing-rails-metal Rails aint dead - but I think even core Rails folks realise it's the answer to every problem. Small things, loosely coupled - that's the Ruby world I want to live in. Weirdly enough, this is the very direction Rails seems to be headed anyway. With support for Rack – via Rails Metal – the opportunities to write tiny apps that stick together is huge.

Have a look here for a couple of examples of where this is headed: http://weblog.rubyonrails.org/2008/12/17/introducing-rails-metal

Rails aint dead – but I think even core Rails folks realise it’s the answer to every problem. Small things, loosely coupled – that’s the Ruby world I want to live in.

]]> By: Kurt Schrader http://kurt.karmalab.org/2009/02/14/living-in-a-post-rails-world/comment-page-1/#comment-354 Kurt Schrader Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-354 Let me clarify one thing, I don't think that Rails is dead. I think that it's very much alive and well (and Rails 3 is looking great), but at the same time the Ruby tools world has reached a level of maturity where if you're not looking at all of the other possible solutions to a problem then you're really doing yourself a disservice. Let me clarify one thing, I don’t think that Rails is dead.

I think that it’s very much alive and well (and Rails 3 is looking great), but at the same time the Ruby tools world has reached a level of maturity where if you’re not looking at all of the other possible solutions to a problem then you’re really doing yourself a disservice.

]]> By: rick http://kurt.karmalab.org/2009/02/14/living-in-a-post-rails-world/comment-page-1/#comment-355 rick Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-355 we never said rails was the answer to everything. it fills a need. I wouldn't say multiple smaller apps are necessarily easier to maintain, though. Each piece adds complexity in getting an application up and running. I'm just dabbling in this area, and I already need to startup a database, a Parkplace server (using Amazon S3 in production), Sphinx, a payment gateway (sinatra w/ json api), and an Astrotrain instance (merb server for processing emails) just to get Tender Support (all rails) running. it's not exactly trivial for me, and it's downright a pain for our designers. Luckily, these external services are optional and only needed if you're looking at that specific feature that they enable. Being able to step outside your comfort zone is a very good thing, though. we never said rails was the answer to everything. it fills a need.

I wouldn’t say multiple smaller apps are necessarily easier to maintain, though. Each piece adds complexity in getting an application up and running. I’m just dabbling in this area, and I already need to startup a database, a Parkplace server (using Amazon S3 in production), Sphinx, a payment gateway (sinatra w/ json api), and an Astrotrain instance (merb server for processing emails) just to get Tender Support (all rails) running. it’s not exactly trivial for me, and it’s downright a pain for our designers. Luckily, these external services are optional and only needed if you’re looking at that specific feature that they enable.

Being able to step outside your comfort zone is a very good thing, though.

]]> By: ferrisoxide http://kurt.karmalab.org/2009/02/14/living-in-a-post-rails-world/comment-page-1/#comment-356 ferrisoxide Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-356 That should have been "I think even core Rails folks realise it's NOT the answer to every problem." Wups.. one little word.. :) That should have been “I think even core Rails folks realise it’s NOT the answer to every problem.” Wups.. one little word.. :)

]]> By: Ade http://kurt.karmalab.org/2009/02/14/living-in-a-post-rails-world/comment-page-1/#comment-357 Ade Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-357 I'm with Sean here...can I see some actual examples of these tiny-app systems? I’m with Sean here…can I see some actual examples of these tiny-app systems?

]]> By: lolcatz http://kurt.karmalab.org/2009/02/14/living-in-a-post-rails-world/comment-page-1/#comment-358 lolcatz Wed, 30 Nov -0001 00:00:00 +0000 urn:uuid:{a.guid}#comment-358 +1 for examples, please +1 for examples, please

]]>