When comparing Howl vs Codiad, the Slant community recommends Howl for most people. In the question“What are the best programming text editors?” Howl is ranked 21st while Codiad is ranked 64th. The most important reason people chose Howl is:
You don't need the mouse to use Howl. Everything can be accomplished with commands and shortcuts.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Keyboard driven
You don't need the mouse to use Howl. Everything can be accomplished with commands and shortcuts.
Pro Fast startup
It's extremely lightweight, making it start up pretty quickly.
Pro Easy to use
Howl is very intuitive and easy to use.
Pro Easy to extend
Plugins (bundles) can be written in Lua or MoonScript.
Pro UI Focused on editting
Non distracted icons, toolbars, pannels, extra spacing, etc.
Pro Language tooling
Has built-in functionality for completion, inline documentation and linting so IDE-like features can be added easily.
Pro Command line palette
Search for your commands in an easy way and see in the list which key-strokes are mapped to which commands
Pro Open source
Howl is an open source project and is actively developed on GitHub(howl-editor/howl). It has a MIT license.
Pro Works on OpenBSD
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 Lack of Lua examples
Although Howl can be extended in both Lua and MoonScript, almost all bundles are written in MoonScript. This means that it is a bit harder to find examples if you'd rather write your bundle in Lua. MoonScript can be compiled to Lua but the code won't be as clean and understandable as if it would've been written in Lua by hand.
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.