Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vscode.dev

code.visualstudio.com

Post reply on HN
Print view View original

11–20 of 273 posts

Re: Vscode.dev

#11

Post by dustinmoris »

MR4D wrote: post #2

I find a couple things pretty neat here: 1 - All of the screenshots are from a Mac. This never would have happened with the old MSFT. 2 - The performance of this is pretty good. Admittedly, I just played with this for a couple minutes, but even opening a folder with a bunch of files was snappy.

This is because Microsoft doesn't seem to want Windows developers to use VS Code. They want to keep them locked into Visual Studio and Windows Azure, which is why the C# plugin is one of the worst from all language plugins in Code.

Re: Vscode.dev

#12

Post by dudus »

> quickly parked it (...) (or, if you are from the Boston area like me, we "pahked it"

What a strange joke to include on Developer docs.

Re: Vscode.dev

#13

Post by Androider »

ARandumGuy wrote: post #4

This 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…

Surely shoving VSCode into a tab is just step 1. Think about what this could do, that your local app couldn't.

Off the top of my head: Complete remote state. Open vscode.dev on your desktop, work for a while. Then open vscode.dev on your Macbook Air later, and be in _exactly_ the same state. I don't mean, the same project, I mean the text cursor is at the same position in the same file with the same set of tabs open.

Need a GPU for some CUDA work? The only question is how many GPU cores would you like.

Could your next engineering hire's onboarding guide be: open vscode.dev/company/workspace, click the "run all tests" button. OK, you're done, please pick the topmost "ready to start" ticket from the queue.

Re: Vscode.dev

#14

Post by minimaxir »

OliverGilan wrote: post #6

I 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.

See https://github.com/gitpod-io/openvscode-server which has that design philosophy.

Re: Vscode.dev

#15

Post by judge2020 »

dudus wrote: post #12

> quickly parked it (...) (or, if you are from the Boston area like me, we "pahked it" What a strange joke to include on Developer docs.

This is on /blogs and has an author under the title of the post.

Re: Vscode.dev

#16

Post by wffurr »

ARandumGuy wrote: post #4

This 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 client-side HTML, JavaScript, and CSS applications in conjunction with the browser tools for debugging.

* Edit your code on lower powered machines like Chromebooks, where you can't (easily) install VS Code.

* Develop on your iPad. You can upload/download files (and even store them in the cloud using the Files app), as well as open repositories remotely with the built-in GitHub Repositories extension."

Also various interesting URLs are now possible:

"For example, change https://github.com/microsoft/vscode to 'https://vscode.dev/github.com/Microsoft/vscode'.

For Azure Repos, do the same. Change https://dev.azure.com/… to 'https://vscode.dev/dev.azure.com /…'."

"As you can see, vscode.dev URLs are a powerful way for us to deliver new, lightweight experiences. Another example is that Live Share guest sessions will also be available in the browser through the https://vscode.dev/liveshare URL. The sessionId will be passed to the extension to make joining a seamless experience."

Re: Vscode.dev

#17

Post by matthewhammond »

ARandumGuy wrote: post #4

This 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…

For me the point is more around generally pushing things towards the cloud and away from snowflake local environments. One click app generation from templates, one click deploys of your app to ephemeral environments for testing and sharing... all without requiring any setup, and integrated into GitHub for collaboration. Want to onboard someone to working on your app, just send them a hyperlink to the repo.

Re: Vscode.dev

#18

Post by factorialboy »

up6w6 wrote: post #3

Not open-source yet, the best alternatives for self-hosting right now are: https://github.com/gitpod-io/openvscode-server https://github.com/cdr/code-server Update: also check the discussion about their differences https://github.com/cdr/code-server/discussions/4267 (IMO both are much slower and worse than vscode.dev)

+1 for GitPod .. Stellar integration with GitLab as well for CI / automation

They claim Github integration as well (although I have not tried that yet).

Re: Vscode.dev

#19

Post by minimaxir »

For those who think web-based IDEs are inefficient, I recommend giving VS Code in the browser a try: nowadays it's just as performant as it is on the desktop.

Even on the iPad it's just as performant (with 120Hz scrolling!), although as noted in the announcement, the file system limitations make it a bit of a pain to work with for ad hoc coding.

Re: Vscode.dev

#20

Post by aptxkid »

dudus wrote: post #12

> quickly parked it (...) (or, if you are from the Boston area like me, we "pahked it" What a strange joke to include on Developer docs.

Proud to be a Bostonian!
Post reply on HN