Earlier quoted context omitted.
Do they have every single medicine memorized, or just the ones they most commonly use? Sure, I tend to remember the parts of libraries and apis I use often, but I'd still argue my editor having a reminder just a keystroke away is very beneficial.
More than just the most commonly used... https://www.youtube.com/watch?v=jR7d56UeeeU <= Song-based memorization aide for 200 different medications
Benefits of Not Using an IDE
271–280 of 389 posts
Re: Benefits of Not Using an IDE
#272Listen, long story short: just say no to nonsense like this. Given the choice of a) tooling, or b) no tooling, you’re not being smart, cool or clever by choosing b. Obviously, what tools you pick are important and heavy IDEs like IntelliJ are a trade off between speed and functionality, and yeah, more nimble tools do exist, and it’s definitely worth trying different development tools to see what makes you most produc…
“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
Similarly, an IDE can be overkill when you're writing a self-contained one-off task, or dealing with an opinionated IDE that doesn't fit with the project you're importing.
Re: Benefits of Not Using an IDE
#273I would say that an editor that INTEGRATES knowledge of your source in some way, like auto-complete, or red-squiggles, is very much a big step towards an IDE and should could as "using an IDE". Whether it does that using plug-ins/extensions or natively doesn't matter. If it has that functionality there's not that much more separating it from an IDE.
VSCode, for example, is more like an IDE than an editor especially as you add more and more extensions.
Re: Benefits of Not Using an IDE
#274Re: Benefits of Not Using an IDE
#275Earlier 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.
My choice in editors follows the same logic. If I just need to jot down some notes, or knock together a simple bash script or something, it doesn't really matter what I use. Whatever has syntax highlighting and is available on that system is great. Something more complex, where I don't want to spend brain cycles on repetitive tasks or management that the tools can handle for me, I'd rather use something that will handle that for me.
Re: Benefits of Not Using an IDE
#276Re: Benefits of Not Using an IDE
#277Earlier quoted context omitted.
For Java at least, the language server built into IntelliJ is comically further ahead than VS Code + extensions.
I know I'll make some people not happy by saying this but the only reason you need so much complex IDE tooling with Java compared to other languages is because the language itself & the tools associated to it are not very well designed. Just about everything requires some insane boilerplate where it should not. It's not a solution to a problem, it's a problem searching for a solution.
The reality is that Java at this point is a mature platform broadly supported by many, many stakeholders. Its benefits and issues are, in general, decently well known and understood.
Billions (likely even trillions) of lines of Java are running in production today and those applications will need to be maintained moving forward. IDEs make Java development a much more pleasant experience and so there will be a place for IDEs.
Re: Benefits of Not Using an IDE
#278I used Webstorm for years, but switched to VSCode. It's just more flexible, which allows me to use new tech/langs very quickly. If you don't focus on IDE features, you tend to implement quality of life improvements at a level that also works in an editor. Like in the language, framework, or library you're using (See the code generators point in the article). With languages like Rust, that have zero cost abstractions,…
Re: Benefits of Not Using an IDE
#279Earlier quoted context omitted.
I use both, one method is just less restrictive.
The whole "real men use vi" type superiority complex failure mode is intensely annoying (and I say this as somebody who often has original ex-vi installed) but the inverted version where you just have a superiority complex from the opposite direction isn't actually any better. It continues to amaze me that "it's worth becoming familiar with a wide range of tools and then pick the one that's going to work best for you…
Re: Benefits of Not Using an IDE
#280Earlier 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…
> 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. Isn't this the case with Android Studio? Is it even possible to do Android development without Android Studio?
Oh yes: https://www.lambdanative.org/