31–40 of 143 posts
require 'bundler'
Bundler.setup
This is exactly what I use in my commandline Node.JS project which is BDD tested using cucumber and aruba.
Recently, I actually started to learn the Ruby spec because I was offered a well paid work in Ruby for many months to come, and I thought it would be cool to work in something new. Besides web dev, my past is C/C++, then many years of Java, and recently Node.js. I turned the Ruby project down because very early down the spec I realized that I don't want to work with technology belonging to 5 (or at least 2) years ago…
Ah, so you don't want to work with mature, proven technologies, language design-wise, that bring benefits to the company and the user base.
Good thing that you don't WANT to work with this kind of technology, because I too don't think you SHOULD be working anywhere near client projects with that mentality.
Tldr: Giles discovers 2011.
tl/dr What I take from the post: Guy has no fun with underlying technology, rewrites from scratch with more fun framework, does not care about current users, thinks this is offset by future users who can more easily use coffeescript.
"And as for overly ceremonial code, let me tell you about my balls. I actually have a rake task to scratch my balls. Somebody told me a good entrepreneurial programmer writes code to scratch their own itch, and I took them literally. The code uses a serial port to power an Arduino board. The Arduino's got a servo with a backscratcher attached. I keep it on a shelf at scrotum height underneath my desk."
tl/dr Rails is not the new hotness anymore, the Rails 3 rewrite was a waste of time and it's strayed far from its initial ease of use. Node & Coffeescript, the new hotness, are awesome, here's my new video series, the first one's free.
And as for overly ceremonial code, let me tell you about my balls. I actually have a rake task to scratch my balls. Somebody told me a good entrepreneurial programmer writes code to scratch their own itch, and I took them literally. The code uses a serial port to power an Arduino board. The Arduino's got a servo with a backscratcher attached. I keep it on a shelf at scrotum height underneath my desk. I literally need to type bundle exec every single time I want to scratch my balls. I don't like having to type bundle exec every single time I scratch my balls. I named the task balls, so I can type rake balls, because it rakes my balls, and Bundler pisses all over my tidy syntax, but am I going to complain? Am I going to point out that asking me to type bundle exec every time I want to scratch my own balls shows incredible contempt for me as a user, particularly considering that the whole reason I'm a user of this particular thing is because I work in a language which was designed to optimize for programmer happiness? Of course not. It's not productive or helpful to say that, so I simply type bundle exec rake balls and scratch my balls in sullen silence. Typing bundle exec every single time I want to scratch my balls is the epitome of the overly ceremonial code which Rails defined itself against from 2005 to 2007.
The problem with tl/dr is that it misses out on the funny. :-(
tl/dr Rails is not the new hotness anymore, the Rails 3 rewrite was a waste of time and it's strayed far from its initial ease of use. Node & Coffeescript, the new hotness, are awesome, here's my new video series, the first one's free.
You missed the most important part: And as for overly ceremonial code, let me tell you about my balls. I actually have a rake task to scratch my balls. Somebody told me a good entrepreneurial programmer writes code to scratch their own itch, and I took them literally. The code uses a serial port to power an Arduino board. The Arduino's got a servo with a backscratcher attached. I keep it on a shelf at scrotum height…
I love Giles. His first Archaeopteryx talk was one of the best Ruby-related talks of all time. He's way too harsh on Rails though. The original "blog in 15 minutes" demos that catapulted Rails into the limelight are still possible with Rails 3. Things like 'gem install rails' still work. If you are determined to skip bundler, you can do that too. What's more, unlike 2005, in the 15 minutes it takes to build a Rails b…
I'd go further and say, that it will be very hard to have a good MVC framework with Node before the async callback mess is brought under control. Maybe we'll even need something like Iced CoffeeScript for this.
As someone who has made an MVC framework in Node.js and launched a production site using that framework, I can assure you that it's not hard to avoid async callback mess. I can also assure you that many others have had success doing this.
It's really not difficult to write beautiful, modular, and readable code in node.js without going past 80 columns and without using Iced CoffeeScript.
I suspect that comments like this only further reinstate the theory that most people are dismissing Node primarily due to the annoying amount of hype. There are better reasons to not use Node, but imo, this isn't a very strong argument.
Rails has always been bloated. That's what you get from frameworks that come with automation for common tasks. However, let me provide a counter-point ... I think that Rails 3 is finally a good framework that I want to use. Blogs written in 5 minutes (which you can still do in Rails 3) have never impressed me. What impresses me is code-reuse, modularity and readability. Which is why I preferred Django instead of Rail…
I don't know. I liked the rails 5 minutes blog demo. I wasn't into rails from the beginning - I followed the recent one http://guides.rubyonrails.org/getting_started.html
I think it's the ideal example for demonstrating a web framework.
1. It gives basic introduction to the framework and installation notes.
2. It's simple enough to follow, yet large enough to show major aspects of development with rails.
3. It shows all major aspects of the web application development - db access layers, db creation and migration, models and validation, request routing, controllers, views, partials...
> What impresses me is code-reuse, modularity and readability. Which is why I preferred Django instead of Rails 2.
I use both Django and Rails. Rails has various stuff which I need for a basic app out of the box, which Django doesn't have - asset pipelines, coffeescript integration, swappable templates, bundler for dependencies, rvm(not exactly rails) for isolating ruby version and gemset, tested gems for basic tasks(kaminari, devise, paperclip) etc.
I know I can do all of it in Django/Python(pip, virtualenv, coffee --watch, webassets etc etc), but rails sets up things for me and I can begin coding.
Rails does require more peripheral knowledge, but it's optimized for people who know rails. Beginners will be more at home with Django, but you are a beginner for a very short period of time, and optimizing for beginners while forfeiting comfort for people who are on-board isn't a good compromise IMO.
In an ideal world, we can have frameworks which is both beginner and power-user friendly, but I seldom see it happening it in the real world.
As far as reading code goes, I have trouble following Rails code, and my only friend is the interactive debugger - I set breakpoints, read code in the editor, continue, break...
I haven't read Django's code in a while, but it used to be quite heavy on magic - not sure about the current status.
tl/dr Rails is not the new hotness anymore, the Rails 3 rewrite was a waste of time and it's strayed far from its initial ease of use. Node & Coffeescript, the new hotness, are awesome, here's my new video series, the first one's free.
You missed the most important part: And as for overly ceremonial code, let me tell you about my balls. I actually have a rake task to scratch my balls. Somebody told me a good entrepreneurial programmer writes code to scratch their own itch, and I took them literally. The code uses a serial port to power an Arduino board. The Arduino's got a servo with a backscratcher attached. I keep it on a shelf at scrotum height…