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).
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.
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?
Based on the post, I would guess not very much. It mostly sounded like they were unable to get people to pay for their service, not that they had problems fulfilling the orders they did receive and at their scale (23 orders on Valentines Day), I doubt a super sophisticated pricing algorithm would have helped.
This would maybe be a "100% tech company" operating at the scale of say Amazon. Over-engineering the technology would have been a huge waste of time and resources.
The title makes a dubious connection between their valuation and their technology. I guess that Secret investors are not interested in the technology but rather the network of users.
Not in the beginning. There used to be a site that measured the time between when a story got to the homepage of slashdot vs. Digg. It was a tossup for a while but eventually Digg started winning out which is when I stopped reading slashdot. Then when Digg started to get inundated with non-tech related stuff, I switched to reddit which was mostly tech focused at the time (see [1]) and once that started to get filled with politics and other garbage, I finally found and switched to HN.
Also interesting to include Digg and reddit. If you extend the date to 2014, turn reddit off because you won't be able to see anything other than green, up, and to the right.
One of the worst embedded bugs I ever had the displeasure of looking into was on a data streaming device developed by a contractor. One of the I/O processes would lockup after something like 6 or 7 days of continuously running without error. My boss and I (the only programmers) scoured the codebase for any possible condition that looked like it might maybe somehow could cause a lockup and added debugging outputs. We ran multiple devices in parallel in an attempt to increase the likely hood of the bug occurring.
The weeks kept rolling by without progress and there was more and more pressure to ship the thing. We ended up writing code that would detect the lockup and perform a soft reset. Luckily there were only a few instances where resetting would cause a perceivable problem but it still hurts to know that you shipped incorrect software.