If file access is supported by all browsers, this accompanied with WASM could lead to a new era for web apps.
Vscode.dev
51–60 of 273 posts
Re: Vscode.dev
#52This seems really cool, and seems like it took a lot of man hours to put together. However, I'm not sure who this is for. Downloading and installing an application is not a particularly big ask for the type of people who use VSCode. The browser version will always be a compromised experience, given the inherent limitations of browser applications. Even if it works 99% of the time, that 1% would add enough friction to…
> However, I'm not sure who this is for. Downloading and installing an application is not a particularly big ask for the type of people who use VSCode It's like how nerdy types could easily slap together their own Dropbox, with rsync and duct tape (as per the famous comment), but most didn't - plus the world is not just full of types who'd do it. And then MS can start adding all kinds of collaboration tools built in,…
Not to mention corporate rules.
Re: Vscode.dev
#53What api is it using to let you create a file in a local directory? I know about https://developer.mozilla.org/en-US/docs/Web/API/FileSystem but that's for virtualized filesystems
The File System Access API: https://developer.mozilla.org/en-US/docs/Web/API/File_System...
e.g. https://developer.mozilla.org/en-US/docs/Web/API/Window/show...
will give you access to a handle representing a directory on the user's real file system
Re: Vscode.dev
#54It’ll be interesting to see how this evolves compared with other players in this space. (Stackblitz comes to mind. They added support for “WebContainers” recently, for in-browser hosting of server-side code: https://news.ycombinator.com/item?id=27223012)
Re: Vscode.dev
#55I've love to see this for open source, especially integrated into GitHub. A simple "click here to contribute" button could really lower the barrier to entry for first-timers.
This has been around for a year now: https://github.com/features/codespaces
Re: Vscode.dev
#56I wonder if this uses pretty much the exact same code as the desktop version. It seems to me that one of the big benefits of using Electron would be to have one codebase deployable as a desktop app and a website with very little change for each deployment.
It's going to use most of the frontend UI code but all of the NodeJS-specific stuff in the desktop version is a no-go and has to be shimmed or polyfilled to run in the browser. The biggest thing you lose here is system-level access like the ability to run processes--tests, terminals, debugging, etc. And as the blog post mentions unfortunately these things aren't supported yet in vscode.dev.
Re: Vscode.dev
#57I don't think this will be a success.
If I get to choose between this and my own local installation, of course i will run the local version.
Why would I want to sit in the browser? To continue on the same cursor position I was if I switch computer? Not worth it at all.
Re: Vscode.dev
#58>"Fast forward to today. Now when you go to https://vscode.dev , you'll be presented with a lightweight version of VS Code running fully in the browser." Does that imply there is functionality missing from the online version of VS Code?
Some extensions aren't available, such as GitLens.
Yeah, the first thing I tried was to install some Go extensions. I guess they'll need to have separate web versions (or some sort of extra qualifiers)
Re: Vscode.dev
#59FYI: You can't run/compile your code (yet), and by extension it means it won't show any error/warning (I tried deleting some lines). I'm guessing the next step is cloud build.
Re: Vscode.dev
#60This seems really cool, and seems like it took a lot of man hours to put together. However, I'm not sure who this is for. Downloading and installing an application is not a particularly big ask for the type of people who use VSCode. The browser version will always be a compromised experience, given the inherent limitations of browser applications. Even if it works 99% of the time, that 1% would add enough friction to…
FTA: "This simple gateway to the local machine quickly opens some interesting scenarios for using VS Code for the Web as a zero-installation local development tool, such as: * Local file viewing and editing. Quickly take notes (and preview!) in Markdown. Even if you are on a restricted machine where you cannot install the full VS Code, you may still be able to use vscode.dev to view and edit local files. * Build clie…
Your solutions are to problems that a decent developer doesn't accept anyway.
Working on locked down machine where you are not allowed to have visual code? Seriously?
Working on a chromebook? Why?
Sorry to be negative but I feel sometimes you tech guys get excited about solutions to problems that doesn't actually exist in the real world.