301–310 of 312 posts
Earlier quoted context omitted.
There is a way to set VScode to use the native menu bar on macOS instead of the Electron'd frameless bar.
Enabling that system-wide made the experience so much more pleasant: "window.titleBarStyle": "native",
I have a new project at work that I decided to use it for to see how I liked using VS Code. For the most part, I like it, but it's lack of Mac-nativeness bugs me, and it may bug me enough to switch. Double clicking the window bar in all natives app minimizes them to the dock for me. In Visual Studio, it maximizes my window (but not into full screen mode). I keep clicking the menu bar to minimize a window, and this ke…
I never minimize anything on Mac, the concept is not so useful since there's nothing interesting on the "desktop" anyway.
Earlier quoted context omitted.
PowerShell needs the .Net runtime so I doubt it will ever be on a par with cmd.exe.
cmd.exe has a limited set of builtin and relies on external applications with a plain text interface. PowerShell has builtins, can import code from any .NET Assembly or native code DLL, invoke external processes, full featured programming language and structured data. cmd.exe will never be on par with PowerShell.
Earlier quoted context omitted.
Na, I think the real plan starting to unfold. This week we get the new welcome screen, next will be the "deploy to Azure" and "how to make a Windows Store App" sidebar links. (not that I'll stop using it, I'm sure someone will fork if gets too obnoxious)
Wow that is a scary vision and it would be heartbreaking if they rendered it unusable with ads or other nagging "features".
My guess is that they will up-sell to a version with bundled plugins which offer turnkey integration with Azure.
Earlier quoted context omitted.
VS Code is a web dev IDE. Microsoft has lost the mobile platform wars and pushing the web is a way of countering that. Plus, web and azure do go hand-in-hand, as you point out.
Nothing in VS Code is terribly web specific. I've been using it for C++ for which it works swimmingly.
Another great release! Maybe I'm just squarely within the target audience of VSCode, but I'm consistently impressed by how many of my pain points just magically go away with each new iteration.
I come from WebStorm, Sublime and Atom. Atom and WebStorm felt rather clunky. Sublime was super fast, but somehow lacked behind in new features. VSCode is a revelation for me :)
---
I am a very happy Jetbrains customer (ultimate, paid in full).
Now doing nodejs work. (Not a fan, it's just a job.) Really want to use latest, greatest (eg await/async). I tried to make the babel plugin workflow thingie work. Bleh.
I'll give VSCode another shot. Last effort, I stumbled on the npm package.json support. The npm plugins I tried baffled me. (Again, not a fan of npm, it's just a job.)
This version introduced a non-trivial bug for me; When I open a file to edit through nautilus, it opens in a new window instead of reusing the existing one. The new settings ( window.openFilesInNewWindow and window.openFoldersInNewWindow ) don't help no matter what when I set them to 'off' EDIT: Fixed it on Ubuntu by removing the '--new-window-if-not-first' argument from the code.desktop related command. sudo nano /u…
This version introduced a non-trivial bug for me; When I open a file to edit through nautilus, it opens in a new window instead of reusing the existing one. The new settings ( window.openFilesInNewWindow and window.openFoldersInNewWindow ) don't help no matter what when I set them to 'off' EDIT: Fixed it on Ubuntu by removing the '--new-window-if-not-first' argument from the code.desktop related command. sudo nano /u…