digitaLandscape

You breed them. It reminded me of horse breeding games my girlfriend used to play. Kind of fun. Not worth the ongoing cost though.

W3W is one of the stupidest proposals I've ever seen, because it's proprietary. We want everybody on earth to need to pay licensing fees and contact a remote API to resolve address?

To call it mad would be far too kind. I may call it evil.

Is there a non-Google alternative for those of us who don’t want our builds spied on?

This means less than nothing.

There was a lot of uproar about this internally but nothing changed. They told us that this was the only "practical" option.

The company has rotted.

Nope. Keybase supports GPG keys, but they haven't been used or generated by default for three years: https://keybase.io/blog/keybase-new-key-model

There's no real reason to use GPG. Make an arbitrary scheme on top of something like NaCl and you'll probably be safer.

Java is encumbered and rotten. Nobody should be using it by choice.

This is clearly not the case: the C64 could respond to input faster than the a few-year-old iPhone.

Amazon has been shipping counterfeit products when you buy "directly" from them for more than five years, now.

They don't care at all. The market is failing to punish them. We need a government to step in and fuck them up.

The `WorkerGlobalScope` interface extends the `WindowTimers` interface, so you can still use `setTimeout` or `setInterval` in your workers.

Just use arrow functions for your callbacks!

This is trivial. Don't create a problem that doesn't exist.

This would have been a good post in 2014 but it shouldn't be relevant to any JavaScript developers in 2018.

Arrow functions don't have `this`, and `...` syntax is simpler and as efficient as using `apply`. You only still need to use `function(){}` for generators and custom constructors, which are rare.

You have things backwards. Python has threading, JavaScript does not. Potential breaks in execution are limited and explicit in JavaScript but almost ubiquitous in Python.

I do and the only time you'll get a straight word from leadership is when Sergey appears on stage drunk (which is often. dude has a problem). The rest are consistently awful.

No.

Wasn't the entire point of this location privacy redesign Google did a few years ago that they wanted to have a single master switch, for internal and consumer clarity?

Because that's the line they sold us inside the company when we complained that it was now asking for broad permissions too often. "It's broad, but it's all controlled in one place now."

If they're now claiming that users are confused and that's not what it means, well, fuck Google management. They don't give a damn. They'll lie to their employees, and they'll lie to their users.

It's stable and mature?

If you've been writing JavaScript your whole career you might not know what that looks like.

Cool. Thanks.

It has types... which are rarely at runtime, when you typically just use an unchecked bag of key-value pairs.

It's closer to getting a bag of bytes in assembly than it is to the behaviour you'd get in any actually-typed language.

Nobody should be using such crap in 2018.

Is this actually capturing any properties of the original set, or is this a set of operations that will make any input look similar? (i.e. is this just a pretty picture with no real connection to the math.)

He cares, because he wasn't trying to be political.

You could try being literate.

Google Closure Compiler doesn't get any use because Google has entirely neglected it for a decade. They could have been where TypeScript is today, but instead they entirely ignored external users, hardly staffed the project, and now have an inconsistent mess with a non-coherent super-buggy type system and no users. It's a disaster, and if you try to do anything non-trivial it will fall to dust.

Good riddance to that abandoned pile of rubbish, and fuck Google management for letting it get so bad. They had a five-year lead on the rest of the industry in serious JavaScript development, and now they're ten years behind.

Meh. The logic still applies: on a bad network, the first request can hang for half a minute when a retry would get lucky and go through immediately.

Don't handcuff your users for no benefit, just because you can't write a well-behaved backend.

I don't like this because in practice sites usually fail to re-enable the submit button if something goes wrong. Just let the user submit multiple requests if they want to retry, don't take that away from them, just make it harmless.

> As a result, Mastodon users basically never boost toots to say how wrong they are, and there isn't an issue with armies of followers descending on the original author.

Because Mastodon is full of like-thinking people, and the ones they'd strongly disagree with aren't joining.

This isn't a bad thing (it's the "local" point this post makes), but it's important to emphasize this as the primary factor responsible for people being nicer, above any design decisions the author is complimenting. Keeping people civil is easy when there are ten thousand times fewer and they all voted socialist.

I checked the mastodon.social local timeline and fewer than 1% of posts were tagged, so I don't see how that's going to make a big difference to my experience.

> Twitter is a public company, funded by investor money; they thus owe a legal duty to make as much money for their investors as they can.

False. This isn't a legal obligation, it's what the investors want because they're toxic scum.

This kind-of comment would have been clever in elementary school.

Here, you're just being a dick.

If by "also tends" you mean "once, as a bug", then yes.

https://news.ycombinator.com/item?id=9724409

That's a disingenuous phrasing, though.