Why I Switched from Visual Studio Code to JetBrains WebStorm
101–110 of 163 posts
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#102When you guys think about all the developers you know, do you rather see a positive or a negative correlation between the usage of high level tools and developer productivity? In other words, is your experience that developers who use an IDE are more productive then developers who only use a text editor? In my experience, the (very few) developers I know who only use VIM or Emacs are way more productive then those wh…
I believe at least for Emacs people use it because it's an interactive environment like Slime. With this kind of interactiveness, I can think by playing with the code. Just like sketching with a pencil instead of a pen.
Most of the time 'sit back and think' doesn't work because if your business model is dynamic you have to break your existing design and refactor, unless you are just solving a problem in a small generic domain. At least for OO languages. That's something IDEs are used for.
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#103When you guys think about all the developers you know, do you rather see a positive or a negative correlation between the usage of high level tools and developer productivity? In other words, is your experience that developers who use an IDE are more productive then developers who only use a text editor? In my experience, the (very few) developers I know who only use VIM or Emacs are way more productive then those wh…
This should not pass code review. If it doesn't have tests then it's a landmine for other programmers in the future, since they can break it without realising - possibly entirely indirectly, such as through a library change.
The most "productive" techniques I've seen are all metaprogramming - assemble something which matches the domain well and use that to produce a large volume of code from specification-as-data.
(Oddly, the only area where nobody bothers to do automated integration testing in my experience is embedded code, possibly because it's too hard to set up)
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#104I would like to try to switch to a JetBrains IDE. Especially the refactoring tools look to be much more advanced then Atom or VSCode. At my workplace, most developers are either full stack or backend (python). As such, we have a grab bag of PyCharm licenses. However, I am purely a frontend developer, so frontend related tools are much more important to me then python support. Unfortunately, the last time I tried PyCh…
The language specific apps (pycharm, rubymine?, phpstorm, webstorm) can’t run most other language plugins. Get IDEA ultimate (also jetbrains) and just install the language plugins you need. I use this to write php, shell, sql, javascript, css, html, a little ruby, a little python, makefiles, and hopefully some D-Lang soon.
Isn't IDEA to Java what PyCharm is to Python?
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#105Earlier quoted context omitted.
> lag issues & the clutter interface of Webstorm I know a few developers who stick to editors like VSCode for those kind of reasons, but as it turns out, they actually never spent time learning how WebStorm works. WebStorm and the rest of the JetBrains family of IDEs are extremely configurable, and speed is not an issue in my opinion: I've spent a lot of time programming with PHPStorm (including database servers and…
> WebStorm and the rest of the JetBrains family of IDEs are extremely configurable, and speed is not an issue in my opinion Speed is totally an issue for me with Webstorm, there's a small typing lag, very small yeah but noticeable, no typing lag is my top priority in an editor, above all the other features. > Looking at them work, they could save so much time refactoring, jumping between code, clicking instead of usi…
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#106Maybe people should realize that the problem is with the JS libraries ecosystem and how most are build in a way that "just jumping into a lib/framework to read its code and see what it does" can't seam to be feasible anymore . For example, in a React app if I'd want to jump from a `Route` import from react-router to it's readable code definition [1], NO IDE or editor around is capable a properly doing the jump, I eit…
I'm not sure if this is positive or negative. But somehow more or less encouraged JavaScript community move towards: 1. Minimal interfaces 2. Better documentation Say like React although the codebase is more or less difficult to read. But the most useful surface-level APIs are quite minimal and intuitive. There are more minimal libraries follow this pattern. And for the documentation -- probably because of the minima…
(But jokes aside, yeah, you're right, there's lots of JS libs with much nicer interfaces and docs than Python ones, I agree...)
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#107For most of the functionalities, I think WebStorm still won. But VSCode typescript completion is great. WebStorm typescript completion is somewhat strange.
However, the mindset of WebStorm follows IntelliJ, of course. You cannot switch projects or single file as simple as code editors. Although it can be achieved but it still feels weird. IntelliJ is constantly trying to improve this like scratches, but it will be still different from code editors.
And something off topic, I found IntelliJ/WebStorm is pretty much following Emacs for a lot of features. Like the VSC system is very alike Magit and they deprecated their RestClient and use an editor-based approach just like Emacs RestClient, or simply scratches. Seems a very good strategy to copy from Emacs community at least for MVP.
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#108When you guys think about all the developers you know, do you rather see a positive or a negative correlation between the usage of high level tools and developer productivity? In other words, is your experience that developers who use an IDE are more productive then developers who only use a text editor? In my experience, the (very few) developers I know who only use VIM or Emacs are way more productive then those wh…
But on the bigger issue, correlation is not causation.
Many new developers start with an IDE because. So you’ll see a lot of inexperienced developers using an IDE. On the other hand, back in the day, if I wanted to have any chance of editing this file on the arse end of a 9600baud dumb terminal then vi is the answer. So there are old bastards still programming, who therefore have a ton of experience, who use vim.
Does using vim make you a good coder? Fuck no. Does using an IDE make you a bad coder. Also no.
I use an IDE. I’ve used an IDE since ‘92. Then it was slick edit on OS/2, at a company working on some of the hard bits of supermarket system, and everyone used it. One of the best programmers I know uses vim. However every other best programmer I know uses an IDE. I suspect the vim guy is wired differently. So if vim seems right to you then use it. If an IDE works then use that. Anyone tells you you aren’t a proper coder unless you use vim or emacs or edlin then they are telling you that they are a pretentious twat. My friend who uses vim will not tell you to use vim. He’ll tell you why he likes it.
But write fucking tests.
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#109Earlier quoted context omitted.
The language specific apps (pycharm, rubymine?, phpstorm, webstorm) can’t run most other language plugins. Get IDEA ultimate (also jetbrains) and just install the language plugins you need. I use this to write php, shell, sql, javascript, css, html, a little ruby, a little python, makefiles, and hopefully some D-Lang soon.
> language specific apps Isn't IDEA to Java what PyCharm is to Python?
Re: Why I Switched from Visual Studio Code to JetBrains WebStorm
#110When you guys think about all the developers you know, do you rather see a positive or a negative correlation between the usage of high level tools and developer productivity? In other words, is your experience that developers who use an IDE are more productive then developers who only use a text editor? In my experience, the (very few) developers I know who only use VIM or Emacs are way more productive then those wh…
1. That depends on the developer 2. Dev's who use VIM/Emacs are probably already living in their computer so you can't really say if they are good because of the editor they use or the other way round 3. What do you mean by "productive"? Closing more tickets in a sprint? In the end not only individual efficiency is important but also the future of a project. With test you document stuff and ensure at least the tested…
I sometimes open VS Code for small for small non-project related files, but I am much more productive with an IDE.
One thing that many get wrong in the VIM vs IDE comparisons are the benefits of keyboard shortcuts. They assume that VIM has a significant advantage, but you can have that with IDEs too.
The JetBrains products have keyboard shortcuts for almost anything, so you do not have to use a mouse unless you want to. I'm sure the same could be said about other IDEs as well. Many forget that when they compare against VIM.