Engaging in unprotected sex with multiple partners while pretending otherwise with each is akin to playing Russian Roulette... with someone else's life.
Man or woman, yes, that sort of behavior deserves a beating.
Agreed, and it's way beyond the social norm to do it at all in public and in front of other people(!) :-)
I can wrap my head around someone thinking a quick kiss in an informal setting without explicit permission could be brushed off, but sticking a hand down the pants of even one's significant other in a public context is way beyond any social norm I'm aware of except perhaps at an orgy.
What are you talking about? Among the subset of the population who participates in hands-down-pants, roughly zero percent of these interactions begin with one of them asking for permission first. It simply doesn't happen.
I can assure you that my method means I do not rape people and your method means you might. And that's regardless of how many people employ my very reasonable and clear method of determining consent. Has the thought ever occurred to you that the fact that people believe ambiguous signals to be consent may actually CONTRIBUTE to the fact that 1 in 5 women experiences rape in their lifetime?
There's no mention of punishment, only arrest. I'm asking, insisting actually, she doesn't drive if she is going to do drugs. Getting sober is a better request but I cannot make her do that, she has to find a way herself.
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.
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.
That's false actually. There is a "new" syntax, but the popularity of the language is in many ways due to the terse, easy-to-read original syntax—it's not going away and it's not deprecated.
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!
