I'm sorry if this hurts your beliefs, but in what way are aggregated and anonymized data exploitative? Every "offline" store does it. How do you expect businesses to make profits if they can't look at what drives their revenue without bothering every single customer with consent requests?
Big Theta isn't "average case". It describes an algorithm with the same asymptotic lower and upper bounds. How would you even formally define an average case, when the result depends on the input?
In Czechia, for example, there's a fairly successful (in some ways even superior) Google Maps competitor in Mapy.cz. Google Maps are better in Prague and other larger cities. Mapy.cz focused on providing features Google didn't really care about, like mapping hiking and cycling trails or having nearly every backcountry road covered in their Street View alternative.
How dare you write a HN comment that doesn't complain about how <thing> used to be so great back in the day but has since been ruined by internet media, corporations, and websites that rely on javascript!
Even if that was the case, it might actually be desirable. I think you can't appreciate the uniqueness in the other cases if you haven't met the general purpose mainstream.
In the EU, you can return any goods purchased online (not sure about in-store) within 14 days without providing a reason. It's a different process from asking for a refund though the company's return policy.
We're using Swarm in production for a bunch of our small CMS projects and it's been great. "A little bit on top of Docker Compose" is a great way to describe it. It's just so easy to set up, and I think it's still a reasonable option when you want to dockerize stuff you've had running on a VPS.
TONS of people. And these companies live off of the fees for unpaid "buy now, pay later" mini-loans. Say what you want about freedoms, but it's just incredibly scummy to trick people who don't know better into signing up for something like this. If it was up to me, I'd just ban that sort of business.
Is it, though? It's not just about exposing an extra API endpoint which updates a DB row. There's definitely a lot of other business & technical design decisions to be made, such as retweets and quote tweets. "Since last year" could mean about six months, which doesn't sound that unreasonable for a pretty major feature (and one that gets a lot of press).
Every time a PHP post makes it to the HN frontpage, there's a ton of people saying how easy it is to pick up, build a project on, and deploy. I sometimes wondered "hm, maybe I was wrong about it, I might try it out". I had no idea it had skeletons like this hidden in the closet.
Damn, imagine working at a place where at the end of each day, the management goes through your shell history and includes it in a "performance review".
If you want to show the user a list of active sessions (and let them revoke one), it makes sense to try and parse the UA and show them a more readable device name.
This comment is ridiculous. You've shifted this from "too many options for everything" to "any options at all". Also, how are these things framework specific? The API vs templates argument also applies for Rails. Choosing an authentication method also applies to Rails. Choosing rendered emails via SMTP vs Sendgrid - also applies to Rails. And so on. You can't mix business requirements with "tooling choices".