This is the way we should be talking about privacy. Using vivid examples that are relevant to everyday people’s lives on both sides of the political divide. Avoiding broad, philosophical-sounding proclamations.
I agree, the substance was there, but the story could use some editing and organization. If it were me, it'd look something like:
1) How people think URLs work, the good parts that people see every day
2) Abstract problems with URLs, followed by concrete examples, maybe links to prominent related bugs
3) Suggested fixes for the problems, including what browers are doing at a UX level
4) Honest look at tradeoffs involved for end users
5) Remaining complications and unanswered questions
I'm not yet convinced that it's just syntactic sugar. For example, what (generic) code is `super` syntactic sugar for?
Even if it is just syntactic sugar, that syntactic sugar makes it much more approachable for devs who want to use classical inheritance (not that I'd encourage that).
Thanks for the response. If the choice is between manually specifying that (type of) code for every kind of object (and likely moving to a #create factory method) or using a native syntax for class declaration, I can see why people would choose the latter.
IMO for web apps that you have open all the time (maybe Asana, Google Docs), native OS navigation and window management is significantly better than tab navigation. Of course it doesn't have as much of a benefit if you do it for every tab you have open.
True, a paid service is probably more likely to be around in a few years (in general), but does that matter for distributed source control?
I guess if you depend on non-git features, like issues, there's a chance that there's some lock-in. However, most of the ones I use have a migration strategy [0].
