When comparing ed vs Codiad, the Slant community recommends ed for most people. In the question“What are the best programming text editors?” ed is ranked 47th while Codiad is ranked 51st. The most important reason people chose ed is:
As the standard text editor, `ed` is available on multiple systems.
Ranked in these QuestionsQuestion Ranking
Pro ed is the standard text editor
As the standard text editor,
ed is available on multiple systems.
Pro Consistent UI
ed has a consistent user interface and error reportage.
Pro Open source
You can run Codiad on your server to allow you and your team to edit files.
Simplest to run may be using a Docker image like linuxserver/codiad.
Pro Easy to self-host: Only requires PHP
It only requires PHP 5+ and Nginx or Apache. No database is required. This makes it really easy to install on many servers include shared hosting.
Pro Multi-line edit
Allows to edit multiple things are once by having multiple cursors like Sublime Text.
Pro Has many easily installable plugins
Many plugins exist, from Terminal, Git to Collaboration and Emmet... Plugins can be installed by using the web interface, or by manually extracting files to the right directory.
Pro Simple and easily managable GUI
There's absolutely no need for ed when you have sed and ex.
Con Not a lot of features
While extremely fast and simple, Ed is simply not for programming for a long time because it lacks a lot of important features. It should be used instead for quick edits.
Con Not a persistent UI
You can only view portions of a file through search or regular expression commands. You cannot scan or scroll through a file using the available screen real-estate.
It's not too dissimilar in use to command-line tools (such as grep and sed) for editing a file. In fact, both grep and sed are based on how interaction is performed with Ed.
Con Terminal runs as same user for everyone
No matter who is the logged in user, the Terminal plugin runs commands as the PHP user. This also affects the Git plugin in that there is a single SSH key for all users using your Codiad instance.
Con Full of small bugs
There are plenty of various issues and bug that may either be due to your setup and the UI will not report them, or due to bugs in the code; I'm including common plugins here as well (just naming a few: search files and in files may report nothing if it had an error, commands stderr not printed, marketplace not showing items, search in market place showing no results, Git escaping
\( in the commit message for no good reason...). Those are generally small but together it makes the product feel flawed.
Con Currently no search and replace in multiple files
There is a search in multiple files, and search & replace in current file, but not something to perform a search & replace in multiple files.
Con Terminal doesn't TTY
The terminal plugin for Codiad allows users to type some commands and see the outputs, but not interactive input is supported (i.e. stdin is closed). Meaning you cannot run Vim, Tmux or anything requiring user inputs.