edibleEnergy

> Brief correction: Cookies seem to get removed and re-created immediately. At least the cookie content and creation date seems to change. Nonetheless: After hitting the "remove all" button you still don't end up with an empty cookie jar.

[1]: https://twitter.com/ctavan/status/1044543955457773573

Comment · 8 years ago

I've used YAML for years, and yeah, there's a lot of warts, but I love it for small(ish) manually edited configuration files. I generally keep it simple and it works.

Comment · 8 years ago

The GDPR explicitly does not set out to specify implementation details because of the reasons here: https://gdpr-info.eu/recitals/no-15/ (Technology neutrality)

Comment · 8 years ago

The latter. I don't have specific examples in mind, just that if you do not trust a company's data collection policies, the collection capabilities of an installed program are much greater than when viewed through a web browser. See [1] for an example from a few of years ago.

[1]: https://gizmodo.com/facebooks-messenger-app-logs-way-more-da...

Comment · 8 years ago

Hi John, just an FYI: if you have Facebook Messenger installed on your phone, you are probably giving Facebook a lot more data than you think.

Comment · 9 years ago

Somewhat tangential to this particular issue, but this is a good lesson for developers in why you should be dry and explicit in your writing.

Sure `alert("FFFUUU WHY U NO WORK");` keeps you entertained for 5 minutes while you debug a problem but when that accidentally gets to prod...

Comment · 9 years ago

Sure, https://perldoc.perl.org/perlpolicy.html#BACKWARD-COMPATIBIL... that’s the policy for the language itself, but as it mentions there it’s considered generally a “community” virtue. I wasn’t programming back in 02 so I’m sure it was extremely different (and the source I’ve read from modules from that era is pretty frightening. Any major framework or generally used module will try to maintain backwards compatibility at least as far as documented behavior. I’ve never come across the kind of stuff I see all the time with node and go and python; package maintainers changing parameters and such because they weren’t happy with the original API.

Comment · 9 years ago

What this article arrives at is basically the perl/CPAN model. Don’t break backwards compatibility unless you absolutely have to; as in cases of security or when the original functionality never worked in the first place.

Comment · 9 years ago

Thanks for writing Ack petdance! Nowadays I typically use 'git grep' but I still use ack a good amount.