Hacker News: digitaLandscape

New comment by digitaLandscape in "The collapse of cryptokitties, the first big blockchain game"

digitaLandscape — Thu, 15 Sep 2022 20:30:10 +0000

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

New comment by digitaLandscape in "Plus codes: addresses for everyone"

digitaLandscape — Sun, 30 Sep 2018 17:06:43 +0000

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.

New comment by digitaLandscape in "The relative performance of C and Rust"

digitaLandscape — Sat, 29 Sep 2018 13:30:06 +0000

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

New comment by digitaLandscape in "Kristinn Hrafnsson Replaces Julian Assange as WikiLeaks Editor-In-chief"

digitaLandscape — Sat, 29 Sep 2018 13:27:46 +0000

This means less than nothing.

New comment by digitaLandscape in "Google Maps won't let you save home address without allowing all Google tracking"

digitaLandscape — Wed, 26 Sep 2018 03:45:19 +0000

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.

New comment by digitaLandscape in "GnuPG can now be used to perform notarial acts in the State of Washington"

digitaLandscape — Tue, 18 Sep 2018 18:41:44 +0000

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.

New comment by digitaLandscape in "Java Is Still Free"

digitaLandscape — Mon, 17 Sep 2018 22:47:26 +0000

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

New comment by digitaLandscape in "Apple now strives to design and build products that last as long as possible"

digitaLandscape — Mon, 17 Sep 2018 12:18:41 +0000

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

New comment by digitaLandscape in "Why Amazon is eating the world (2017)"

digitaLandscape — Sat, 08 Sep 2018 14:36:40 +0000

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.

New comment by digitaLandscape in "A tour of JavaScript timers on the web"

digitaLandscape — Mon, 03 Sep 2018 20:29:20 +0000

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

New comment by digitaLandscape in "Javascript Fundamentals: ‘this’ keyword"

digitaLandscape — Sat, 25 Aug 2018 16:11:34 +0000

Just use arrow functions for your callbacks!

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

New comment by digitaLandscape in "Javascript Fundamentals: ‘this’ keyword"

digitaLandscape — Sat, 25 Aug 2018 15:28:29 +0000

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.

New comment by digitaLandscape in "Johnny-Five v1.0 – JavaScript Robotics and IoT Framework"

digitaLandscape — Fri, 24 Aug 2018 04:05:53 +0000

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.

New comment by digitaLandscape in "Google Data Collection research"

digitaLandscape — Thu, 23 Aug 2018 22:41:47 +0000

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.

New comment by digitaLandscape in "Magic Leap One Teardown"

digitaLandscape — Thu, 23 Aug 2018 16:37:27 +0000

No.

New comment by digitaLandscape in "Google Data Collection research"

digitaLandscape — Wed, 22 Aug 2018 15:59:32 +0000

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.

New comment by digitaLandscape in "PyPy.js: Python in the web browser"

digitaLandscape — Wed, 22 Aug 2018 15:41:05 +0000

It's stable and mature?

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

New comment by digitaLandscape in "A visualization of the prime factors of the first million integers"

digitaLandscape — Wed, 22 Aug 2018 15:33:31 +0000

Cool. Thanks.

New comment by digitaLandscape in "Dynamic Django Models with Model Models"

digitaLandscape — Wed, 22 Aug 2018 15:32:21 +0000

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.

New comment by digitaLandscape in "A visualization of the prime factors of the first million integers"

digitaLandscape — Wed, 22 Aug 2018 15:23:08 +0000

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.)