> 1. Right-click on your desktop and select New Folder 2. Type in or copy and paste the following as the name: GodMode.{ED7BA470-8E54-465E-825C-99712043E01C} 3. Hit Enter and the folder icon will change to GodMode 4. Enjoy easy access to all Windows 10 settings!
I know that the exception came from GetDisplayNameOf handling it incorrectly, but this whole thing begs the question:
Why is this a good way to do shortcuts?
https://msdn.microsoft.com/en-us/library/cc144096(VS.85).asp...
Side note, does anyone have experience using Excelsior Jet to deploy natively compiled applications or services?
Overall, I would say that AOT suddenly becoming kosher helps our business way more than competition hurts it.
Then, "JDK9 has AOT out of the box" is a bit of exaggeration. Oracle AOT is only available for Linux/x64 ATM, yields huge binaries and may be a bit cumbersome to use: http://mjg123.github.io/2017/10/04/AppCDS-and-Clojure.html
The main difference however is that a binary produced by Oracle AOT is to a big extent just a pre-populated HotSpot cache, whereas Excelsior JET has been AOT-centric since day one. In practice that means that with Oracle AOT you have to ship both the native binary and the original class files to your customers, and with Excelsior JET you only ship the native binary, which makes reverse engineering your application more difficult.
I recall us being quite surprised when a customer survey had shown that IP protection is more important than application performance for many of our customers, even though it was just a byproduct of our optimization efforts.
I wouldn't call it "malformed" -- the OS simply returned a null pointer: "the field that is supposed to point to the buffer containing the resulting string is NULL." Which in C means "nothing there." And the Java native interface code didn't check for that (it could have returned an empty Java string in that case), but dereferenced the null pointer instead. "Fail fast" indeed.
1: https://msdn.microsoft.com/en-us/library/windows/desktop/bb7...
https://msdn.microsoft.com/en-us/library/windows/desktop/bb7...
That would mean the API behaved according to the specs. See an example here, it's impossible for the call to destroy the pointer to STRRET:
https://msdn.microsoft.com/en-us/library/windows/desktop/bb7...
I suspect that you missed fhood's joke, or else I missed yours.
(It is not unreasonable to suppose that another path to the existence of operating systems would be the, perhaps human-guided, evolution of progressively less primitive programs. I am not sure that I'd want to use the result, but it's at least a conceiveable way for history to have developed.)
