It seems to me like "troubleshooting why the internet connection is down" is probably a capability you would want to have, no?
800 karma · joined April 30, 2014
It seems to me like "troubleshooting why the internet connection is down" is probably a capability you would want to have, no?
Next Thing says the C.H.I.P. (or at least the C.H.I.P. Pro) runs mainline Linux, but that's not really comparable to the current Raspberry Pi.
You may want to add the tilde to the path, as it seems to open to /mnt/c/Users/<username>/. Also, I think it still messes with the keys, but not always. They seem to work fine right after starting it.
They both run in Java, so you can combine Sikuli with Selenium pretty easily [0], so long as you're not doing headless testing. I've played around with it a bit, using Selenium to get coordinates of a container element and then having SikuliX operate just on that region of the screen.
[0]: http://www.softwaretestinghelp.com/sikuli-tutorial-part-2/
There are several limitations in the Windows/NTFS implementation, however:
1. You have to specify the target type (file or directory) at link creation time.
2. Creating symbolic links requires either being an Administrator user, or having the "Create symbolic links" group policy enabled for your account.
3. No real directory hard links. (EDIT: For some reason, I forgot that Linux doesn't have these, either. Maybe I was thinking of bind mounts.)
From about halfway down the page:
> This is probably the first OpenGL renderer for PSX that is not based on outdated fixed-function OpenGL code and which is, actually, well, open-source. Because we can assume shaders will be there, we can get reasonably close to emulating texture windows accurately (with Pete’s OGL1 GPU plugin, there were codepaths for doing it with paletted textures – the hacky approach – and the pixel shader approach). Therefore, the renderer is still kept pretty simple and easy to understand.
I wish I could afford to ignore Internet Explorer... if Microsoft leaves Windows 7 to rot with IE 11, corporate users are going to keep holding back the web for a few more years.
My wife thinks I'm weird, but I hate the taste of regular Coca-Cola. I much prefer Diet Coke.
For a quick snacky lunch, I love celery and cream cheese or, depending on what mood I'm in, celery and mayo.
In the meantime, you can download the online installer [1] and run
vs2015.2.exe /Layout
to launch the downloader, which should create a folder which contains everything that you would find on the update ISO. (EDIT: This seems to result in a 4.53 GiB download, so definitely smaller than the 6.95 GiB full install ISO.)Depending on what version ranges dependencies are locked to, you could still end up with a pathological situation which breaks the path length limit, but I've only had that happen once since switching to npm 3, and it was easy to resolve.
It looks like Cygwin has a ping package, but it isn't something you'll get unless you specifically select it in the installer.
I wonder if this Unix filesystem layer will be able to break the Windows legacy path length limit. If so, the Linux version of Node.js will suddenly become much more useful than the Windows version.
> It remains to be seen if this is better (more performant) or worse
Sounds like performance, at least, will be better. TFA says "it's totally shit hot! The sysbench utility is showing nearly equivalent cpu, memory, and io performance." I'll reserve judgment until I see the fork() benchmarks. :)
There actually have been [1], and I imagine MS has continued to flesh out those improvements.
Nowadays, the most common use I've seen is as the Windows implementation of 'npm link' for Node.js developers.
The typical workaround in Java is to either pass around .class instances, or to do tricks with anonymous subclasses to create a type token. [2]
[1]: https://ideone.com/th18eh [2]: http://docs.guava-libraries.googlecode.com/git/javadoc/com/g...
There's a third-party tool [2] that is supposed to solve many of the issues, but I haven't tried it.
Of course, if you do this, there's a decent chance that if you try installing it again in 6 months, your shrinkwrapped version of at least one of the dependencies won't be available any more...
[1]: https://docs.npmjs.com/cli/shrinkwrap [2]: https://github.com/uber/npm-shrinkwrap
> The new way/API is unfortunately not working for Windows 7 due to a bug in the Windows HID Class Driver
[1]: https://github.com/dolphin-emu/dolphin/pull/3245 [2]: https://github.com/dolphin-emu/dolphin/pull/3245#issuecommen...
I keep hearing people say that, but I really don't think that's how it will turn out. Adblockers rely heavily on pattern-matching to work: scripts loaded from certain third-party domains, resources in particular subdirectories, markup structured with predictable element IDs/CSS classes, and the like. There are ways to break all of these: first-party ads, either by directly hosting them or by proxying your ad network; media served via embedded data: URIs or hash-based URIs; CSS which is minified, and randomized every few weeks; etc. These techniques may not be widespread yet, but I'm sure they will grow in popularity as the adblocking war rages on.
But hey, maybe ads will get a bit less egregious in the process.
Last I heard (um, a couple of years ago), USAA's solution was a proper API, but Mint was still screen-scraping. I have no idea if that's because Mint is lazy or USAA'S API is too limited for what they want, but my money would be on the former.
DRM is a problem, though. I don't think there's currently any way to get Amazon Instant Video working, which is the only thing keeping me from using my nVidia Shield TV as my sole media device.