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

VS Code Roadmap 2018

github.com

Post reply on HN
Print view View original

201–210 of 236 posts

Re: VS Code Roadmap 2018

#201

Post by ZenoArrow »

slededit wrote: post #183
WorldMaker wrote: post #155

Earlier quoted context omitted.

> what's the business model behind it's development. I'm too much of a skeptic to believe it's just so developers have a warm fuzzy feeling associated with Microsoft There are a couple things others touch on, but to expand on a few things: 1. Microsoft was formed for developers in the first place. It's first product was BASIC (for MOS 6502). Developer productivity has always been a part of Microsoft's long term visio…

Minor correction, the first BASIC was for the MITS Altair 8800 which had an Intel 8080 CPU.

Minor correction, the first BASIC was for the GE-235. The Altair was the first home computer to have a version of BASIC, but BASIC had already been around for a decade before it was ported over.

https://en.m.wikipedia.org/wiki/GE-200_series

https://en.m.wikipedia.org/wiki/BASIC

Re: VS Code Roadmap 2018

#202

Post by chillee »

Tehnix wrote: post #186
chillee wrote: post #171

Earlier quoted context omitted.

I suspect what you're running into is some kind of crash when running a command. I will say that I don't think we're doing a very good job handling errors, and I suspect it's that most users don't report them (they just press and it goes back to normal). For example, this: https://github.com/VSCodeVim/Vim/pull/2087 Either way, if you're ever interested in heading back to VSCode and felt disappointed in the Vim mode,…

Ah, that would certainly make sense. Is there any logging anywhere when such a thing occurs so one could help dissect the issue?

If you try opening up dev tools when that happens, it's likely the issue will pop up.

Honestly, there's several places that from an engineering quality standpoint bother me quite a bit. Performance on rapidly repeated actions is one. We have a couple race conditions too. A bunch of inproperly handled errors is another.

However, most of these don't really impact most users most of the time. If you're using vim, you're probably not holding down `dd` or rapidly typing actions one after a while. Similarly, as errors are separated into their own action and are captured at the top level, hitting escape is usually enough to get you back to a usable state.

Re: VS Code Roadmap 2018

#203

Post by veidr »

mikewhy wrote: post #196
and0 wrote: post #187

Earlier quoted context omitted.

SSB?

"Single-site browser", or "site specific browser". Basically a very thin wrapper over the systems web view.

Me, too. For instance, I use a site-specific browser for:

- CircleCI

- GitHub

- JIRA (blecch, but I have to use it...)

- AWS

- Google Docs (for work, and the rare personal use of Google stuff can just happen in one of the general browsers I am using)

...and others.

The OS does a much better job of partitioning windows and groups of windows than a browser typically does. You can easily keep switch between groups of windows, or keep them in their own workspace/desktop, etc.

Plus you can keep your cookies and saved passwords isolated between the environments... the browser handling AWS doesn't need to store or have access to the pasword for my Google account, and so on. For production type apps you can disable saved passwords entirely.

It is incredibly useful, and the only thing I worry about is that on macOS (my main workstation OS) there is only one good solution for this I know of: Epichrome, which seems to be a one-man side project:

https://github.com/dmarmor/epichrome

Other solutions that I know of don't save passwords, or don't keep password/cookie stores separated between the browser instances.

(I think Chrome can do this by itself on other platforms.)

Re: VS Code Roadmap 2018

#204

Post by slededit »

ZenoArrow wrote: post #201
slededit wrote: post #183

Earlier quoted context omitted.

Minor correction, the first BASIC was for the MITS Altair 8800 which had an Intel 8080 CPU.

Minor correction, the first BASIC was for the GE-235. The Altair was the first home computer to have a version of BASIC, but BASIC had already been around for a decade before it was ported over. https://en.m.wikipedia.org/wiki/GE-200_series https://en.m.wikipedia.org/wiki/BASIC

Meant the first MS Basic :)

Re: VS Code Roadmap 2018

#205

Post by Rondom »

