ddagradi

"she" (or "they" if you're not certain) - the author is a woman.

> Because you don't have a response other than to cherry pick sentences that sound bad out of context? Go right ahead, buddy.

You have a context that makes domestic violence acceptable? I sure didn't see it in your parent comment.

"Ask first" works just fine when the question is "can I stick my hand down your pants?". It really isn't the social norm to do that without asking.

According to the post, she was punished by the law for that (DUI). What else are you asking for?

GitHub is not a company involved in the business of midwifing. They are a company involved in the business of software development.

Is it not possible that the cultural imbalance in all of these fields is due to sexism?

[reposting stolt45's comment that got killed]:

Hey Ricky, we've definitely had some billing related issues recently. We've just finished the initial stages of moving onto a new system which should help clear up the cause of the issues like the one you mention in your last post. Sorry about the delays. If you email me at chris [at] heroku [dot] com and I'll make sure you're taken care of.

re: DNS CNAMEs, thanks for the feedback! I've updated the relevant section:

> This ensures that in the event of an infrastructure-level issue, core components can be replaced without requiring you to make changes to your apps.

You are right, it's not about protecting the platform from an app being DDOSed - that example was far too specific. It's about ensuring that an app is configured take full advantage of the flexibility and redundancy that our infrastructure is designed to provide.

Apps with > 1 web dyno are not idled. Please do open a support request if you think your app is being idled incorrectly.

You're right. It will be supported indefinitely through the gem - so neither officially deprecated or going away.

However, since .sass is no longer the primary syntax (nor default for Rails), and it's not supported by any new development efforts, it's safe to say that it is not the favored child.

Too late to edit anyways, but we're both right on this one. SCSS is a Sass syntax. ".scss" and ".sass" are both Sass files. Their docs tend to name the languages in titlecase, and the formats in all caps. That surely won't confuse anyone!

That syntax has been essentially deprecated for a while now. I think one of the most important aspects of SASS syntax is that any valid CSS3 file is a valid SASS file and compiles without error.

This can't be true of the indented-syntax, which has two downsides:

* It's a huge barrier to entry for anyone new to the framework when they already know CSS.

* It makes porting and/or incorporating existing CSS unnecessarily complex.

(The same things could be said about HAML, but people generally have no problem writing HTML, while CSS is still a fluid and ever-changing system).

The indented-syntax is way nicer to look at, but it's a good thing that it's heading off into the sunset.

"The horse-and-buggy has been working perfectly for the last hundred years, why rebuild it from scratch?"

Nothing is beyond disruption. Just because a technology is sufficiently functional doesn't mean there's no benefit to rethinking it.

It's not "5 lines", and it's not about "junior programmers". My designers need to work with my Rails apps, and learning the intricacies of setting up a Rails stack is not their job description. Just like maintaining their dev environment isn't mine. There's a bigger issue here than "those kids will never learn things the hard way".