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.

IF UWP will expand to do that it's not in any announced roadmap (and if it's being discussed internally I'm not privy to such things :) ) whereas Xamarin is doing it now(ish). You are right, the XAML is a bit different, the syntax is the same, but we use different class structures.

ECMA spec is for the CLI, essentially the specification for runtime like type system and GC and all the other things that make an environment work at all

Net Standard is a specification of APIs. So in order to be compliant to the standard you must have a class named X with parameters string Y, int Z.

"Net Framework" is the name for the Windows "full .net framework" -- this doesn't have a descriptive name since it was before all the rest, but basically its an SDK that is a superset of the Net Standard (and therefore is .Net Standard compliant / interoperable)

Mono is a open source implementation of "Net Framework" that runs on multiple platforms (linux, etc). It attempts to treat full .NET Framework's surface area as a spec but re-implement it cross platform. It is _also_ a open source CLI implementation. So in common speech "mono" like ".net" can refer to either the "basic sdk" _or_ the runtime environment.

Xamarin is forks of mono for iOS, Android and Mac platforms plus libraries that include full support for interacting with those platforms Native SDKs

Unity is a fork of Mono plus gaming tooling and runtime tools. Microsoft does not maintain this, it's a separate company.

Microsoft's Xamarin Forms 3.0 (stable release later this year) allows you to target Linux and Mac[1] and is very similar to UWP conceptually - UI written once, run anywhere. It's just that Xamarin's "anywhere" is much larger :)

Disclosure: I work on Xamarin team at Microsoft

[1]https://forums.xamarin.com/discussion/85747/xamarin-forms-fe...

I like both mcmansionhell.com AND my mcMansion. Weirdly, she calls out fake shutters that won't actually close over the windows, but my 1954 built, 1300sq ft previous house had those as well!

Seems like Uber would be a big step _down_ for Sandberg.

This is the most reddit-like comment thread I've ever seen on HN

Hey Guys, Xamarin University Instructor here,

Obviously I think it's worth it, I learned it well enough to teach others. We have a bunch of free Self Paced Learning modules and videos at Xam University, as well as obviously the paid stuff that pays my salary ;-)

There is a ton of investment and effort from a small team, remember, we've only been with a "big company" a few months, so the improvements come at a blistering start-up pace. If you haven't seen it in a couple years, you should really check back.

If you are going to develop "all platforms" or even just iOS and Android, it is _certainly_ worth a long look. Access to every API you get access to in their native languages and the ability to avoid that language "context switching" pain. Plus, some amount of shared code (varies wildly, 25% - 75% depending on how heavily your app is just about custom UI and animations ).

Because we use the same APIs (except when we have better ones), you can leverage the same documentation and StackOverflow posts when you need to (yes with a little language translation), but you often don't need to because Xamarin has a _lot_ of great documentation as well.

And, as has been mentioned, "Xamarin Forms" does not equal "Xamarin". Although it is a valid choice for developing in Xamarin, it is only one option. Here is a super shallow comparison:

Xamarin Forms: Super fast for super simple UI's and interactions with common elements. It is highly opinionated on what it should do and look like on all platforms. Customization is do-able but starts to increase the complexity of the app quickly to the point where the below would have been a better choice.

"Xamarin" aka "Xamarin.iOS and Xamarin.Android": Use essentially the same development patterns as Native Android and iOS developers and use the same API's (plus .NET library, and many .NET 3rd party libraries). You get code sharing (as noted, amount varies considerably), ability to "think in one language (often including your server, which might also be c#), and access to some additional libraries (because we support both the Native libraries _and_ the .NET ecosystem).

Hope this helps :)

Oh, and a quick plug. Xamarin University is live classes taught by real, very experienced developers who can actually help you learn and understand, so we are, you know, worth asking questions of. Also, we'll be doing a free presentation all day on November 18th as part of Visual Studio Connect, so check us out there and see what you think of Xamarin _and_ Xamarin University!

I would throw Pioneer Woman on as the second Google option. She doesn't have the geeky bent that Kenji does, but has amazing recipes.

Article is from 2013

I'm American and it drives me crazy to hear this, but it is regretfully not terribly uncommon.

oh man. I have a connective tissue disorder that messes with my joints pretty bad but I had _no idea_ this was a concern!

Wow, "fast.com" is one helluva valuable piece of DNS real estate Netflix is throwing at this.

Diets often do improve cholesterol, blood sugar and other health markers in the short term, but these gains may result from changes in behavior like exercising and eating more vegetables

um, "changed in behavior ... eating more vegetables" -aka- "diet". So in other words "fad and crash diets" don't work. But "improving your diet" does and always has.

Wow. No. Just no. This comment is so wrong, to remotely compare any of these things to smoking and drinking. And even if we stipulate (even if, since the science is poor) that these are contributing factors, nobody thinks they increase risk enough to make a dent in the statistics we're talking about here.

...said a guy in his 30's