sjellis wrote: post #29
dingo_bat wrote: post #24

Earlier quoted context omitted.

This speaks more about enterprise "packaging process". Why can't they let the devs manage their own machines? This is one big reason devs love Macbooks, because OSX just doesn't allow the employer to fuck around with the machine a lot.

"Why can't they let the devs manage their own machines?" Part of the problem is that then the devs aren't actually managing the systems, they are blindly trusting the vendors. To a large extent, (re)packaging is make-work that should not need to happen, but it does provide a kind of safety fuse. In the event that a vendor breaks something or worse, unilaterally decides to change the product, organizations needs to be…

Well, I do appreciate the service that distributions do. In Debian everything has a manpage, even if upstream does not provide one and things install into the right directories and integrate into the system well.

If for instance Chromium adds some phone home functionality, I trust that it will be patched out...

The homebrew debacle has shown me that today's "open source" developers don't care about their user's privacy.

Re: VS Code Roadmap 2018

#206

Post by rvern »

moomin wrote: post #18

I’d love to see more IDEs try to address the issue of Spellcheck in code editors. Currently, you can do it by writing your own spell checker and embedding it in your language server, but this is a recipe for repeated work and inconsistent user interfaces.

GNOME Builder uses gspell: https://wiki.gnome.org/Projects/gspell.

Re: VS Code Roadmap 2018

#207

Post by spinningarrow »

merlish wrote: post #129
spinningarrow wrote: post #7

Earlier quoted context omitted.

I don’t think Electron is entirely to blame e.g. I tried the Discord app and it was amazingly snappy (just install both Slack and Discord and you can feel the difference).

I actually really want to know how Discord does it. Do they actually use the DOM, or just draw everything themselves? Honestly, anyone who hasn't used Discord, I'd recommend installing it just to try it, especially if you're a SPA web developer or you work with Electron. The performance beats native apps, even dealing with very long sections of text that need to be swapped in and out as you scroll. However they're do…

> I actually really want to know how Discord does it.

I tried asking them on Twitter and the reply was ‘magic’.

Re: VS Code Roadmap 2018

#208

Post by saosebastiao »

balefrost wrote: post #89
Vinnl wrote: post #79

Earlier quoted context omitted.

> some don't like the electron-based thing/performance It's mostly not liking Electron-based, performance is very reasonable for VSCode, I think. As for the end-game: it's most likely luring you into Azure. Tight integration with a proper editor/IDE might give it an edge over competitors.

One very specific performance metric is startup time, and Sublime beats the pants off VSCode in that department. Creating new top-level windows in VSCode is also annoyingly slow compared to Sublime (presumably because it's spinning up a new browser context). Other than that, it seems snappy enough.

Never tried Sublime (it sounds fantastic), but VSCode is lightning fast compared to the other IDEs I currently use or have used in the past: Eclipse, IntelliJ, Visual Studio, and MonoDevelop.

IntelliJ is probably the most annoying...it takes less time than VS does, but during the 2 minutes it takes to start it hijacks the OS window focus at least 5 times. I like to actually work on other things while waiting for that beast to start up and it constantly screws everything up.

Re: VS Code Roadmap 2018

#209

Post by tmzt »

Sir_Cmpwn wrote: post #128
metamet wrote: post #125

Earlier quoted context omitted.

Were you using Mono or .NET Core/Standard?

Both at different times. My Mono projects started breaking and getting .NET Core/Standard running on anything but their blessed distros is difficult.

There are supported Docker (Linux) containers which can be used as is or extracted and come with needed libraries.

Re: VS Code Roadmap 2018

#210

Post by Sir_Cmpwn »

tmzt wrote: post #209
Sir_Cmpwn wrote: post #128

Earlier quoted context omitted.

Both at different times. My Mono projects started breaking and getting .NET Core/Standard running on anything but their blessed distros is difficult.

There are supported Docker (Linux) containers which can be used as is or extracted and come with needed libraries.

That doesn't count, not even a little bit.
Post reply on HN