Some of those try much too hard, which is kind of silly because you don't need to reach very hard to find people saying stupid/ignorant things about any race/religion/sex/gender/orientation/whatever.
"Most girls aren’t into this kind of stuff." - Easily can be said about guys. In fact, most guys aren't into many stereotypical nerd pursuits.
"How did you learn to do all this?!" - Said to me all the time, and I'm a guy.
"Let me know when you want to do that so I can help you. No offense, but you just don’t know enough about it to try it on your own." - Said to me, and I'm a guy.
"See, that’s the great thing about you, I know I can tell ‘offensive’ jokes around you and you won’t care." - Coworkers say things that make me uncomfortable as well, and I'm a guy (I get squicked out when people start comparing how physically attractive people are, male or female, for example).
The problem is that the general public is going to take "unbreakable encryption" at face value. So don't worry, unbreakable encryption prevents the hacker from getting access to the golden key, because without the golden key even the government can't break into things. The whole thing feeds on itself.
Which is too bad. I'm curious about rtc's argument around machines taking the pictures. It seems the logical conclusion of his argument is that if you buy a camera, and the software on the camera takes a picture without the act of camera owner, then the owner of the camera doesn't own the copyright but instead the company that made the camera? That seems like a very strange conclusion.
Q contains some helper functions for creating generators, tying them to a promise, and automatically starting the generator, eg Q.async(). I've found that I'd rather continue using Q and use Q.async()/Q.spawn() rather than dealing directly with the generators and managing them.
Have you ever worked at Amazon? He did. For 3 years (I did for 4). I very much doubt PA is any worse than Amazon with regards to it being the job from hell. Everything in the PA job description is practically a carbon copy of what should be in every job description from Amazon.
"he probably has no idea what a market salary looks like"
Amazon doesn't pay as well as Google, but Amazon salary is really far better than you'll get at anything other than the four big tech companies for a normal SDE.
You're conflating their target functions. etcd is all about configuration distribution. Serf seems more like its about member discovery. So you might have a service you run in multiple clusters. Each cluster has a different configuration (etcd), and each instance in a cluster needs to know about the others in the same cluster because they talk to each other (Serf). You could make etcd handle all this, but it probably wouldn't do it as well (Serf has heart beats and recognizes dead nodes, etcd won't do that except for etcd nodes themselves).
No, you're just missing the point. People are focused on the profit and monetary cost of decisions based on their limited capacity to reason about time, which is on the order of probably 10-30 years (if we're being overly generous).
Reiterating, not putting all our eggs in one basket ie self-sustaining human populations not on Earth in the shortish term, not in our solar system in the less shortish term, and not in our galaxy in the longish term, is not something a single person is going to do in their lifetime. It may take (tens/hundreds of) thousands of years to accomplish these goals, if they are even possible, but we should start them now because the alternative is a random case of bad luck with a meteor, or a nutter with a thermonuclear or biological weapon, or whatever. Extinction events.
People struggle to see beyond their own needs and desires. If we're to survive as a species, we have to think and plan on time scales that dwarf the current recorded human history.
This isn't meant to be an indictment of you personally, I'm just pointing out that the view-point, though normal and held by the majority of people, is still short-sighted by definition: a human lifetime is nothing in comparison to human history, and the potential human future.
If Google was only interested in putting a faster language into Chrome they could have just shipped with LuaJIT for Lua and been done with it. Obviously they're more interested in playing around in their own sandbox (Dart).
I don't think there's a reason to bake futures/promises into the language. Once you've got coroutines (generators here), people can build the abstractions around them that they like.
That's a pretty terrible way to share code. Simple example: I work on a project, write some code. Turns out that code is useful for someone else, so they reach in and include it, which is easy since it's all the same repo and all delivered to the build system. Now I make a change and break some customer I didn't even know exists. Oops.
> Very common problem: interviewers asking questions about who was going to take care of the kids.
Not to excuse this, but it made me think of a rather terrible mistake I recently made, which I am glad has not come back to bite me. I was the last interviewer for a guy who was Jewish and didn't use technology on the Sabbath. As I was walking him back to the lobby I mused out loud that that was interesting since we have pager duty and I wonder what other teams do in that situation, since surely we wouldn't be the only team at the company who employed someone with that or similar restrictions. It wasn't until my wife pointed out to me that that was probably completely illegal and could have had serious repercussions for me that I thought I had done anything but muse about something meaningless out loud.
Sometimes people just don't think, I guess is my point.