that's great. but why doesn't ctrl c do it? I mean it closes everything else on my system, except man pages, vim and some other programs that use less.
I would be interested in this if it weren't for the foul language. This speaks volumes about the author's attitude.
If you're annoyed with something, have they even tried bringing it up with Heroku's support team? If so, have they tried shipping this tool that doesn't make the maintainer look like an arrogant troglodite?
I never claimed I was deeply offended by swearing. I claimed it will ultimately impact the maintainer's reputation and user base. Clearly you're a narrow minded person that can't see the big picture.
Uh, this is not going to impact Tim Pope's reputation in any way whatsoever given that it is a tiny inconsequential project. He is already an open-source A-lister.
I don't see what fucking language you're talking about. Joke aside, I think this is just part of the author's humor, it has nothing to do with being arrogant.
That fucking language was quite mild. Past versions of Linux (don't know if it's still there) used to have a quote from "Heathers" in a comment: "Fuck me gently with a chainsaw", as well as non-quote swearing like "fuck me plenty" and "fuck me harder".
init/main.c:
/*
* Tell the world that we're going to be the grim
* reaper of innocent orphaned children.
*
Some software development subjects are best not discussed in front of ordinary people, but it's hard to not make fun of it when you're dealing with a daemon that's not properly reaping it's zombie children...
I have completely the opposite opinion. Clojure is not as widely used as some other languages. Python springs to mind; I know it was part of the Kickstarter pledge.
Support for compiled languages would be nice, although I realise this is difficult.
Most of our sites run entirely on S3. While we do have a cron server running, we could just as easily ship the updated JSON files from one of our laptops.
In fact, for the 2012 election, our fallback in case EC2 was unresponsive was to decamp to a coffee shop with a laptop and s3cmd.
There hasn't been an acknowledged S3 outage since April 2009 that we can find. Also, we use two different buckets in different geographic availability zones to allow us to stay up if one AZ goes out. Finally, our biggest projects are cached in CloudFront, which would serve a stale cached item if the backend were unavailable.
Do you 'invalidate' all files when pushing an update or do you use a low cache expiry value for CloudFront?
In particular, I am thinking of edge cases where a news story has a typo/other important correction and you want to update just that story. What is your strategy? How is it impacted by caching done by CloudFront? Thanks.
Yes and yes. Yes, it is possible for S3 to go down and yes uptime is very high. For their purposes, S3 uptime is much higher than they can reasonably sustain with in house hosting.
I am one of the lucky few who has insurance provided by their employer. Unfortunately, if I am in a car accident and rack up $100,000 in bills, I am bankrupt.
> Unfortunately, if I am in a car accident and rack up $100,000 in bills, I am bankrupt.
...or you just have to haggle with the hospital and refuse to pay their grossly inflated funny money prices.
I have a good friend who incurred 30K in bills for a 2 day stay related to a broken femur. He has no insurance. Since seeing his bill, which wasn't itemized at all, he's basically refusing to pay anything until he sees what he's being charged for. In response to this demand the hospital reduced his bill by about 12K, magically, and still providing no itemization.
He is still refusing to pay and only time will tell what the outcome will be. It's very clear, however, that he was grossly overcharged and that the hospital has no clue what they're really billing for. It's a game. Some people roll over, others fight.
If someone really ends up with 100K+ in medical bills after adjustments then it might actually make sense to take 7 years of 'bad credit' after a bankruptcy. No easy answers here, but it's pretty clear we're all being swindled.
The rule of thumb that I've heard (from a health cost sharing ministry [0]) is that you should expect to be able to negotiate a discount of at least 40% if you're a self-pay patient.
My sister shattered an ankle a while back, and was billed around $40,000. Between reductions, writeoffs, and charities the hospital connected her to, she ended up only paying about $5000.
Not true - they could check email and send you push notifications server-side, but still have the client talk directly to gmail for nearly all functions.
