91–100 of 197 posts
Finally, we get hot exit. :)
Isn't just better to enable autosave? (VS Code has that as well). I learned its usefulness from PHPStorm, where it is switched on by default. So I just not explicitly save anymore, it is done automatically and immediately.
Maybe there's some config I'm unaware of, since VSCode's site does mention "words" as a type of completion, but I've never seen it work for js files.
I recently moved from EMACS (after using it for ~10 years & ~6 languages) to VSCode. There are loads of things that I miss but overall it's been a fairly smooth transition. I'm moving because I spend most of my time writing javascript and felt that no combination of emacs modes allowed me to keep up with a proper IDE. Emacs is a tool to learn once and use for a lifetime (and I will continue to use it for other editin…
Anyone using Visual Studio Code for Rust development? If so, how is it? https://areweideyet.com/ Going by feature set alone (plugins included) it appears like a good choice, though I've yet to try it myself.
Racer (intelligent auto complete) has always been a bit flaky, but other than that it's been great.
Why are people using this instead of WebStorm? It seems like: - It a little faster for Typescript (but no better TS features from what I can see). - A lot of people are trying it because it's new, or because they like MS tools. - It's free On the other hand WebStorm still has more functionality overall, a few less rough edges, and a more standard UI (some people don't like how MS Code doesn't have a tabbed doc UI). M…
VS Code has had tabs for over half a year now, since the 1.3 release in June. Beforehand, the "active documents" acted more or less as nerfed tabs, but I agree the real tab support was desperately needed before 1.3.
> they have been pushing out features very fast for years now.
WebStorm gets major updates 2-3 times a year, VS Code gets major updates 12 times a year. I'm pretty sure you can't really call WebStorm "very fast" on that front given that metric.
I've never used WebStorm so I can't really comment on the other points, but you're also being very vague. What are some examples of more functionality and less rough edges?
Anybody know how many people are on the VSCode team? They're moving so fast in adding useful stuff with very few hiccups...I'm lovin' it.
Earlier quoted context omitted.
I am pretty to the javascript/node world. The debugging situation is pretty pathetic in my view. Most people I know use a ton of logging like we did with C/printf 25 years ago.
Using awareness of how to use a debugger is a reasonable interview technique WRT javascript devs. In general, ignorance is not a pejorative but if a candidate walk into an interview claiming to be an expert and I find out that you debug in anger using console log, I'm calling bullshit. They're either very green or too lazy to have investigated the tools available. Jr devs are, obviously, another story. Read up on how…
Why are people using this instead of WebStorm? It seems like: - It a little faster for Typescript (but no better TS features from what I can see). - A lot of people are trying it because it's new, or because they like MS tools. - It's free On the other hand WebStorm still has more functionality overall, a few less rough edges, and a more standard UI (some people don't like how MS Code doesn't have a tabbed doc UI). M…
From my experience, I would just add that while WebStorm is indeed far more powerful in terms of features that it has, it:
- is actually slower even than VS Code for many operations (both of which are, when compared to a native editor like Sublime or TextMate 2, objectively slowww at basic operations like launching and opening windows)
- it comes with a shopsack full of shit enabled by default, that most people will need to scale back, adjust, or turn off before getting productive. E.g., on the Mac, all the text editing keyboard shortcuts are wrong, drag and drop doesn't work like any other app, some windows can only be docked or floating windows (wtf!) and can't be put in the background, and all sorts of spurious code-linting and annoying popup suggestions are enabled by default. It's the UI equivalent of somebody shouting all sorts of commands and suggestions at you, while when you first open VSCode its a fairly minimal rectangle of text that you can work with right away and gradually learn the advanced features when you are ready to.
So one answer to "why people use this instead of WebStorm" is probably that, especially on Mac, many people's first response to WebStorm is to groan "bleeeccch! yuck!" and close the window and drag the app to the trash.
(I did that a few times, too, but in the end the WebStorm the code completion and intelligent navigation was so much better than anything else that I decided to endure the UI atrocities and stick with it.)