grabastic

"what does it really mean?"

It means he's a node troll. They take a shot at the dominant frameworks any chance they can get. Node trolls have reached the level of obnoxious arrogance that early Rails developers were once mocked for. Don't feed the trolls.

I'm not sure if you're joking. Github is Git as a service... it's not in the business of software best practices.

Are you suggesting that Github starts tracking all major frameworks, all versions of said frameworks, and the files that should maybe not be version controlled within each of those frameworks/versions?

I'd imagine it's because people who aren't satisfied with Less are using/contributing to Sass instead... and vice versa. ;)

There are also big differences in design philosophy. I love the if/else, while, and for options that Sass provides, but Less has chosen to forgo that for (imo) a clunkier syntax. Things like that are unlikely to change.

A simple example...

    // Less
    .rounded-corners (@radius: 5px) {
        -webkit-border-radius: @radius;
        -moz-border-radius: @radius;
        -ms-border-radius: @radius;
        -o-border-radius: @radius;
        border-radius: @radius;
    }

    // Sass + Compass
    .rounded-corners {
        // All vendor prefixes are generated for you
        @include border-radius(5px); 
    }

I'm sure there are plugins for Less that can accomplish the same. I just grabbed this code from the Less homepage.

Another thing... Sass has much nicer control flow (if/else, while, for) that can create very powerful mixins.

Also, these aren't particularly good examples of ack vs grep... as others have pointed out.

I'd say start with ack for its ease of use, but knowing grep is important. I prefer ack but most of the boxes i work on don't have ack installed (and won't).

This is not just a sad kid and this is not just about pants. Did you ever grab a knife and threaten to kill your mom in front of your 7 and 9 year old siblings?

What is not clear about "black or khaki pants only"?

I'm quite surprised that you've chosen to identify with the petulant, knife-wielding child in this article.

Sure feels like you're bringing some personal baggage to the equation... this article is too short on details to draw the conclusions that you have.

Google has over 15,000 patents from their acquisition of Motorola mobile.

I doubt that the CoffeeScript-haters would accept any compile-to-js language. Maybe it's language stockholm syndrome. ;)

But for me, JavaScript's shortcomings are far worse than CoffeeScript's.

I always prefer text as well. I can get the information quicker and if I'm looking for a particular piece of information I don't have to scrub through a whole screencast.

I don't see why the author needs to add a "what is D3" section to a tutorial. A visitor to a tutorial site for library_x is pretty likely to know what the purpose of library_x is.

I think he's targeting his audience well. I'd imagine most of his users arrive like this...

  1) I need a data visualization library.
  2) D3 seems to be a good one.
  3) Read the D3 docs at the project's homepage.
  4) I still need help learning D3.
  5) Google for tutorials.
  6) End up at this person's tutorial.

"What is D3" would make sense if users did this in reverse (like I'm sure some people clicking on this news item have done), but I don't think that's the normal use case and I don't blame the author for not addressing it.