When comparing Slap vs Codiad, the Slant community recommends Slap for most people. In the question“What are the best programming text editors?” Slap is ranked 47th while Codiad is ranked 64th. The most important reason people chose Slap is:
Slap supports mouse keybindings even though it works inside the terminal and also through SSH.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro First-class mouse support
Slap supports mouse keybindings even though it works inside the terminal and also through SSH.
Pro Uses desktop-like keybindings
Slap features configurable keybindings (Ctrl+S, Ctrl+Z, etc).
Pro Great terminal interface
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
Cons
Con Requires node.js
Slap is written in JavaScript and it requires something to interpret it in a local machine. That something is node.js, but for people who don't need node, it would be a hindrance and an overkill to install node just to use a simple text editor. Furthermore, it can only be used remotely if the remote machine has node installed.
Con CLI only
Slap only runs through the terminal.
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 (
by \(
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.