Chinese push it to the extreme though (disclaimer, my wife is chinese, and her family fit exactly the description above, and they freely admit it...my wife was born here and was kind of a rebel, thus why she broke the line and ended up with a white guy).

The length they'll go to avoid all "foreigners", even when they're in the middle of big cities, big schools, etc...All big companies have a "Chinese" mailing list that a ton of them subscribe to, eat together, go out together, only deal with doctors/contractors/etc who are chinese, etc. Its crazy.

Our brains are basically designed to spot differences and handle them as special case scenarios (thus why if I have a wall full of green dots and one is red, you'll probably notice the red dot before you realize there's a wall behind it).

We're also (understandably so) relate better to things that remind us of ourselves/our families/etc.

The two put together means someone who physically looks different than what you're used to, will automatically take a pretty big hit. Black people take the brunt of it, being a lot more different visually than, let say, a white westerner and an asian.

That's not enough in itself though. Black people in countries that don't have historical background relating to them will have a lot less racism issues.

Then tack on statistical differences in certain areas (ie: a city where there's a big economic divide with a high racial correlation, usually again because of historical reasons), and you hit a society perfect storm that will take a miracle (or just a lot of time....) to overcome.

That will heavily depend on how you do it. If you have a 1 to N, and insert the object trees one by one, you're going to get a crazy amount of back and forth. The amount of queries will be the same, and similar to the ones you do manually, so there won't be any meaningful differences there.

The main difference is that you're likely to do "Insert 1 in master, 5 in detail, 1 in master, 5 in detail", batching them in groups of 1 and N, when the correct way is to insert all the rows in master, then all the rows in details (batching in smaller groups if transaction size is a problem).

EF can handle that scenario just fine. Its just not that clean.

That's just understanding how an ORM work, and all ORMs have these issues. You get used to working around them. (You'd have a seizure seeing what Rails Active Record does, yet people use it in petabyte scenarios.)

What's readable or not is relative to the context of the reader.

A lot of the features that were added, were only added once they were pretty much standard everywhere else.

I remember the first time I saw a lambda in a language... var foo = (x, y) => x * y

What...the...fuck...is going on there.

Of course, now that syntax or slight variations of it are everywhere, so most people will be able to read the above just fine, even if their language is choice doesn't use that exact syntax (ie: ruby). The C++ version is a little messy, but it sure as hell was needed.

Same thing can be said of most of the additions.

Entity Framework being slow isn't the problem with it. The performance of an ORM only really depend on 2 things. The time it takes to do the mapping, which is trivialized by the actual queries and is really a micro-optimization, and the SQL generated.

The later is fine in almost all of the mainstream ORMs, and the only real issues come from N+1 queries, and not aggregating queries that can be by using the context and futures. ActiveRecord based ORMs have issues because of the way context vs model objects is managed but they can still handle it fine, the N+1 problem is almost always a developer thing.

The reason Entity Framework sucks is that its API is poorly documented, so short of reading the code, no one knows how to do things correctly, a lot of its features are not exposed through the tools, thus encouraging using the RAD/shitty ways of doing things, and they pulled it in all directions trying to make everyone happy, ending up with a lowest common denominator.

You can get perfectly good performance out of EF, it has all the features an ORM needs to achieve it. Its just hidden/awkward/changes all the time/forces you into writing shitty code.

Development cost for these things is still pretty close to half the whole cost. If you think making an engine from scratch is gonna cost you less than 5% (though do take in consideration the cost of learning/using the engine is, as that's not zero), go for it. Some companies still do it. Fewer and fewer though.

Generally when people say compiled language, and they refer to things like Objective C and C++, they usually mean compile to as close to native code as possible. I love C#, but its fairly obvious that bytecode languages were not options this time around.

C++/Boost is their best bet.

QI chargers, already used across the Nexus line, and I _think_ some Samsung phones?

Im personally happy, since all my phones/tablet support Qi.

Looked at the site, can't wait to be able to try it (signed up on the site to hopefully get in the beta eventually).

We're also in Boston and starting to have remote teams/offices, but full digital whiteboards are a little too much for us. This looks like a sweet spot.

Except it happens all the time. In many profession. Even in Europe. Just google a little.

Its people's reaction to seeing naked pictures of you that are the problem. You can get fired, disqualified from jobs, shunned, and all around your life can become a living hell.

If you get beat up in a alley, the damage (aside for the psychological damage from the event itself) might go away once the wounds heal. If you're a teacher and students find pictures of you? You potentially can kiss your career (or at least your next promotion) good bye.

And its one thing if the person allowed the picture to be taken (though even then, but whatever), but a lot of people abuse of positions of trust, and a lot of those pictures are taken without consent. There's a LOT of assholes out there.

They were definitely referring to android/iOS tablets, which have all these push notifications and easy access to everything all the time, which is definately distracting to the average person. The average person also uses those as e-readers. A few years ago in the subway all you saw was kindles. Now you see a few (I see a bunch every day), but they're definitely outnumbered by people reading books on ipads or on their phones.

I'm still addicted to my kindle though and is my device of choice during my commute. The tablet is for when I want to browse the web.

Many developers ARE famous. If you're a dev who created some very popular/well known open source framework, you probably have an army trying to get to you. You're basically a celebrity, and in the extreme case may have to end up dealing with things like one.

My employer has been trying to build a front end team recently, and willing to pay whatever it takes and remote work is fine. But even getting in touch with some of these people to be able to say "Hey, name a number, we'll give you that number" is near impossible, because they shut themselves out with all of the normal recruiters trying to reach them.

Then you have the "not famous, but very good" devs. The average shitty dev still get a seemingly infinite amount of recruiters reaching out to them. The ones that are actually good? Yeah, its crazy. And if they don't want to go to work for a well known company (ie: Google), and actually have to poke around the market to find a good match, it can be more work than a full time job and a half. If you're looking and have an actually useful recruiter under your belt, its helpful, but at the end of the day they don't work for you. Having someone who actually does? Why not.

Its a pretty big deal actually. If every time you go to the store, they accept Apple Pay but not Google Wallet, and you're into that kind of thing, eventually you're going to get annoyed and buy a damn iphone.

And yet your card still worked, so it had a magstrip. And when I go back home to visit family (I'm canadian living in the US), my american cards work fine up there too. So someone could still clone your card, and use the copy. The only thing making it a little trickier is the fact you don't have to hand over the card, but there are ways around that (like a hacked up terminal). There are also vulnerabilities in the chip cards.

What is really protecting you is that the bank will cover your ass if something happen to it. This is also why no one gives a damn south of the border: pretty much no one ever really gets hurt when their card gets cloned. Call the bank and it will be done and over with 2 days later.

But with the chip cards, banks tend to be reluctant to help when your card gets owned. They still generally take care of it, but you have to argue a bit more.

So really, in the end it doesn't change a whole lot. Its easier to exploit magstrips, for now. And then you have all the chip cards that have NFC, and that's a whole other can of worm.

The one thing I'll give you is how its fucking annoying to have someone run away with your card at the restaurant, though some restaurants do have it (ie: Legal Seafood)