71 karma · joined December 13, 2012
He complained about the readability of the content, I think it's a valid complaint. You might be able to read it just fine, but you don't represent 100% of the human race.
VR will be clearly more than just movies. And AR is far from just for smartphones. Granted HoloLens isn't ready and might not be that great, but it has so much more potential than just smartphone gimmicks. A good set of AR can completely replace my work setup, I wouldn't have the need for monitors anymore. I'm excited by that idea, a new way to interact with the world.
Are you judging this on their ability to invert a binary tree? People here are ranting about having a problem with interview practices not representing whether or not you are good at your job. That's presumably (IMO) why the tweet was posted.
I'm not surprised of the jump, I've been waiting for AMD to make such a jump so they could try to keep up with Intel's horsepower.
Not all places use salt, and even then if you get your car washed and underbody cleaned it should help the longevity of the car.
And ZFS is on a lot more than just FreeBSD, even if it's not official. ZFS started on OpenSolaris, not on FreeBSD. OS X has a port. Then FreeBSD got it's port. Linux has a stable port. And there are NAS OS's shipping with it like FreeNAS, TrueNAS, and a device called ReadyDATA by Netgear that has it.
I was mostly surprised at this: "The good stuff that probably won’t make it to NetBSD 7: Stable ZFS." So you're telling me ZFS isn't considered stable on NetBSD? It seems to be that it's pretty stable on quite a few other platforms, some mentioned above.
I personally think placeholders/known sizes are a must in web design. It really annoys me when I'm reading something and it gets pushed down due to slow loading images, etc.
I'm not saying that at all, I said early on that this is a problem. Refer to this in my first comment replying to you: "I don't think RaiseException is well defined. If it's only meant to be used for x86, it should be coded that way instead of relying on other code to enforce the behavior."
Internally it seems they only intended it to be used in specific cases, but there's nothing preventing anyone else from calling it when they shouldn't as you noted. This is bad design.
#if PLATFORM_EXCEPTIONS_DISABLED
FPlatformMisc::DebugBreak();
#else
FPlatformMisc::RaiseException( 1 );
#endifTechnically no, however it's only used in x86. It's only ever called if PLATFORM_EXCEPTIONS_DISABLED is 0. If you look up where PLATFORM_EXCEPTIONS_DISABLED is defined in Platform.h, you'll see it's only defined when not using PLATFORM_DESKTOP. PLATFORM_DESKTOP is disabled for Android, HTML5, iOS, WinRT, and WinRTArm. PLATFORM_DESKTOP is enabled for Linux, Mac, and Windows. So that instruction is only intended to be used in x86 desktop environments.
Considering this, I don't think RaiseException is well defined. If it's only meant to be used for x86, it should be coded that way instead of relying on other code to enforce the behavior.
Granted I've never used a service like Uber, so I can't directly understand where you're coming from.
Concerning #4 there's Console2, ConEmu, and Cmder which is a package with ConEmu.
There are solutions for all but one of the above, which I mention because Brew isn't an Apple driven solution, so I assume you don't mind other decent solutions not provided by Microsoft.
As I said, the results can't be tailored to your needs. For instance: when I search Python how does DDG know to bring up? Python can refer to the snake, the programming language, the horror film, the missile, the sports car, the turboprop engine, etc.. DDG doesn't know what I intend. It can try to go off of popularity though, or I have to feed it more keywords for what I'm actually looking for.
Granted other engines can have this issue, but I think DDG more susceptible to this problem.