131–140 of 163 posts
For web work I use VS Code because it has the best plugins for Vue, React, etc. I would also use it for less popular languages.
When 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 only use Vim, currently inside WebStorm. From my anecdotal experience, people who are willing to learn vim/emacs are also willing to learn a lot more about the whole programming experience, tools and theory. They usually are more productive, but I don't think it's vim that's making them productive, it's the other way around usually.
Fast forward a few years on that job, I'm finding myself utilizing a workflow that's tracking closely to ESR's TAoUP. I still have to lean on the IDEs for certain classes of problems that I might come across, but they became a tool in my toolbox instead of being the toolbox.
That was all well over a decade ago. I haven't touched an IDE in my full-time work since 2013 or 2014, when I wrote my last line of C#. If I had to go back, I'm glad that VsCode has appeared on the scene in the meantime, but I wouldn't be thrilled about it.
My personal opinion is that living at the layer that I live at, in a terminal with a multiplexer and doing things that leans heavily the UNIX philosophy, gives me an understanding of the systems that I create that I perhaps wouldn't get otherwise.
I can understand that people may perceive VS Code and WebStorm as alternatives. Though, as rightly pointed out by the author, the former is an editor while the latter is an IDE. The whole post just says that in 10 different redundant ways.
You can debug inside VSCode. That is an IDE. Practically by definition. A text editor is Sublime text.
The key factor for me, is the ability for the tool to understand the codebase at some level. It needs to be able to tell me where a symbol is used, let me refactor that symbol (e.g. adding a new mandatory argument, or changing the argument order, or renaming the symbol) with as little extra work from me as possible.
Jetbrains tools allow me to do all of that (in PHP at least. I write about as much JS as I eat mud) where no others I've seen do.
I use IntelliJ IDEs for statically typed languages (and Ruby/Rails), the refactoring/ navigation is top notch and search is super quick. For web work I use VS Code because it has the best plugins for Vue, React, etc. I would also use it for less popular languages.
Earlier quoted context omitted.
* Find usages * Go to definition * Extract method * Introduce parameter * Inline variable * Rename method * Rename variable In a Jetbrains tool these are automatic / atomic operations.
All of these can be done in emacs/vim as well for most of languages. None of the above is modern by any standard.
Or have a go at https://github.com/daviddenton/refactoring-golf
Very biased article and by the way, tslint will also warns you if you don't use promise: https://palantir.github.io/tslint/rules/no-floating-promises...
FYI TSLint still has a large amount of config required to get it working, and the vscode integration still has a "wont-fix, upstream" bug where it won't lint files unless they are open in the editor. So you need to manually run tslint from the commandline. See: https://github.com/Microsoft/vscode-typescript-tslint-plugin...
I'm guessing that webstorm does this this more auto-magically for the user.
When 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…
> do you rather see a positive or a negative correlation between the usage of high level tools and developer productivity? Absolutely none whatsoever. If anything it's negative. I have never found "speed of editing" to be remotely correlated with good code or even productivity.
Earlier quoted context omitted.
> do you rather see a positive or a negative correlation between the usage of high level tools and developer productivity? Absolutely none whatsoever. If anything it's negative. I have never found "speed of editing" to be remotely correlated with good code or even productivity.
most people here aren't talking about speed of editing, but rather speed of code navigation. That way it's easier to figure out what's going on in larger codebases, or one even just one you're not familiar with.
Maybe 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…
It's been bugging me for a while now as I can't find the video but the Vs code team made a demo where they were able to jump to a dependencies source code on github inside the editor. Looked pretty amazing and would definitely solve the problems you mentioned.
https://github.com/Microsoft/TypeScript/wiki/What's-new-in-T...
Jumping to definition works with typescript projects correctly when this is turned on, but it's still not a solution for JS projects with definition files