geuszb

Golang, as a garbage-collected execution environment, suffers from lousy tail latency

My theory on this is that it is easier for designers to empathize with users who are the same age or younger, since in these situations they've had the experience of the user's age, whereas very few designers have had the experience of being old (save for the author of TFA).

It's kind of funny to point out issues with SQL's composability, and in the same breath spec out a language in which "a set (including an empty one) cannot be an element of another set".

There are many real life problems with SQL but this doesn't feel like it's resolving any of them.

This was 2007. Is this used in production these days? If not, what else is used instead?

That strategy is dumb because in practice people don't mind or prefer using distinct apps for each of their subnetworks; and when these networks start overlapping in the same app, they start posting less (Facebook's problem), creating multiple accounts ("finstas" on Instagram), or bifurcating their real friends to another app (Snapchat 3 years ago).

Hell the fact that Snapchat succeeded in growing a credible threat to Facebook with a fraction of the engineering and marketing resources as Google+ should tell you how wrong that strategy was...

Each of the networks grew initially by providing an insanely better experience specific to a subnetwork (FB for alumni networks, Insta for narcissistic hobby photographers with its filters, Snapchat for horny teens who want to send nude pics, or who want to be goofy with its funny face filters...)

There were a few niches where Google+ unintentionally ended up being successful, such as internal to enterprise, and for pro photographers who liked that pictures had an option to be hosted uncompressed. But the vision overall had poor market fit and would never have latched on to a dense enough subnetwork to succeed IMO.

This gives me an idea... Even in fullscreen, I believe hovering the mouse near the top of the screen will also bring back some controls into view, but temporarily... So there's already some kind of "peek mode" for the controls... Entering this mode while typing a password in a standard password input field might make sense!

Thanks. This is a great reference indeed!

The challenge is preserving ability for content to control all pixels; without it, the content ecosystem ends up developing single-purpose, generally crappy apps, which isn't necessarily a better thing either...

I'm not sure it is the only solution either - what about "secure attention key" type ways to get the system's attention (in this case the browser's), bypassing any content interception? For example, what if there was a key combo guaranteed to always bring in the browser UI, and typing that key combo was necessary before inputting any password field?

Alternatively, the reliance on browser password management could provide some security if it can be trusted to always work...

Hmm not if your users are trained to press Ctrl-Alt-Del again... The login screen would also allow them to order the OS to log off the current session too.

An API usually embeds significant design decisions that are hard work to come up with. That said, there is some precedent for companies reimplementing competitors' API verbatim in order to get customers to port their applications more easily...

In large companies, there's another factor to consider, which is that if you're a few years into the company, the stock grants that you received a few years back and that are still vesting now are now possibly worth a lot more... your total yearly comp increases quite a bit if your company stock did well for the few years you've been with them.

You can negotiate for a reasonable increase but if an offer comes in at half of what you're making, negotiation is a waste of time for both parties.

Education is no doubt one of the problems underlying credulity but it is not the only one. I have seen very well-educated people repeatedly fall for misinformation on social networks that played to their preconceptions.

> Protected from prying eyes

Yes but only by law, which allows exceptions, notably law enforcement, national security, etc.

And I wasn't saying this causes fake news, but it does pose a moderation challenge when done at scale

> What exactly is it about the platform that makes it so "evil"?

Off the top of my head I'd personally nominate

Ads on WhatsApp Password breaches affecting both fb and ig Forced homogenization of the product offering via Stories Sleaziness around graph growth An upcoming boondoggle of an integration between Fb Ig and WhatsApp identity systems supposedly to align them on strong privacy via end to end encryption And personally I'd add the pursuit of end to end encryption at scale, which sounds like it'll lead to a disaster of moderation. (Ie don't count me in as the supporter of e2ee in the first place.)

> Do we really think we can stem "fake news" by expecting Facebook to bear the responsibility for everything that is communicated on their platform(s)?

I am not sure what the alternative you propose is. Dig your head deeper into sand?

> are we truly confident that hamstringing Facebook with a "break-up" is really going to lead to a better future? Do I really want my kids to be using TikTok/WeChat/Telegram or some other foreign controlled platform over which my government has much less oversight

I am not sure which is your government but it would probably have some power as long as we're talking about commercial operations, which tend to have some substantial presence in the jurisdictions where they're operating at scale. Or, even just blocking...

Ad-nominem!