Maybe there is something to the SV culture that's either rotten or just too self-absorbed to acknowledge there may be a problem. I'm down in SoCal (LA) and having worked for several small tech shops, I've never seen the issues that a lot of folks complain about up in SV. My workgroup is 50% female, and other than my manager, everyone is a minority (black, asian, indian-asian (and not H1Bs). Upper management tends to be of the white-male variety (I dunno, do we count gingers in that?) although our CEO is white female. I've been on the interview panels and it's not like we were hiring for diversity. We were just looking for people who had the technical know-how and personalities that would not be detrimental to our work group. And, I must add, our women engineers are engineers, not just "tech evangelists" or "tech spokeswomen" and the like that seem to get a lot of controversial press up there. Our black developers? The same. Maybe there really is a tech-bro-fraternity mentality in the SV, I've not moved up there to find out for myself (and as an asian, I don't imagine I'd actually see much of it directed against me, but who knows? More likely, I'd face issues because I'm over the age of 40).

You have to want a better streaming experience than Valve's Steam already offers for free (and you can buy a Windows Tablet for the same price, and Valve is expected to support Android and iOS soon). You can use whatever system and whatever video card you want to stream the game to and from - even go wired ethernet to get around the inevitable problems you get streaming games over wireless.

If you go Shield, the tablet price is just the beginning: you have to have a mid-range GeForce card purchased in at least the last 2 years ($120+ if you don't already have one), the controller + stand ($100), and of course a suitable dual-band router runs at least $70 (most people use the crap one that came with their internet install).

In all, you could be on the hook for anywhere from $400 all the way up to $600. That's getting DANGEROUSLY close to the same price as an entry-level gaming PC, so again the need just doesn't present itself there.

You do acclimate to caffeine, though. Caffeine blocks adenosine receptors, which would normally absorb the adenosine released into the brain, and as a consequence your body releases adrenaline when it tries to make you tired and fails. That's the real 'caffeine crash', the big bottoming out after an adrenaline rush. Keep ingesting enough caffeine, and your nerve cells respond by creating more adenosine receptors; that means you need more caffeine to block out the same amount of adenosine. It's not huge, since you are only talking about the tiny amount that gets into the brain, as the rest of the nerves don't respond quite the same, so 'addiction' isn't the giant issue that it is with other drugs.

This is not to justify the Mormon position about drugs, as my thoughts on the matter are "could I see the list of those available?", but to dismiss the idea that caffeine is somehow different from other drugs.

The article mentions sandbox tools that allow admins to test applications and see what the code and the libraries are really doing, but doesn't name any of them. Any /.ers know if there are FOSS or BSD tools of this sort? Or even cheap proprietary ones? I read the code for any library I use, and I try to add some assert() like statements where the lib dev might have felt them unneeded to be certain that nothing gets past memory boundaries. But everyone misses something now and then, and just look at the IOCCC to spot how code that looks like it does one thing can do something else.

As someone who has written a few apps (none for sale, just local use) I feel like the article was taunting developers, "We know how to tell if you've been duped by your library code, and while we'll bash on developers who don't read the code they use, we won't help out those are writing in a new language and might get tricked by some language specification (or in C's case, unspecified compiler-dependent behavior). We'll even tell you that tools exist, but we won't name even one of them." Sure, I can spend all day trying to guess what type of sandbox tool I'm looking for, and install and test 30 or so of them, but that opens up the same can of worms of trusting code that I haven't read.

Formatting ate my brackets. Chances are, if you're interested in a language, there's a /r for it. In that /r there's usually talk of projects built with that language, or articles comparing that to other frameworks. It's kinda like a wikipedia style hole you fall into. For example, on a whim I was looking at /r/smalltalk and found pharo. Once I was digging around pharo, found newspeak. Or in /r/lisp, found dr. racket while reading through. I haven't read through /r/linux though, mainly because I'm rather content with my Mint installation, although I have been eyeing trying a slack release again on another box.

Honestly, /. still gives me some leads on occasion. hacker news, reddit.com/r/, and then just googling for shit.

Hell, I'd be happy if we could open up code shops on Indian Reservations here and help get a lot of those kids out of their cycle of poverty and alcoholism.

This hasn't been my experience. It's hard to find qualified people - they've all got decent jobs already. It's the unskilled workers that are struggling with unemployment (and underemployment).

/* so is there no shame for a guy to report being sodomized against his will by a man? */

Speaking as a man, I would much prefer admit I'd been sodomized against my will by a man than raped by a woman. Either scenario sucks, but most men can understand some gigantic physical specimen of a psycho raping another man, or being gang raped in prison. Almost no man wants to admit that some "girl" fucked him against his will, or used her position of power to gain "sexual favors" as a metric of job performance. Sorry.

You'll notice in the second half if my post that I called the separate controller + tablet + stand gaming method CLUMSY, and praised the original Shield for including all-in-one. This is because I also agree with you that this sort of gaming is untenable, and I actually gave up and bought a 3DS about 6 months back to get my portable gaming fix.

Touchscreens suck for gaming!

Also, you'll notice I suggested the WIRED 360 controller because it's not nearly as complicated as pairing a wireless bluetooth controller. Just plug it in, and play your games...or you can sit here all day and complain about Android breaking your favorite bluetooth controller.

And your point is?

Games are being produced for the mainstream to high-end currently out there, so a SoC with twice the power brings nothing useful to the table. And streaming PC games requires none-of-the-above GPU power, so it's one of those questionable value cases.

Then there's also the concern about whether K1 will throttle under load, since this tablet doesn't have a fan like last year's Shield did. You'll notice that NONE of today's reviews go into that level of detail, and that's probably no accident.

With something as simple as a USB OTG adapter and a wired Xbox controller.

Believe it or not, most modern Android games already support the Xbox controller, and if you're gaming on such a tiny screen you can believe me that the wireless controller is NOT a necessity (will be 1-2 feet away at most). You can buy a $200-ish entry-level Android tablet that can handle games just fine, and reuse the Xbox controller you undoubtedly already have. So, why would you spend $300 + $100 for the same thing with an Nvidia label on it?

I'm actually disappointed that they didn't stick with the concept of the original Shield, and deliver another handheld gaming system; that alone is the only thing you cannot find in the Android world. If they insist that you use a clumsy tablet setup involving a screen prop and a separate controller, then why do we have to buy the tablet, screen prop and controller FROM THEM?

Very few and far between.

Well, exactly. Who the fuck wants to actually, you know, work for IBM? A gigantic, monolithic mega-corp with a potentially stable (not anymore!) cube job answering to middle management assholes, stuck in meetings, and occasionally getting to code for. Look, that might be your idea of a good job, but for many of us Open Source supporters, we're not wearing a tie or cutting off our beards just so we can get 'paid' to do open source. So when someone says "no one's getting paid to work on open source," what they mean is, there aren't many one man or 5 man shops developing Open Source for a living. There are exceptions, but there's a million projects out there that prove the rule.

Whether or not this is a good thing, I don't know, but I sure as hell didn't decide when I was 8 years old "Mommy! Daddy! I wanna be a numbered cube worker!" /snark