jasallen

slightly off topic, but my favorite example of the difference is that botanically, a green bean is a fruit.

The difference is between retailer and marketplace. Both Amazon and Costco are retailers, and both could use that knowledge to decide what products to self-source for better retail margins. Either way, still a retailer, but maybe also a manufacturer / wholesaler.

But Amazon is also a marketplace. In that role it acts as a "rentable retail space". Using the data of the retailers in your marketplace to decide what to make/wholesale and then retail is another layer.

You could easily argue that it reduces to the same thing. But societally we've excepted that the retailer is a full layer in the system and gets full access to the data flowing through it. The marketplace itself is historically more of a fee-for-use type of thing, so its not an ingrained concept for us.

It's actually a far superior mouthfeel! The eggwhite foam can have a texture that's hard to describe...dry? coarse? But the aquafaba is smooth (and no, no chickpea taste even though I was pretty worried about that the first time I tried).

If you're trying to add a little more seasoning you will need to bake. You'd do this after a rough cleaning or cooking something watery or acidic. If you're just protecting it from ambient moisture just a teensy coat.

I'd say this is a difference of scale. Hinton's comments are meant to inspire and encourage _The Next Great Thing_. We could read the paper that broadly, but they seem to be addressing a more immediate local minima.

> Has there ever been a bigger missed opportunity in business than Docker managed to preside over?

Sun Microsystems

Not even close. But ugh, it is sort of getting there as far as what inflated titles are being offered/used. Going to be as watered down as today's "DBA" vs 20 years ago "DBA" at this rate.

MSFT at $805B ;-) (disclosure, my employer, etc)

"negative latency". That's a Jobs worthy dodge right there.

Yes, this is silly. And while they address it, and admit that using that field alone basically results in perfect classification, they don't do the logical thing and give this whole exercise up as pointless. Instead they just break the Account Create Time up into individual features: "Account Creation Hour", "Account Creation Minute". Seriously?

The reality is, the inclusion of that field in the metadata means that identifying a user from metadata is trivial and no interesting case for ML. In order to publish, they "degraded" the data until it was just interesting enough to be headline worthy. Insulting.

In fact your whole post misses the grandparent post's point. Their point was that they _absolutely intend to do_ what you just said. However, very little of what we do as humans in conscious decisions. Most of it is autonomic pattern response.

Forgetting disabilities for a moment: if you are not used to being around _children_ then the first time you are surrounded by them you'll act completely weird. Because they are different than you're usual pattern. With sufficient exposure you adapt, you integrate that slight variation into the pattern and all is well. For some patterns you act differently (you act different for children than adults) for some you won't act differently (for most disabled children you act the same as for other children) but in all cases exposure is the key because we humans are imperfect pattern recognition machines.

Also though, some people are just assholes. I mean don't baby talk to anyone ever.

"Ubdoubtably"... because... Well because by definition we don't doubt articles of faith right?

I find it weird that you consider it a workaround to put a Password Entry field inside a cell rather than using a "PasswordEntryCell", that's just simply nesting a control, in what platform don't we have have to do that? Might this platform or that one _have_ "passwordEntryCell" sure, but I fail to understand why such would be a first class citizen in your mind.

I also can't imagine jumping ship to React Native. If you're going to jump off Xamarin Forms and already like f# / .net then native Xamarin.IOS and Xamarin.Android are more easy, powerful and expressive than React Native.

My wife and I are currently back to using _none_ of these services for much the same reasons as everyone else (prep time, dirty dishes, small portion sizes) but I will say Blue Apron is by far the best of the lot. Their instructions made the most sense, didn't require us to scale them ourselves, the food tasted wonderful, and I learned new techniques. The rest of the services have a lot of catching up to do, so if even Blue Apron is in trouble, maybe this model isn't so sustainable at all.

That's true, but it's done so that you can have simple 'if' logic to determine if something is available without having to recompile. If the interfaces were missing altogether the libraries wouldn't be portable from one implementation to another.