IDEs visualise more data about the project you're working on then just text editors. It might point out common errors/mistakes you've been doing on your code before executing it.
Text editors don't have these features.
this post was submitted on 31 Jan 2024
22 points (95.8% liked)
Asklemmy
43818 readers
869 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
You're also forgetting automated refactors, git integration, maven integration and a whole lotta stuff that IDEs facilitate
For sure, they do got integration up the wazoo!
Though in the past decade or so, the lines have been blurred between a "dumb" editor and a full-on IDE with the advent of LSP, DAP and the like.
The line between text editors and IDE can be blurry, neovim with plugins is a thing.
Depends strongly on the editor. Emacs can make you a cup of coffee.
Essentially modern software development uses a few different components.
Usually you have a text editor with plugins or an IDE (integrated development environment) which has the text editing functionality and ties the other tools together for display purposes and to tell other tools which locations in the code you mean.
A lot of IDEs had more of the tooling for one or more languages built-in but usually now you have a so called language server which runs in the background and communicates with your text editor or IDE via the Language Server Protocol (LSP).
There is also a similar but less mature system called the Debug Adapter Protocol which is used by some editors and IDEs and has support in debuggers for some languages but is far less universal than LSP at this point in time.
Other tools require less detailed interaction with the editor or IDE and they are just called and their output is processed. These are probably the terminal applications you are thinking of.
This includes some interpreters and compilers as well as static analysis tools such as linters and test suites for your code.
Some people prefer to control everything with their IDE and others call some of the tools manually in separate terminal windows.
Some editors and IDEs also integrate with tooling such as version control systems like git to e.g. display which lines of code are new.
Part of development also happens outside of IDEs or text editors, e.g. in code review tools like Gerrit or the code review part of GitLab.
they are so much more than that. Builder for example has a full tree view of your project, instant compiling (well, instant in the sense that the compile button is always accessible and you don't have to leave the application to do it), live preview for markup languages, Git integration, unit tests, profiling, and several other things I can't remember right now. so no, an IDE is an entirely different beast from a text editor
Not really. A good code editor has:
- Editing.
- Syntax highlighting, paren matching.
- Filters - basic functions like sort, up to your own scripts.
- Build/send to REPL.
ed doesn't have highlighting, but it's perfectly useful. Notepad's basically useless, you can't highlight or filter, can't build. Vim does 1-3, and then you just type :!make or whatever.
An IDE is to Notepad, as a car is to a skateboard.