Live data from Hacker News

The Era of Visual Studio Code

blog.robenkleene.com

11–20 of 698 posts

Re: The Era of Visual Studio Code

#11
post #2

Given the talks from Microsoft's own React Native team regarding the 300x performance loss from Electron based apps, I am looking forward to the day it gets rewritten in React Native. https://youtu.be/IUMWFExtDSg?t=1146

I'm looking forward to the day when you can have multiple windows open on the same project without going through some horrible kludge. Some of us (!) have more than one monitor and would like, say, to put the debug widgetry over on _this_ one. (Edit: fixed three typos.)

I am glad someone else shares my pain.

Re: The Era of Visual Studio Code

#12
The "Aggressive development" point is what got me to switch to VSCode from Sublime. While most of my colleagues were switching to VSCode, I stuck with Sublime, after never fully jumping into Atom for performance reasons. However - and I'm assuming due to the open source nature of the platform, or the accessibility of JS vs Python, extensions were just higher quality on VSCode. I think the Go extension is maintained by Microsoft themselves. Very soon things just worked better in VSCode.

Re: The Era of Visual Studio Code

#13
> Learning software is an investment, and if you have to switch to another application later, you lose some of that investment.

Learn lazarus, what's that: a data module. A neat way of grouping related data sources and sharing them between forms which can query datatables.

Learn spring boot. What's that? Services. A neat way of grouping related repositories which can query entities.

Turns out if you learn one thing very well you know a lot of other things that are similar in nature.

Re: The Era of Visual Studio Code

#14
post #9

VS Code is awesome. If you told me ten years ago my daily driver text editor on Linux would be a Microsoft product, well, you’d have been right. Sane defaults. Snappy interface. Universal UI on multiple OSes that doesn’t suck. First class and best in class TypeScript support. It’s going to be hard to beat, now or five years from now.

It's good for JS. It's ok for Golang, since there doesn't seem to be anything better that's free. But I still feel it's an editor trying to be IDE. I love it for markdown/asciidoc though.

Re: The Era of Visual Studio Code

#15
VS Code, the text editor, is a trojan horse.

Microsoft is selling you into the IDE, in small portions. This is similar to the IBM approach with JAVA last decade(s?).

You install a "text editor" for simple things, like code completion. Before you realize you don't even know which compiler you are using or where it came from. You just press F5 and look at convenient break points. And somehow it only runs right on Azure :) the last one is a joke (for now?)

As a language popularity grows, it approaches the Java curve. Just like nobody who uses `npm` like (or know) maven, nobody using VS Code know about the old java IDEs, and how they become todays Java IDEs. Or how the React monolith is the same as the Java Monolith.

I guess people mixing up java and javascript in the 90s... just thad more, long term vision?

Re: The Era of Visual Studio Code

#16
post #2

Given the talks from Microsoft's own React Native team regarding the 300x performance loss from Electron based apps, I am looking forward to the day it gets rewritten in React Native. https://youtu.be/IUMWFExtDSg?t=1146

I'm looking forward to the day when you can have multiple windows open on the same project without going through some horrible kludge. Some of us (!) have more than one monitor and would like, say, to put the debug widgetry over on _this_ one. (Edit: fixed three typos.)

Speaking of which, as a light user of VS Code, is anyone else completely confused by the project / workspace interface? I'm always confused as to what project or workspace I'm in and what file is associated with what workspace, and what mode I'm in. The UX could use some love with the onboarding experience.

Re: The Era of Visual Studio Code

#17

The "Aggressive development" point is what got me to switch to VSCode from Sublime. While most of my colleagues were switching to VSCode, I stuck with Sublime, after never fully jumping into Atom for performance reasons. However - and I'm assuming due to the open source nature of the platform, or the accessibility of JS vs Python, extensions were just higher quality on VSCode. I think the Go extension is maintained b…

The Go extension is now maintained by the Golang team: https://golang.blog/the-vs-code-go-extension-joins-the-go-pr...

Re: The Era of Visual Studio Code

#18
post #6

I hate visual studio programs. They are always so slow, buggy, and when they crash, the program vanishes from the task manger but is still are running from the background, so you cannot kill it easily. Visual Studio is a crutch for real coding.

i take it your an Ed guy.

Ed is for writing scripts. Real programs are made on hand crafted punchcards.

Re: The Era of Visual Studio Code

#20
post #7

If VS Code is an endpoint to incremental improvements in text editing, then the next big thing that appears will involve a revolutionary approach.

Text editing is mostly a solved problem, and arguably done better elsewhere. VS Code makes improvements on interacting with particular languages / DSLs.
Post reply on HN