Slashdot Mirror

← Back to Stories (view on slashdot.org)

Community Ports 'Visual Studio Code' To Chromebooks, Raspberry Pi (infoworld.com)

Posted by EditorDavid on from the IDE-ideas dept.

An anonymous reader quotes InfoWorld: A community build project led by developer Jay Rodgers is making Visual Studio Code, Microsoft's lightweight source code editor, available for Chromebooks, Raspberry Pi boards, and other devices based on 32-bit or 64-bit ARM processors. Supporting Linux and Chrome OS as well as the DEB (Debian) and RPM package formats, the automated builds of Visual Studio Code are intended for less-common platforms that might not otherwise receive them. Obvious beneficiaries will be IoT developers focused on ARM devices -- and the Raspberry Pi in particular -- who will find it helpful to have the editor directly on the device they're programming against... Rodgers said the lure of Visual Studio Code for him was its user-friendly interface, making it approachable for new users.

3 of 79 comments (clear)

  1. In other news... by GerbilSoft · · Score: 1, Informative

    Community "ports" slashdot.org to Chromebooks, Raspberry Pi.
    Community "ports" microsoft.com to Chromebooks, Raspberry Pi.
    etc... You get the idea.

    Visual Studio "Code" isn't Visual Studio. It's also not a real program. It's merely a JavaScript "app" website wrapped in a copy of Chromium.

    1. Re: In other news... by Anonymous Coward · · Score: 1, Informative

      30 years ago they were a tech company. Now they're a legal company run by a lawyer.

  2. Re:Android by The+MAZZTer · · Score: 4, Informative

    Nope. VS Code runs on Electron, which runs on Windows, MacOS, and Linux. No Android. Since Electron is essentially the Chrome web browser stripped down you could, in theory, have a cloud version that Android could load up in Chrome, but you'd have to rewrite anything relating to file handling and keyboard handling (as most Android devices don't have a hardware keyboard). It would take a lot more work to port it. I would imagine in this project's case they just had to port any native code modules to Linux and change any external process usage to work with Linux tools.