231–240 of 389 posts
Earlier quoted context omitted.
That sounds more like a problem with git than a problem with the IDE. Why does git allow you to screw up your repository?
Bacause git is powerful
The author seems to use IDE for one purpose only: to auto-generate boilerplate code. But this is far from the only benefits of IDEs! I rarely use IDEs for code generation, I don't even like autocomplete. For this stuff I use code snippets; I develop collections of those for any language I use. You don't need an IDE for it; any good text editor has such features. For me really important features of a good IDE are: - N…
There are languages and environments that are more prone to requiring IDEs. For example, when I write React and I use the Foo component, either it is defined on the same file or it is in one of the imports. On the other hand, with Angular, the foo component is not imported anywhere. In fact, there is no foo component, just one or many Foo components which declare to use the foo tag, and one or another may be loaded d…
There's always the option of not working with such obfuscated environments. I know I don't.
A good ide is all about auto completion and refactoring tools. The autocompletion means you don’t have to spend as much time memorizing apis, so you can focus more on simplifying your design and minimizing coupling. In something like unreal engine, the intellisense really sets ides apart. The refactoring means you can quickly and easily make large changes to make the code easier to work in. You can just work signific…
I'm surprised how many of my colleagues don't use the debugging features of their IDE. Being able to step through code line by line and see all the variables states at any time and evaluate arbitrary expressions given those states seems far superior to print/console based guesstimation. However, somehow my colleagues still do great work!
Sure, in some settings the source code is not available and you still want to debug. Then I use debuggers. But outside of that I prefer printf debugging.
Note that I'm not saying that people who prefer debuggers are wrong. They probably have their reasons, as I have. Everyone should be allowed to use the method they prefer the most.
Earlier quoted context omitted.
The best developers I've found are the ones who know how to work without an IDE, even if their preference is to use one. Contrastingly, the worst, slowest developers I've worked with rely on their IDE without understanding what it's doing for them, and are helpless in new/unsupported situations. They also, 100% of the time, screw up their git repositories on a regular basis, and need someone who knows what they're do…
The thing I hate most about IDEs is when they insinuate themselves into a project's development workflow so deeply that you can't make do without them. Do I have to spin up a whole session of the IDE just to run my test suite? Do I have to dig through eleven nested GUI settings dialogues to find out what the command to build the damn project is, just so I can tweak a build parameter? Is there so much boilerplate or X…
Isn't this the case with Android Studio? Is it even possible to do Android development without Android Studio?
Earlier quoted context omitted.
Power drills are simple tools, they are the 'vi' equivalent of the 'ed' manual drill. The physical equivalent of an IDE would be a laser-guided auto-centering/levelling drill with automatic drill bit changer/sharpener, depth guide, dust evacuation and material sensor with automatic lookup for which hole size and depth to use for the given task. It would weigh 15 kg, need an external power pack and be unusable in tigh…
I think you mean cnc machine. And those are amazingly productive.
Earlier quoted context omitted.
The thing I hate most about IDEs is when they insinuate themselves into a project's development workflow so deeply that you can't make do without them. Do I have to spin up a whole session of the IDE just to run my test suite? Do I have to dig through eleven nested GUI settings dialogues to find out what the command to build the damn project is, just so I can tweak a build parameter? Is there so much boilerplate or X…
>An IDE can be a powerful abstraction how IDE "can" be an abstraction? It's tool, it's wrapper (e.g button over commandline commands), but abstraction?
Earlier quoted context omitted.
“Power drills have batteries or cords and motors that wear down and they’re more expensive and complex and can break more easily and it’s just smarter to bring hand crank tools to the worksite.” - Nobody
I think you've hit upon an important distinction, because while construction workers won't be bringing hand tools "to the worksite," there are in fact many people who do use hand tools for fine woodworking in their woodshops. People work with wood for different reasons and people write software for different reasons. All of these tools and approaches can be valid. Some may be interested in rapid and low cost large sc…
When I’m paid to produce, I use tools that help me produce.
When I’m enjoying my passion, I actually do use an entirely different set of tools!
The author seems to use IDE for one purpose only: to auto-generate boilerplate code. But this is far from the only benefits of IDEs! I rarely use IDEs for code generation, I don't even like autocomplete. For this stuff I use code snippets; I develop collections of those for any language I use. You don't need an IDE for it; any good text editor has such features. For me really important features of a good IDE are: - N…
Does emacs or vim with lsp count as an IDE?
I guess it depends on your definition of an IDE, and where you're most comfortable/productive. I see a lot of posts about autocomplete, refactoring, linting, tooltips, tests-by-cursor/file, snippets. Thanks to a very friendly plugin community, you can get all of these in vim, emacs etc. I like vim, and it has nothing to do with hubris. For me it's mostly about: 1. proximity to the terminal: I find cli tools very usef…
> Thanks to a very friendly plugin community, you can get all of these in vim, emacs etc. I like vim, and it has nothing to do with hubris. > 0% adjustment when working over SSH: tabs, splits, etc. both in my editor and terminal are identical in an SSH session. No discomfort. Mostly useful at home. Aren't these two benefits mutually exclusive? If you're got a very personalised vim setup, then vim on your workstation…
Now that vscode has a plugin that uses your local setup to edit files over SSH, my argument is a lot less compelling. Even at home, I have a lesser vimrc I provision to servers - I found it hard to justify installing treesitter, linters, etc. on a server where I'm mostly dealing with json/yaml/shellscript.
Earlier quoted context omitted.
> Do I have to spin up a whole session of the IDE just to run my test suite? In the java ecosystem at least, the answer is no. But in highly CI-based situations, the answer is still no, but you DO need the CI system to be up, and the only way to run a test at all is to just commit something and see the CI system run it, e.g. because the tests require a database engine that isn't installed on your development machine.…
In my current organization I saw a project, where there is no Maven. The build system is a couple of configuration files for Eclipse IDE and that's the only way to run it. I'm glad I didn't have to do anything around that.