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

Visual Studio Code 1.5

code.visualstudio.com

Post reply on HN
Print view View original

131–140 of 270 posts

Re: Visual Studio Code 1.5

#131

Post by labrador »

RussianCow wrote: post #28
Touche wrote: post #20

Earlier quoted context omitted.

Xamarin doesn't support the platform the editor was originally written for: the web.

Not super relevant to the topic, but what's with Xamarin not supporting what is arguably the most important platform? This seems like a huge weakness, especially when you can now build a React app that renders natively on web and mobile thanks to React Native.

My impression is that Xamarin is designed to suck dollars out of corporate enterprise users who need to do something with mobile devices and can pay big bucks for Xamarin because it allows their C# devs to make a mobile app in short order. It saves them in the long run.

Re: Visual Studio Code 1.5

#132

Post by mythz »

Brakenshire wrote: post #118
renke1 wrote: post #113

Earlier quoted context omitted.

React may not have "native" support for TypeScript, but in combination with TypeScript using React is so much more fun, if only for the fact that your props can actually be typed and checked at compile time.

The standard recommendation seems to be to use PropTypes. And also in general, to use Babel with React programs. Would be interested to hear experiences of using Typescript with React.

Using React, Redux, JSPM, TypeScript work great together in VS.NET, it compiles on save so you don't need to run any additional watchers and JSPM's bundle feature means you also don't need Babel. Since ES6 support is VS.NET is very weak, using TypeScript is the best way to use the latest ES6/TypeScript features today:

https://github.com/ServiceStackApps/typescript-redux

Re: Visual Studio Code 1.5

#133

Post by nix0n »

carussell wrote: post #30

It's unfortunate to see that the group who named their extension "Vim" is being recognized as more or less the official recommendation for Vim emulation, despite being not so good. The last time that I did a survey of feature completeness, performance, and code quality, the author of the amVim extension had a much better showing across the board--and more active involvement in VSCode extension APIs themselves. Percep…

> the author of the amVim extension

i.e. you? https://gitlab.com/crussell/amVim

Re: Visual Studio Code 1.5

#134

Post by sunnyps »

JonnieCache wrote: post #123
plexicle wrote: post #14

Opening a newly cloned Chromium repository in ~3s is very impressive to be honest.

I was about to try one of these fancy new browser based editors again, but now I'm confused. Shouldn't opening a directory be O(1)? I just opened the chromium trunk in sublime and it took 0.2 seconds, regardless of whether it was currently running or not. Why would one ever use a text editor that has perceptible latency when doing everyday tasks? 3 seconds isn't even latency, it's a freeze tbh.

I don't think being "browser based" as the reason that opening a directory is slow. A lot of traditional IDEs (cough Visual Studio cough) also have similar problems. I think they're doing a bunch of work (e.g. caching all subdirectories and files) but aren't doing it concurrently with the UI.

Re: Visual Studio Code 1.5

#135

Post by kim0 »

RedCrowbar wrote: post #82

Worth mentioning that in this release TextMate Python bundle was replaced with MagicPython [1] for much improved Python code tokenization. [2] [1] https://github.com/MagicStack/MagicPython [2] https://github.com/Microsoft/vscode/commit/f4967722fa02471da...

Do I need to do anything to be upgraded to magic python? Thanks!

Re: Visual Studio Code 1.5

#136

Post by detaro »

nix0n wrote: post #133
carussell wrote: post #30

It's unfortunate to see that the group who named their extension "Vim" is being recognized as more or less the official recommendation for Vim emulation, despite being not so good. The last time that I did a survey of feature completeness, performance, and code quality, the author of the amVim extension had a much better showing across the board--and more active involvement in VSCode extension APIs themselves. Percep…

> the author of the amVim extension i.e. you? https://gitlab.com/crussell/amVim

Just because he has a fork of the code under his username doesn't make him the author. The original repo is clearly linked on the page. And the vast majority of commits seem to be by somebody else. Does not look like the author to me.

Re: Visual Studio Code 1.5

#137

Post by rebornix »

alfanick wrote: post #52
johnfn wrote: post #47

Earlier quoted context omitted.

Ah, you should definitely join in on our Slack. Another guy has done some similar work in a plugin: https://github.com/extr0py/vscode-relative-line-numbers

yeah, that's the extension that inspired me ;)

The reason that plugin lags is because it was using `setInterval` initially but I changed it to selectionChange hook and now it works smoothly. Now the only problem with it is it hides breakpoints but definitely we will improve this experience later on. / I'm a Code team member*/

Re: Visual Studio Code 1.5

#138

Post by Tyriar »

ralusek wrote: post #126

I love VS Code, but I'm getting a little disheartened after bringing this up almost every release. Is there a plan to improve the syntax highlighting? I know there are custom themes, etc, but they all seem to have the same elements available to them. The JS syntax highlighting can't distinguish between properties and variables, or properties that are functions, or object literal keys. It's almost there, but it's lack…

We packaged up Atom's JavaScript grammar into an extension which is probably just what you're looking for https://marketplace.visualstudio.com/items?itemName=ms-vscod...

Re: Visual Studio Code 1.5

#139

Post by DougN7 »

labrador wrote: post #129
mixedCase wrote: post #68

Earlier quoted context omitted.

VSCode is open source software. WebStorm isn't. I love JetBrains IDEs but I sure as hell prefer using tools that I can fix or modify myself.

I had one of those aha moments last week. I started to write to complain to Microsoft that VSCode didn't remember my previous searches when I remembered that I could just hack it in myself, which I did. Most programmers like me like that kind of control.

Honest question as I'm not really part of the open source world: 1. What happens to your change when an update comes out? (Or, do you keep up with updates) 2. Having just merged my first ever pull request, how does a project stay coherent with possibly hundreds or thousands of people submitting their 'hacks'?

Re: Visual Studio Code 1.5

#140

Post by Tyriar »

biot wrote: post #130
ralusek wrote: post #126

I love VS Code, but I'm getting a little disheartened after bringing this up almost every release. Is there a plan to improve the syntax highlighting? I know there are custom themes, etc, but they all seem to have the same elements available to them. The JS syntax highlighting can't distinguish between properties and variables, or properties that are functions, or object literal keys. It's almost there, but it's lack…

It's open source. Make the change and use it yourself, then submit as a pull request. [edit: link removed; see Tyriar's reply for correct repo]

This is the source repo for both JS and TS grammars https://github.com/Microsoft/TypeScript-TmLanguage
Post reply on HN