_ar7

Really cool that this is built completely from scratch. I expected a dependency on something like d3 at least.

This is why electron is so popular

My question would be what's the alternative? Cross platform native apps rarely look as good, and would require entirely new code bases and different sets of developers. Sure electron sucks for users, but what's the business incentive to ship native apps other than to satisfy the minority of users who are even aware electron saps so many resources?

I think that for whomever is developing using electron in most cases the desktop versions of the apps wouldn't even exist if electron wasn't a thing. Also, just as a side note, electron apps are so _easy_ to develop. I don't know if any other platforms that target desktop are as simple, but I might just be out of the loop.

facebook

So if we were to have a rational debate, what points did he have, and points did his opponents have?

Although it wouldn't work if you were using objects and wanted to do a deep comparison e.g.

    [...new Set([{x: 1}, {x: 1}])]

If you wanted to do O(n) functionally, you could do

    [1, 1, 2, 3, 4].filter(
      (obj => x => {
        if (obj[x]) {
          return false;
        }
        obj[x] = true;
        return true;
      })({}),
    );

What's happening is that you're passing an object (hashmap / hashset) into a function that returns a filtering function, and that object is used inside the closure to track the dupes. It's still a pure function because even though you're mutating the passed in object, the filtering function is still deterministic and referentially transparent.

Yeah you're reading it wrong. This is for node so it'd never be client side, and I'm sure the pw examples are in plaintext just for simplicity in the README.

All those machines are owned by Google or Apple though. They're not completely random machines.

Really liked the blog post. Elixir and the capabilities of the BEAM VM seems really awesome, but I can't really find an excuse to really use them in my day to day anywhere.

Lol now I feel bad for perhaps coming off a bit too harsh. I appreciate you taking my feedback into consideration. Best of luck with your company!

* Why do I have to download an 8MB payload on load, most of which consists of 1MB+ PNGs, which aren't even visible until I scroll?

* Why are you doing some unintuitive scroll-jacking?

* Why are you using React for literally a single scrollable page?

* Why are you putting the scroll position into the URL instead of somewhere like local storage? It's annoying that I can't even leave the page without pressing back multiple times.

ugh

Operator mono I think. It costs a lot.