Live data from Hacker News

What do you really get from IDE-driven development?

briandfoy.github.io

101–110 of 143 posts

Re: What do you really get from IDE-driven development?

#101

Earlier quoted context omitted.

They take pride in their masochism

It's called exercise. Plenty of people do a lot of physical exercise when they could be content to stay still, but it's good for health. In this case, mental exercise keeps the brain healthy.

Time you spend fiddling with tools trying to replicate a tiny portion of what an IDE offers can be spent actually doing mental exercises to keep your brain healthy.

Re: What do you really get from IDE-driven development?

#102
post #27

Having spent a few years in Perl I understand some of the frustration of an IDE. I find dynamic languages don't gain a lot from an IDE. But if you're in something with stronger types like Java, typescript or F# the IDE is a God send. The best tool ever is refactor rename. When the IDE can parse your entire code base and rename just the function or variable you want it's amazing. Go to definition is worlds better too.…

Well, what's the old saying - nothing can parse Perl, but Perl?

As for JS and IDEs, you should try an IDE again. Far better.

Re: What do you really get from IDE-driven development?

#104
> Mark Jason Dominus has an interesting perspective on Java, which he enjoyed: You will not produce anything really brilliant...

I'd argue that there's plenty of brilliant things written in Java. And Perl people sneering at Java feels a bit like defensiveness.

Re: What do you really get from IDE-driven development?

#105
post #61

Earlier quoted context omitted.

I think a lot of people's views have been influenced by their use of languages where the type system or overall language framework is either too weak (eg: Python, Javascript) or in some cases too complex (eg: C++) for more than a thin layer IDE experience to be possible. If you use those kind of languages then it's true, IDEs buy you a limited set of functionality and you don't need much more than a basic language se…

I agree; before I starting writing Swift, my only IDE experience was using Eclipse in college, and I really looked down on IDEs. I thought of them as a crutch required by poorly-designed and overly-verbose languages like Java. But the IDE experience with a language that has decent type system like Swift is really great. It truly just feels like a more efficient way to consume documentation and write code. The analogy…

Even if an IDE is only a crutch for poorly designed languages, people still use those languages and an IDE is a useful tool in that scenario.

Re: What do you really get from IDE-driven development?

#106
post #29

Earlier quoted context omitted.

> getting back into the command line, the terminal, the console & re-learning the hard way how to re-enact many of the things your IDE does for you is really hard. So, if the IDE gives us those tools, what is the exact benefit of "going back and learning the hard way"? > To insist on fast immediate obvious worth is to miss the big picture, is toxic to healthy ecosystems & diversity's neandering How much time do I hav…

> So, if the IDE gives us those tools, what is the exact benefit of "going back and learning the hard way"? Becoming a person of unlimited potential. Being capable of understanding & tackling anything, understanding the world you live in, not living like a marrionette shadow puppet your life. > How much time do I have to spend in the good old hard learning command line to replicate, say, 5% of Intellij Idea's refacto…

> Becoming a person of unlimited potential.

That's pure demagoguery. As is, really, the rest of your response.

> Two afternoons learning CodeMod would provide a lifetime of infinite capabilities

That's not the answer to the question. So, you've learned CodeMod scripts . How much timeyou will then have to spend to replicate 5% of IntelliJ's refactoring capabilities? And while you're struggling to replicate that, how many capabilities you're missing out on?

Re: What do you really get from IDE-driven development?

#107
An IDE has lots of tools I need to use to get my work done efficiently.

Because there are so many tools it is not obvious which tools should I should use when and in which order. And it depends on the context. Should I search for a string globally or in the current file? Or current directory or project? Should I split the code-editor vertically or not, or should I split it horizontally.

What I'm fascinated by is how working with an IDE it feels like I'm constantly creating a program in my head for myself to execute, to use the tools and functions of the IDE in a given sequence. I am thinking ahead what tasks I need to do and then I do them, in other words I am writing a program in my head for myself to execute.

I wonder if people are doing this kind of thing generally, or think of it this way?

Re: What do you really get from IDE-driven development?

#108
post #27

Having spent a few years in Perl I understand some of the frustration of an IDE. I find dynamic languages don't gain a lot from an IDE. But if you're in something with stronger types like Java, typescript or F# the IDE is a God send. The best tool ever is refactor rename. When the IDE can parse your entire code base and rename just the function or variable you want it's amazing. Go to definition is worlds better too.…

Well, what's the old saying - nothing can parse Perl, but Perl? As for JS and IDEs, you should try an IDE again. Far better.

Haha I've not heard that one. Perl is very much an unreadable code soup.

I will have to try on next time I'm in plain JS. It doesn't happen often. I have a preference for strongly typed languages. I suspect I have something similar to dyslexia. I mix the spelling of words and sometimes even the words. Strong typing is the tool that makes that problem go away.

Re: What do you really get from IDE-driven development?

#109
A single context to do everything. I don’t need to alt-tab away to run a CI job, browse the filesystem, run a shell, run my tests, etc etc its the same keyboard shortcuts, it eliminates the overhead of multiple contexts. I try to exploit features like “run tool” in my Ide so i never need to switch away.
Post reply on HN