Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Slap vs Microsoft's Visual Studio, the Slant community recommends Microsoft's Visual Studio for most people. In the question“What are the best JavaScript IDEs or editors?” Microsoft's Visual Studio is ranked 17th while Slap is ranked 45th. The most important reason people chose Microsoft's Visual Studio is:
Javascript Intellisense allows Visual Studio to provide you with useful hints and auto-completion features while you code.
Specs
Question 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 Javascript Intellisense support
Javascript Intellisense allows Visual Studio to provide you with useful hints and auto-completion features while you code.
Pro Clean UI
Visual Studio has a clean, intuitive user interface.
Pro Cloud storage
Your Visual Studio online account gives you a place to store your code, backlog, and other project data with no servers to deploy, configure, or manage.
Pro Product backlog
In agile development teams, one really needs features such as product backlogs where you can assign features to teammates and track their progress on them. VS provides a web-based interface for you to track your team's complete progress on the project.
Pro Very good XML/XSD support
Syntax highlighting, Intellisense, and jump to declaration all work in XML documents.
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 Tons of feature bloat
If you're doing simple web frontend dev, then VS is far too arcane and feature bloated for most of your work.
Con Not cross-platform
Visual Studio is only available on Windows, which causes platform lock-in.
Con Slow
Visual Studio can be quite laggy.
Con Takes up a lot of space
Visual Studio can use about 6 GBs which a lot of space to be taken from your computer.
Con Terribly slow development
Keep dreaming about features already provided by alternative products.
Con Non-native window frame
The IDE main window lacks a standard window frame (titlebar/borders). A custom solution is used where the custom titlebar contains numerous application-specific controls. This results in inconsistent UX and can also be problematic when you're using shell replacements or other various window-management software (such as bbLean).
Con Terrible UI
Con Extensions
