Netbeans vs visual studio
You just need to run Tasks: Configure Task Runner command and that’s it.
NETBEANS VS VISUAL STUDIO CODE
VS Code behaves a bit differently but in the end, it detects possible tasks as well. Because when you open a project in NetBeans, it tries to find the most common task runners - their config files (grunt, gulp, …) and detect possible runnable tasks what they provide.
I would really appreciate that!Įdit: I found Path Intellisense extension but it doesn’t seem to work well for RequreJS modules. But I think that it is just a matter of time when someone writes an extension for that. In fact, VS Code does not suggest anything, NetBeans suggests everything. In suggesting module paths in define() and require() functions. The project I work on uses RequireJS for modularization and that is where NetBeans is much further in Code Completion. But just for me of course, because I actually don’t use it :-) If you are used to it from your editor, you must make your own comparison -) RequireJS So the difference between Code Completion in NetBeans and VS Code is actually negligible. As I wrote before, it’s pretty hard to make a suggestion really usable for some kind of coding styles and most of the time I spent by finding the right item in Code Completion popup by pressing Up and Down back and forth. I use it heavily for Java development in NetBeans but didn’t use it much for JavaScript development. You know…writing a code and then a small popup with code suggestions appears next to the caret automatically, or by pressing e.g.
When you are used to NetBeans Theme colors, try to use NetBeans Light Theme extension for VS Code.Įveryone of us is somehow used to it. It is not possible to get 100% same experience, because theming in VS Code does not support semantic colorings, but I would say, that my NetBeans Light Theme is almost the same ans NetBeans one -) When I applied that Theme, I was like a newborn child which gets pacifier. So I decided to prepare my own NetBeans Light Theme. It should use them for same elements, etc. Yes, it uses the same colors, but it’s not the same. In fact, it doesn’t look like NetBeans coloring…at least for. So I tried to find some Custom Theme extension which would provide me same Code Coloring what I was used to from NetBeans.
I wasn’t able to scan the code effectively through my eyes. I tried them all, but I was very nervous when coding in them. Seriously! VS Code has a lot of native themes provided out of the box. I would never think that code coloring would be the biggest problem for me when switching from one editor to another. That was too much and I said ENOUGH! I already had a short term experience with Visual Studio Code editor, so gave it a chance and here are my switcher observations.
NETBEANS VS VISUAL STUDIO PRO
The latest version of NetBeans (patched 8.2) suffers from memory leaks (I think that it happens only for JS development due to parser implementation switch, didn’t notice that in other project types) and my 6 years old MacBook Pro is not able to handle that gracefully -) Yep, I was forced to restart NetBeans every hour. NetBeans for JS has a really nice coloring (well, I’m just used to it, hence I say it’s nice -), it also provides some useful items in code completion, it has a native support for Karma test runner, etc. There is nothing worse than tools which do some automatic stuff like refactoring and one can not rely on it (in the sense that it will not break your code silently). Also, there is no need for refactoring features because it’s too hard to evaluate current coding style and make such feature really reliable. In fact, that means that the editor does not need to provide anything more than just colorings and at least some code completion (which does not need to be precisely accurate, most of the time just everything could be in there). Since it has no strict type checking, then the editor must be more free. However, when it comes to JavaScript development, it’s absolutely different story. Ok, maybe IntelliJ IDEA could be a competitor in such a contest, but for me, NetBeans would win -) At first, I must say that I was a NetBeans developer for a long time and I still love it.