Does the mac launcher work if you primarily use python 3 now?
Visual Studio Code 1.0
71–80 of 487 posts
Re: Visual Studio Code 1.0
#72I still have the CD-ROM from visual C++ 6.0, is that better than this? (service pack 1)
Re: Visual Studio Code 1.0
#73VSCode has done the thing that nobody expected MS to do, change the way code was written on Unix/Linux. I love linux/unix, but the problem always was with the lack of an awesome text editor cum IDE, yep there is eclipse but it is too clunky, I do not like sublime as it isn't FOSS (call me crazy), gedit took way too much memory, geany is fast and mean but the UI sucks plus functionality isn't that great. Enter VSCode,…
> gedit took way too much memory
Can you elaborate?
Re: Visual Studio Code 1.0
#74Well we know what happens to vStudio and WPF now, don't we?
Yes, from these presentations 13 days ago:
The Future of Visual Studio (https://channel9.msdn.com/Events/Build/2016/B859)
Building Desktop Apps in Visual Studio vNext (https://channel9.msdn.com/Events/Build/2016/B824)
Re: Visual Studio Code 1.0
#75Earlier quoted context omitted.
Atom was around before VSCode and they feel roughly equivalent to me, no? They're both web browser based even... I'm a heavy IDE and Emacs guy though, so perhaps I'm missing something.
> Atom was around before VSCode Nope. Visual Studio Code was created before Atom.[1] Although both VS Code and Atom are based on Electron[1] and are both Chrome-based. VS Code does seem to be stealing Atom's thunder as what they say [1] [1] https://discuss.atom.io/t/atom-seems-to-be-lossing-contribut...
https://en.wikipedia.org/wiki/Atom_%28text_editor%29
Atom = 2014
https://en.wikipedia.org/wiki/Visual_Studio_Code
VSCode = 2015
Am I missing something? Sure, MS had some preview online IDE thing before VSCode came out, but that's not the same thing obviously.
Re: Visual Studio Code 1.0
#76I've been writing OCaml for a while and seeing that VSCode has a pretty sweet integration for F# gets me quite excited. Is there anyone here who's running F# on Linux / OSX and can share their thoughts?
Re: Visual Studio Code 1.0
#77Earlier quoted context omitted.
Can I ask what you'd be looking for out of a new editor that Vim doesn't already do for you? Hard to see the point of this comment.
Not suck at plugin management
Have you tried Vim 8? One of the major updates is plugin package management. Can't say much about it, haven't upgraded yet, but the write up on it looks promising.
Re: Visual Studio Code 1.0
#78VSCode has done the thing that nobody expected MS to do, change the way code was written on Unix/Linux. I love linux/unix, but the problem always was with the lack of an awesome text editor cum IDE, yep there is eclipse but it is too clunky, I do not like sublime as it isn't FOSS (call me crazy), gedit took way too much memory, geany is fast and mean but the UI sucks plus functionality isn't that great. Enter VSCode,…
> but for the people like me who don't or can't use terminal based editors, VSCode is quite literally the best.
Sure, if you find fault with and don't use the 14 other options, the one you're left is, quite literally, the best.
Re: Visual Studio Code 1.0
#79I use it for Typescript development exclusively. Obviously it works quite well.
Can you talk about how you use it?
Re: Visual Studio Code 1.0
#80Earlier quoted context omitted.
But you shouldn't need high end hardware to run a text editor.
It's interesting how people seem to have very different experiences with lag on vscode. I wonder if it's actually much more laggy on some system configurations. What are your running it on?
I've noticed that VSCode + the JSX plugin, when run concurrently with webpack in watch mode, cause my machine to thrash. Working theory is that they are both watching the large node_modules folder, but yet to confirm.