dmbass

The sentiment is that goods should be produced sustainably instead of unsustainably or not at all. Obviously consumers gonna consume whatever is available to them (that's why they are called consumers).

puppeteer only supports Chorme so you will need to use Slimer if you wish to use Firefox.

Allows the stock owners liquidate in public market

I don't see how you can be against subscription pricing for living software. You're paying the publisher/developers to continue developing and supporting the software and run associated services. It's the only sustainable model for long lived software and 1Password is good enough to be worth it.

A negative review from him would probably be pretty damning and deter lots of techies who are stilly trying to buy the phone.

Taking it back for the people.

Didi already has a non-compete pact with Uber (they acquired Uber's Chinese arm from Uber).

from the article:

> Our code is completely open, but piping to bash can be dangerous. For a safer install, review the code and then run the installer locally.

I think a lot of the "complexity" of web development comes from the fact that most of us are just YOLOing to get something that "mostly works" out the door. For the most part, lives don't depend on our systems and the standard for performance is much lower than something like a video game or operating system thanks to the legacy of dialup and ads.

Babel and webpack are megaoverkill for this and account for a good chunk of the 2k gzipped size. The actual library code is barely 140SLOC. There's a lot of room for improvement if this is intended to be a real standalone library (vs. a webpack/babel test).

I've thought about doing the list of smaller lists but it could cause issues with the DOM (if you care about it) since components must return a single element. Will look into that fixed data table.

The biggest performance issue I've encountered is with long lists. The most basic implementation means you will have to instantiate a new component for every item in the list even if only one of them has changed. I haven't spent that much time looking into it, so the bottleneck might be function binding (I hadn't thought of that before) but if anybody has an approach to this any ideas are appreciated. Maybe only pass an id as a prop and grab the rest from context?

How do we know they're not using techniques like this?