3,439 karma · joined March 5, 2014
The fact that it provides those relevant links is what allows it to replace Google for a lot of purposes.
I think three things about what you're saying:
1. The answers you're giving don't provide a lot of signal (the queue one being the exception). The question that's implicitly being asked is not just what you would choose, but why you would choose it. What factors would drive you to a particular decision? What are you thinking about when you provide an answer? You're not really verbalizing your considerations here.
A good interviewer will pry at you to get the signal they need to make a decision. So if you say that back-pressure isn't worth worrying about here, they'll ask you when it would be, and what you'd do in that situation. But not all interviewers are good interviewers, and sometimes they'll just say "I wasn't able to get much information out of the candidate" and the absence of a yes is a no. As an interviewee, you want to make the interviewer's job easy, not hard.
2. Even if the interviewer is good and does pry the information out of you, they're probably going to write down something like "the candidate was able to explain sensibly why they'd choose a particular technology, but it took a lot of prodding and prying to get the information out of them -- communications are a negative." As an interviewee, you want to communicate all the information your interviewer is looking for proactively, not grudgingly and reluctantly. (This is also true when you're not interviewing.)
3. I pretty much just disagree on that SQL/NoSQL answer. Team expertise is one factor, but those technologies have significant differences; depending on what you need to do, one of them might be way better than the other for a particular scenario. Your answer there is just going to get dinged for indicating that you don't have experience in enough scenarios to recognize this.
But definitely not absinthe.
I found interacting with it via chat to be super-useful and a great way to get stuff done. Yeah, sometimes you just have to drop into the code, and tag a particular line and say "this isn't going to work, rewrite it to do x" (or rewrite it yourself), but the ability to do that doesn't vitiate the value of the chat.
To put this very concretely, look at Pimax. Their Crystal headset allegedly has standalone capability. All the hardware is there for it, they make this thing, they sell it -- but they don't have a standalone platform, and have no hope whatsoever of being able to develop one.
For PCVR, they just use regular standard SteamVR and OpenXR, but for standalone usage, they suddenly have to be an amazing software company and they definitely are not. Using Horizon makes a ton of sense, and makes their product more attractive and better than it is without it.
I think that pre-Proton, Linux gaming was somewhat marginal -- some things worked, but a lot of AAA stuff didn't -- but these days, it's much, much better.
Hixie's criticisms of it were correct, and WHATWG was the kick in the pants that the W3C needed to focus on relevant things again.
Cynically, this is probably why they're releasing new, NACS-enabled cars (which will presumably charge at full speed on Tesla chargers) before releasing the adapter -- so that when owners of the existing cars realize how bad the experience is, new buyers will already have a better car available to buy, and won't need to worry about how this transition screwed over everyone who already bought a Hyundai/Kia EV.
Because it's Framework, you can of course buy the heavier hinge and put it on the older models; I haven't, because it's not a problem for me, but if it's one for you, it's a fix you can do cheaply.