grabastic

ha! It does. Thanks.

Thanks for posting the email.

I'm a Chicago Public Radio member, too, but I didn't get an email. I'd certainly like to be on this list... checking spam folders now...

I think everyone has given him the benefit of the doubt, but this particular thread could have been much shorter if tptacek had just explicitly stated, "It's important and I won't help attackers by elaborating on the details." If that's not made clear then it's only natural for someone to ask for the specifics.

Just a nitpick... but is there a particular link in these results that you want us to view?

There's probably ample evidence to support your claim, but linking to search results doesn't seem all that helpful. (If Google is still personalizing web searches or if someone has blocked a domain from their results we could be looking at different lists.)

Not bad. You won me over. :)

"Hey customer, someone hacked your page thanks to a vulnerability in my service, but don't worry... I've added him as a contributor to my project and sent him a thank you email."

Like that?

I read more negativity into your comment than I should have. Apologies.

So if you had a vulnerable product and this gentleman altered one of your customer's pages without permission you would be grateful? That is strange to me.

His behavior should not be rewarded.

I am also a paying customer, but I don't feel entitled to a thorough explanation anywhere but through their own official channels... even if one of their employees has chosen to comment here.

Sure... Ryan is being snarky on Twitter. :)

Fair points.

Given what you've described I'd suggest you take just one more friendly unbiased look at Rails 3... and if after that it's still not your cup of tea then fair is fair. Maybe you won't choose to develop with it, but maybe you also won't choose bash it. It's pretty cool and I believe it was an attempt by Rails developers to address your very concerns. Most major components can now be easily swapped via Railties thanks to the decoupling efforts.

http://edgeapi.rubyonrails.org/classes/Rails/Railtie.html

How do you minify and concatenate your files in your projects? Part of a deploy/build script? Commit hooks? Manually? Do you do it at all? What about compiling Sass and CoffeeScript?

The asset pipeline is not arrogance it's convenience. If you have a better system for those tasks then you shouldn't use the pipeline, but for a lot of people the asset pipeline saves time and results in a faster, better experience for their end users.

"My favorite part about node is that it isn't opinionated. It leaves the opinion to the community modules."

Node is not opinionated because it is not a framework; it is a JavaScript environment built on V8 and some common libraries. It would be much more appropriate to compare Express* with Rails than Node with Rails.

If you want to compare Node with something you'd be more correct comparing Node and its modules with Ruby and its gems.

* Even though, from what I can see, Express has more in common with Sinatra than Rails...

I'm glad to see this make it into 4. I'd love to see it get backported to 3.

"Why are they even bothering? Really, who cares about PATCH vs. PUT?"

Lots of people care. It's about following existing standards to allow for more predictable behavior. What if people didn't care about status code 200 vs 404?

And if you don't care... what's with the rant?

it's just an echo chamber

Exactly. Many smaller businesses can't afford a lengthy legal battle even if they are likely to win.

This looks very, very promising. Great work.

I've never liked how RVM overrides shell commands.

Democratic governance of standards sounds better to me. I think this is long overdue. Best part is JSLint will still be around.