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

131–140 of 273 posts

Re: Vscode.dev

#131

Post by davedx »

paxys wrote: post #125

It's crazy how much the dev tooling space has evolved in just the last few years. VS Code is of course a big part of it, but there are a hundred offshoots providing CI/CD, dev VPS, source control integrations, language tools, static hosting, staging, functions. The next step, IMO, is more clarity. How do all these puzzle pieces fit together, and what is the "ideal" solution for me as an individual developer or a smal…

There’s been loads of progress and some stuff has categorically improved the dev experience, but a lot of it is pretty chaotic churn (hello grunt, gulp, webpack, babel), and we are still missing out of the box UI tooling that shipped with Visual Studio like 20 years ago (MFC/VB forms). And let’s not even get started on the kind of stuff that was possible with Smalltalk.

The problem is much dev tooling is indeed so fragmented and mostly missing strategy or direction. It’s like a collective stream of consciousness that has a bunch of directions in mind.

I wonder if MSFT has the vision to reinvent some of the visionary dev tooling from the last century for the modern web. That would be really something.

Re: Vscode.dev

#132

Post by jaywalk »

imafish wrote: post #102
jaywalk wrote: post #31

Earlier quoted context omitted.

That's a pretty strange implication. I just tried opening up a .NET Core application in VS Code developed exclusively in Visual Studio, and it fired right up. Now I certainly wouldn't say that the debugging experience is as good as VS, but nobody should expect it to be. VS Code isn't supposed to be a replacement for VS, although it can certainly hold it's own. And it's free .

VS community is also free :)

Yes, but it has a very significant licensing restriction that prevents it from being used to develop commercial software. VS Code has no such restriction.

Re: Vscode.dev

#133

Post by phil294 »

It would be great if we could also run VSCode in terminal. It should theoretically totally be possible, but for some reason, there is still no good text-only browser supporting JavaScript.

Edit: Just tried brow.sh - only displays a white page. Might be a solution though

Re: Vscode.dev

#136

Post by WorldMaker »

qbasic_forever wrote: post #43

Interesting they're using tree-sitter for syntax highlighting. Obviously they can't run LSPs in the browser so this must have been an alternative. I'd be curious to see this get into mainline desktop VS Code though (and I'm not alone: https://github.com/microsoft/vscode/issues/50140 ).

The article points out that the Typescript/Javascript and Python LSPs run in the browser providing "better" experience than the tree-sitter experiences for languages without browser capable LSPs today.

Re: Vscode.dev

#137

Post by paxys »

Something worth noting – unlike offerings like Github Codespaces, code-server and others this one is running fully in your browser (no backing VM). This is both good (faster to start and run, no server roundtrips needed) and bad (can't install custom language toolchains or run build scripts, can't pause and restart on different machines). vscode.dev is specifically not a "cloud IDE".

Re: Vscode.dev

#138

Post by gkfasdfasdf »

Androider wrote: post #13
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.…

Saving state sounds pretty awesome indeed, but does it really work like that? From the blog post it sounded like it is opening files on the local filesystem.

Re: Vscode.dev

#139

Post by Godel_unicode »

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…

> ...the type of people who use VSCode

This type of gatekeeping helps no one. We should be optimizing for lowering barriers to entry, not justifying making an already hard problem (learning to code) harder.

> ...except in desperate circumstances...

Some 15% of American adults are smartphone only. That percentage rises very quickly once you look outside of the G20. Those are also some of the people most likely to have their lives drastically improved by having access to the ability to code.

The fact that you don't have a usecase for a tool absolutely does not mean that such a usecase does not exist, nor does it make that usecase less valuable.

Re: Vscode.dev

#140

Post by WorldMaker »

fetzu wrote: post #39
thurn wrote: post #32

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

I’m not sure if I am understanding your post correctly, but AFAIK you can just hit “.” from your browser on GitHub and it opens an editor (based on VSCode) for that repo. Not sure if Git is fully integrated in there (although, it being based on VSCode, it should).

Yes, just hitting dot in Github opens up Github.dev which is very similar to this VSCode.dev. So similar that this VSCode.dev lets you get the same experience if you rewrite a Github.com repo URLs and prefix it with VSCode.dev. Today VSCode.dev also supports the same thing with Azure Repos if you prefix dev.azure.com repo URLs.

The "remote repository" experience on VSCode.dev is a little more involved than just "fully integrated git" (it relies on the GitHub/Azure Repos APIs and existing VS Code extensions with Remoting support for some of it beyond just what raw git can provied), but they say in this article that it is extendable and they can and hope to add other providers in the future.

Post reply on HN