4 ms·
The only bad part about Jetbrains is that no matter how much i've tried i can't use a text editor without feeling crippled. A big factor is probably that I sta
by spdionis 11y ago
The only bad part about Jetbrains is that no matter how much i've tried i can't use a text editor without feeling crippled.
A big factor is probably that I started programming using Jetbrains tools (except some c++ in codeblocks before that). It's so awesome everything else just sucks.
The problem is when i want to try some language that is not well supported by IntelliJ. No matter how cool the language is i get frustrated by editors like sublime/atom/emacs.
- noir_lord 11y agoI know what you mean, I started programming back in the 80's as a kid so I spent about a decade without anything that looks like a modern IDE and since then I've used nothing but IDE's, I can live without an IDE but I seldom want to, it just suits my programming style.
- spdionis 11y agoMost importantly I always miss "Go to definition" that usually doesn't work (well?) in editors. Also in javascript. The exploratory power that comes with that is also incredible. I don't need to read your damn docs (unless the module is heavyweight and needs studying), I just want to be sure I called your mehod with the arguments in the correct order ffs!!
- hit8run 11y ago"Go to definition" works great in vscode. I tried it with golang and it also has the feature to show definitions inline :)