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

VSCode on Google Colab

amitness.com

Post reply on HN
Print view View original

41–50 of 53 posts

Re: VSCode on Google Colab

#41

Post by johnisgood »

wvenable wrote: post #38
johnisgood wrote: post #34

> modifies it to run in a browser. The future is truly horrifying. I do not want to run my text editor in my browser. Soon our text editors will be hosted by Google or something, and we will edit files with them online. Ugh. Imagine requiring Internet connection and a browser just to edit a file on your computer! I know I am exaggerating a bit, but jeez, this direction sucks.

Browsers don't have access to local files so this isn't about editing a file on your computer. VS Code runs on electron so it is already an editor running in a browser locally without an Internet connection required.

> Browsers don't have access to local files

What do you mean by that? Mine does. Although I firejail it.

> VS Code runs on electron so it is already an editor running in a browser

I am sure we can push it further than that. :)

Re: VSCode on Google Colab

#42

Post by johnisgood »

wffurr wrote: post #36
johnisgood wrote: post #34

> modifies it to run in a browser. The future is truly horrifying. I do not want to run my text editor in my browser. Soon our text editors will be hosted by Google or something, and we will edit files with them online. Ugh. Imagine requiring Internet connection and a browser just to edit a file on your computer! I know I am exaggerating a bit, but jeez, this direction sucks.

Too late? That's essentially what Vscode, the most popular text editor for programmers, does. Nothing stopping you from continuing to use vim, emacs, sublime, etc though.

Yeah, I am sure the workplace will be perverted first.

Re: VSCode on Google Colab

#43

Post by wvenable »

johnisgood wrote: post #41
wvenable wrote: post #38

Earlier quoted context omitted.

Browsers don't have access to local files so this isn't about editing a file on your computer. VS Code runs on electron so it is already an editor running in a browser locally without an Internet connection required.

> Browsers don't have access to local files What do you mean by that? Mine does. Although I firejail it. > VS Code runs on electron so it is already an editor running in a browser I am sure we can push it further than that. :)

Web applications don't have access to local files -- at least not in the open/edit/save editor scenario.

Re: VSCode on Google Colab

#44

Post by johnisgood »

wvenable wrote: post #43
johnisgood wrote: post #41

Earlier quoted context omitted.

> Browsers don't have access to local files What do you mean by that? Mine does. Although I firejail it. > VS Code runs on electron so it is already an editor running in a browser I am sure we can push it further than that. :)

Web applications don't have access to local files -- at least not in the open/edit/save editor scenario.

I am not up to date with it, to be honest. I know there is a WebUSB API and whatnot. Having access to files might not be that far-fetched.

Re: VSCode on Google Colab

#45

Post by wvenable »

johnisgood wrote: post #44
wvenable wrote: post #43

Earlier quoted context omitted.

Web applications don't have access to local files -- at least not in the open/edit/save editor scenario.

I am not up to date with it, to be honest. I know there is a WebUSB API and whatnot. Having access to files might not be that far-fetched.

I have a robot who's firmware can be updated via bluetooth from a web application running in Chrome -- so I get your point. Oddly enough, arbitrary access to files are still off limits.

Re: VSCode on Google Colab

#46

Post by tracker1 »

babuskov wrote: post #20

I'm curious. I know it's great for one-offs, but is anyone actually using VSCode as their main tool when so many native IDEs and text editors are available? I would love to know what's your use case. Maybe I'm missing something big.

Absolutely... directory tree view and integrated terminal are the two big killer features for me... everything else is just extra awesomeness. Support for JS projects is pretty much best in class (Though jetbrains/webstorm is decent too).

Support for other languages like go, rust, C# (.Net Core) are pretty decent. The extensions/marketplace is incredible in terms of the breadth and depth of support for almost anything you can think of. I even have an enviornment setup with a settings file defaulting to CP437, where I use SSH remote extension in code to configure a remote telnet BBS.

Beyond all of this, it's relatively quick to load and run, though there are faster editors, I haven't seen a (much) faster IDE really.

The remote ssh extension is probably the third killer feature for me. I've gotten a lot of mileage out of those three things alone. I don't use some of the other features nearly as much as I rely on the console a lot, and the integrated terminal just makes it in the box as an experience.

Re: VSCode on Google Colab

#47

Post by wffurr »

johnisgood wrote: post #42
wffurr wrote: post #36

Earlier quoted context omitted.

Too late? That's essentially what Vscode, the most popular text editor for programmers, does. Nothing stopping you from continuing to use vim, emacs, sublime, etc though.

Yeah, I am sure the workplace will be perverted first.

wat

If you don't like it, don't use it. No one is forcing you.

Re: VSCode on Google Colab

#48

Post by candiodari »

echelon wrote: post #33
shp0ngle wrote: post #6

Note that this is not "actual" VSCode, but its fork code-server, that takes VSCode and modifies it to run in a browser. https://github.com/cdr/code-server This package just installs code-server on Google Colab, whatever that is. Hosted VSCode instances that Microsoft has on Azure and in beta on GitHub are a different thing and are not open source.

> Hosted VSCode instances that Microsoft has on Azure and in beta on GitHub are a different thing and are not open source. I can see it now: one day all of our engineering work will happen exclusively in the cloud and we'll all be using thin clients. Just like smart phones, the typical desktop or laptop will become a dumb device. A Chromebook, but worse. Subscribe to your tools, for the low monthly cost of only... An…

https://www.gnu.org/philosophy/right-to-read.en.html

Re: VSCode on Google Colab

#49

Post by farisjarrah »

nwienert wrote: post #39
echelon wrote: post #33

Earlier quoted context omitted.

> Hosted VSCode instances that Microsoft has on Azure and in beta on GitHub are a different thing and are not open source. I can see it now: one day all of our engineering work will happen exclusively in the cloud and we'll all be using thin clients. Just like smart phones, the typical desktop or laptop will become a dumb device. A Chromebook, but worse. Subscribe to your tools, for the low monthly cost of only... An…

Yep. And Google Colab is a Trojan horse. Give away free GPUs for a few years to choke out any competition, guaranteed they start charging for them once they’ve done that.

I like seeing arguments like these and then I go and see people do stuff like this where people get Debian running on Kindles:

https://github.com/kathamer/DebianKindle

Whenever there is locked down hardware, invariably there is always someone trying to hack it.

Re: VSCode on Google Colab

#50

Post by ralphc »

babuskov wrote: post #20

I'm curious. I know it's great for one-offs, but is anyone actually using VSCode as their main tool when so many native IDEs and text editors are available? I would love to know what's your use case. Maybe I'm missing something big.

Couple of years ago Salesforce switched from Eclipse plug-ins for development and went all in on VSCode. They have a set of plug-ins that log in to Salesforce and send configurations and code back and forth. They're even going to use "VSCode in the browser" to edit code in place in your organization.
Post reply on HN