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?

It's from Google's Polymer project https://www.polymer-project.org/1.0/

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

This post is about the FT service http://polyfills.io/

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.

1 - http://www.wired.com/2014/01/the-gentrification-of-reddit-in...

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.

http://www.google.com/trends/explore#q=%2Fm%2F05zpmc6%2C%20S...

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.

I think that's the entire point of the article. The premise is that designers have been given a seat at the table because of the perception that they have some advanced insight into producing products with market fit and betting on them is more likely to produce a successful product. The author uses these three apps, a sample of design driven products, to show that lauded designers have no better insight than anybody else. Maybe they're only better at making things shiny, not creating valuable products.

This is subtly different for Linkedin. They DO show the same thing to Googlebot as logged out users. Registered users end up seeing a different page which Google bot has no way of accessing because it does not have an account.

I think this is a misrepresentation of what makes React.js valuable. React is useful for optimizing your rendering (model state -> DOM state) because you don't have to think about re-rendering sub-views of things that haven't changed. This has nothing to do with defining a communication flow for your app. You're still propagating state up and down your tree whether it is a tree of Backbone views or React components.

Rendering optimization is definitely a nice thing to not have to think about though.

That's not the endgame. Once machines pass the Turing test, it will be impossible to filter humans vs. machines.

Why is this important? What makes this different from any other open source game clone?

Indeed. HTML isn't even mentioned in the post and it also doesn't seem like they are dropping support for forecast.io, just updating the existing native iOS app to be more in line with the HTML based website.

Hmmm... I'll have to make a graph of that and see how it pans out.

Let me give an example:

Say I pay $10/month and only listen to 2 artists, each with .001% market share. IMO, each one should get $3.50 from my pool of subscription money. Using their current scheme, each would get $0.00007 while Lady GaGa would get $0.30 when I didn't even listen to Poker Face.

  2. Artist’s Spotify streams divided by total Spotify streams

  This calculates an artist’s popularity on the service, their
  “market share.” Dividing an artist’s streams by the total
  streams on Spotify determines the percentage of our total
  pay-outs that should be paid for that artist’s rights.

This sucks bigtime. Why should artists that I never listen to receive any of my monthly subscription? This portion of the calculation should be done on a per subscription basis.

The Wirecutter does pretty extensive lists of "the best" electronic products/gadgets.

Here's their networking section: http://thewirecutter.com/leaderboard/networking/