Went Off The Rails: Why I'm Rebuilding Archaeopteryx In CoffeeScript
gilesbowkett.blogspot.in
Went Off The Rails: Why I'm Rebuilding Archaeopteryx In CoffeeScript
1–10 of 143 posts
Re: Went Off The Rails: Why I'm Rebuilding Archaeopteryx In CoffeeScript
#2I have faith the community is self critical enough to identify these problems and fix them. Posts like this are needed though to give us all a kick in the ass and make things better.
Re: Went Off The Rails: Why I'm Rebuilding Archaeopteryx In CoffeeScript
#3I'm not ready to ditch rails yet, but I think the framework (and Ruby itself) needs an intervention. Bundler, Ruby 1.9.2, 1.9.3, and a ton of gems are all making life harder than it used to be. I have faith the community is self critical enough to identify these problems and fix them. Posts like this are needed though to give us all a kick in the ass and make things better.
Re: Went Off The Rails: Why I'm Rebuilding Archaeopteryx In CoffeeScript
#4I'm not ready to ditch rails yet, but I think the framework (and Ruby itself) needs an intervention. Bundler, Ruby 1.9.2, 1.9.3, and a ton of gems are all making life harder than it used to be. I have faith the community is self critical enough to identify these problems and fix them. Posts like this are needed though to give us all a kick in the ass and make things better.
Re: Went Off The Rails: Why I'm Rebuilding Archaeopteryx In CoffeeScript
#5The Rails learning curve is now very steep for new users and the accusation that it has become all it set out to solve is a fair one.
For me it's a mature/stable framework and ripe for using commercially now, but I can understand the new kids gravitating to something more disruptive.
Re: Went Off The Rails: Why I'm Rebuilding Archaeopteryx In CoffeeScript
#6Re: Went Off The Rails: Why I'm Rebuilding Archaeopteryx In CoffeeScript
#7I'm not ready to ditch rails yet, but I think the framework (and Ruby itself) needs an intervention. Bundler, Ruby 1.9.2, 1.9.3, and a ton of gems are all making life harder than it used to be. I have faith the community is self critical enough to identify these problems and fix them. Posts like this are needed though to give us all a kick in the ass and make things better.
The maintainers are highly opinionated and have shown very little concern about the bloat up to now - mitigating it by targeted optimisations not by removal of bloat itself.
The community will just move on to something less bloaty - many Rails developers I know spend more (side project) time with JS now.
Re: Went Off The Rails: Why I'm Rebuilding Archaeopteryx In CoffeeScript
#8Re: Went Off The Rails: Why I'm Rebuilding Archaeopteryx In CoffeeScript
#9You can't compare a web framework with an event reactor.
Re: Went Off The Rails: Why I'm Rebuilding Archaeopteryx In CoffeeScript
#10I'm not ready to ditch rails yet, but I think the framework (and Ruby itself) needs an intervention. Bundler, Ruby 1.9.2, 1.9.3, and a ton of gems are all making life harder than it used to be. I have faith the community is self critical enough to identify these problems and fix them. Posts like this are needed though to give us all a kick in the ass and make things better.
How are things harder with these technologies?
Ruby Debug is impossible to get working in 1.9.3. The maintainer of ruby-debug has gone AWOL so we're forced to deal with solutions like this http://blog.wyeworks.com/2011/11/1/ruby-1-9-3-and-ruby-debug that don't work within bundler or a team environment.
1.9.2 + Rails 3.x is attrociously slow (30+sec). With falcon (a very unstable ruby hack) the startup speed goes to 10seconds. But 10sec is still way too slow
Sorry, it sounds bad when I just rant. In the grand of scheme of things, Rails makes me more productive as a web dev than I ever thought possible. It's just easy to pull out the daily frustrations and complain. I've been trying to help fix these issues but they are so dependent on a web of gem authors, and core ruby fixes that it takes an extraordinary amount of time.
I'm almost to the point where I think things need to be fixed top down. Matz needs to take control and try to make stuff not suck as soon as possible. Since he's working for Heroku now, it's in his best interest to push the platform and keep new users engaged.