Respectfully, you're missing the point. It is often the best (and only, in my mind) choice, and it is always sad. It's not the word or even the concept that's the problem. Using it in a post about euthanasia is fine; using it as callous euphemism for shutting down your business is pretty terrible.
Definitely agree. I just had to euthanize my beloved dog two days ago and reading that truly hurt. Between that and several aspects of the post other commenters have already pointed out, it doesn't seem like these people had a very good understanding of pet owners or pet ownership.
Agreed, I'm more confused than ever. I've been really sad to watch Voice die, and begrudgingly migrated towards Hangouts. Now I don't know what app I'm supposed to be using. Do I opt-out of having SMS go to Hangouts now? This is ridiculous.
Agreed. 2.6 is was EOLed over 2 years ago and is consequently already missing significant security patches (e.g. CVE-2014-1912). I think it's unnecessary and maybe even unwise to support it, especially for a security-critical application.
I've been using this for several months and it's now an indispensable tool for me. Maybe I just never learned enough Curl options, but I find HTTPie to be so much easier and more intuitive. Paired with jq, it makes my life much easier on a daily basis.
I agree. I really winced at that bizarre syntax. I find it strange to read and painfully unintuitive to write. It's not just "un-Pythonic"; it's unlike almost any other library.
I would also imagine the strange structure and all those nested accessors makes debugging and developing for the library itself unnecessarily complicated, thereby impeding contributions to the project itself.
I've been using this for the past month or so, and overall I think it's the best app for Muni. The interface is not anywhere near as slick as the Google Maps app for example, but for transit routing it feels much more functional.
