Visual Studio Code finally arrives on ARM64 Windows. No, you haven't woken up in 2017, sadly. It's still 2020 Good news for those who have splashed the cash on Microsoft's flagship Surface Pro X – the software behemoth has emitted an ARM64 build of Visual Studio Code. #ARM people! It's time to try @code Insiders right now! Nightly builds starting today for Windows 10 on ARM, including background updates!🙋♂️I admit, this Surface Pro X …
If Node.js is supposed to make "cross platform" easier via JavaScript, then WHY did it take so long for the internals running Node.js stuff to support ARM64?
I'm just a _bit_ confused, here. Java is cross-platform as long as there's a JVM. But we're talking SCRIPT here, which is interpretive. Just what hardware-dependent things are the Node.js and other supporting libs DOING that you can't just re-compile them for ARM64 and be done with it?
In my opinion, Micros~1 might as well JUST USE C/C++ and be done with this kind of "unexpected incompatibility". You could use it with wxWidgets, Qt, or GTK for cross-platform compatibility, too. Or, maybe fix MFC so that it SUPPORTS LINUX... I think that would be _AWESOME_ !!!
_SO_ many OTHER possible solutions, yet they chose something based on Node.js ...
"Hasn't Chromium been running ARM64 for years though?"
As far as I know, yes (especially for any Android devices that are arm64).
But I don't think Chromium is dependent on 'electron' which (I might point out) is most likely the thing that ultimately determined that VS code would use Node.js. And, as far as I can tell, Chromium is mostly C++ code (unless this changed since the last time I looked at it). Being that the library bottleneck (aka 'electron') uses Node.js, it's a core part of the problem, using 'Node.js' at all.
This is great news for the 3 people developing apps on ARM64 Windows who'd want to use VS Code...
I'm still not sold on Windows on ARM64 because the hardware makers don't seem sold on it. The only readily available ARM64 Windows system is the Surface X and Microsoft has proven many times that they're unable to kickstart new architecture support in Windows by building their own hardware. I'd love to be wrong here, but 3rd party ARM software on Windows is basically non-existant.
The only way I'd want to live through 2017 again is if I woke up in January '17 and '16 had been a nightmare, and Bernie was about to be president. I'd settle for Hillary. But it's been over 3 years of neverending nightmare now, hopefully I'll live long enough to see the orange shitgibbon gone.
The death count here will probably hit 200k before that happens. I'm sick now, probably going to get tested Monday if it doesn't get worse, quarantining this weekend. I've got ok health insurance, many don't.
Just been ejected from a Windows 10 install......Microsoft wanted an active broadband connection, then an email address, and then sent an "authorisation code" to my landline.....so lots of PII slurping, and the DEMAND for a mobile phone number (so the authorisation text message would work)........all this because a Microsoft online account is MANDATORY for me to use my own equipment..........all this just last Thursday. To paraphrase Nike -- "Just don't do it!".
*
I abandoned the "factory install", reformatted the hard drive...........and installed another OS.
*
CODA: Reviews of my new machine (£400) say it's marginally useful on Windows 10......too cheap.....not the £1000+ required for a "powerful" Microsoft Surface. But in actual fact, used with the alternative OS it's a delight. No processing problems at all once Windows 10 is replaced by something less bloated. Why do people put up with huge costs AND PII slurping? Someone here will no doubt be able to explain.
You don't need to use a Microsoft Account to sign in to Windows 10.....There's an option to skip that and sign in with a local account instead but you must have thrown your toys out of the pram before noticing it I guess......Seen and used plenty of £300 - £550 machines that run Windows 10 just fine.
If you didn't get through the install because you mistakenly thought you needed a MS Account (they do make it tricky to spot the small link with the option, that's on them.....not bothering to read the full page is on you) how do you know Windows 10 doesn't run well on the device?
Out of interest what are the specs of the machine? A lot of tech reviewers talk out of their arse and think everybody needs a top spec i7 device to do anything, so I wouldn't 100% trust their assessment of how well a device will run Windows 10.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
