What is Neovim and what are its top alternatives?
Neovim is a popular text editor that is a fork of the original Vim editor, with added features and improvements such as better performance, asynchronous plugins, and built-in terminal emulator. It allows for extensive customization through plugins and configuration files, making it a favorite among developers for its efficiency and flexibility. However, some users may find its learning curve steep, as it requires a good understanding of Vim commands and configuration.
- Emacs: Emacs is another powerful text editor with a rich set of features and customization options. It offers a highly extensible and customizable environment through Emacs Lisp, but it may have a steeper learning curve than Neovim for beginners.
- Visual Studio Code: Visual Studio Code is a widely used modern code editor developed by Microsoft. It offers a user-friendly interface, extensive plugin ecosystem, and built-in debugging capabilities, making it a strong competitor to Neovim, especially for those looking for a more integrated development environment.
- Sublime Text: Sublime Text is a sleek and fast text editor known for its speed and responsiveness. It offers a simple yet powerful editing experience with features like multiple selections, split editing, and a distraction-free mode. However, it is not open source like Neovim.
- Atom: Atom is an open-source text editor developed by GitHub. It provides a modern and customizable interface, support for plugins, and a built-in package manager. Atom may be a good alternative for those looking for a more user-friendly editor compared to Neovim.
- JetBrains IntelliJ IDEA: IntelliJ IDEA is a popular integrated development environment for Java and other programming languages. It offers advanced coding assistance, intelligent refactorings, and built-in tools for testing and debugging. While it may be heavier than Neovim, it provides a comprehensive set of features for professional developers.
- GNU Nano: GNU Nano is a simple and easy-to-use text editor suitable for beginners. It offers basic editing features and keyboard shortcuts, making it a lightweight alternative to Neovim for quick edits and simple tasks.
- Kate: Kate is a feature-rich text editor for the KDE desktop environment. It provides advanced editing capabilities, syntax highlighting, and support for numerous file formats. Kate may appeal to users looking for a Neovim alternative with KDE integration.
- Vim: Vim is the original editor from which Neovim was forked. It offers powerful modal editing, extensibility through plugins, and a large user base. While it lacks some of the features of Neovim, Vim remains a solid choice for those comfortable with its modal editing style.
- Micro: Micro is a modern and intuitive terminal-based text editor. It aims to be easy to use with keyboard shortcuts and mouse support, making it a user-friendly alternative for those who prefer a more accessible editor compared to Neovim.
- Geany: Geany is a lightweight text editor with basic features and plugins available for extended functionality. It offers a simple and fast editing experience suitable for smaller projects and quick edits, making it a straightforward alternative to Neovim for casual users.
Top Alternatives to Neovim
- Vim
Vim is an advanced text editor that seeks to provide the power of the de-facto Unix editor 'Vi', with a more complete feature set. Vim is a highly configurable text editor built to enable efficient text editing. It is an improved version of the vi editor distributed with most UNIX systems. Vim is distributed free as charityware. ...
- Atom
At GitHub, we're building the text editor we've always wanted. A tool you can customize to do anything, but also use productively on the first day without ever touching a config file. Atom is modern, approachable, and hackable to the core. We can't wait to see what you build with it. ...
- Kakoune
Kakoune is a code editor heavily inspired by Vim, as such most of its commands are similar to vi’s ones. Kakoune can operate in two modes, normal and insertion. In insertion mode, keys are directly inserted into the current buffer. In normal mode, keys are used to manipulate the current selection and to enter insertion mode. ...
- Emacs
GNU Emacs is an extensible, customizable text editor—and more. At its core is an interpreter for Emacs Lisp, a dialect of the Lisp programming language with extensions to support text editing. ...
- SpaceVim
SpaceVim is a Modular configuration, a bundle of custom settings and plugins, for Vim. It got inspired by spacemacs. ...
- Spacemacs
Since version 0.101.0 and later Spacemacs totally abolishes the frontiers between Vim and Emacs. The user can now choose his/her preferred editing style and enjoy all the Spacemacs features. Even better, it is possible to dynamically switch between the two styles seamlessly which makes it possible for programmers with different styles to do seat pair programming using the same editor. ...
- Git
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...
- GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...
Neovim alternatives & related posts
- Comes by default in most unix systems (remote editing)347
- Fast328
- Highly configurable312
- Less mouse dependence297
- Lightweight247
- Speed145
- Plugins100
- Hardcore97
- It's for pros82
- Vertically split windows65
- Open-source30
- Modal editing25
- No remembering shortcuts, instead "talks" to the editor22
- It stood the Test of Time21
- Unicode16
- VimPlugins13
- Everything is on the keyboard13
- Stick with terminal13
- Dotfiles12
- Flexible Indenting11
- Hands stay on the keyboard10
- Efficient and powerful10
- Programmable10
- Everywhere9
- Large number of Shortcuts9
- A chainsaw for text editing8
- Unmatched productivity8
- Developer speed7
- Super fast7
- Makes you a true bearded developer7
- Because its not Emacs7
- Modal editing changes everything7
- You cannot exit6
- Themes6
- EasyMotion5
- Most and most powerful plugins of any editor5
- Shell escapes and shell imports :!<command> and !!cmd5
- Intergrated into most editors5
- Shortcuts5
- Great on large text files5
- Habit5
- Plugin manager options. Vim-plug, Pathogen, etc5
- Intuitive, once mastered4
- Perfect command line editor4
- Not MicroSoft1
- Ugly UI8
- Hard to learn5
related Vim posts
- Go because it's easy and simple, facilitates collaboration , and also it's fast, scalable, powerful.
- Visual Studio Code because it has one of the most sophisticated Go language support plugins.
- Vim because it's Vim
- Git because it's Git
- Docker and Docker Compose because it's quick and easy to have reproducible builds/tests with them
- Arch Linux because Docker for Mac/Win is a disaster for the human nervous system, and Arch is the coolest Linux distro so far
- Stack Overflow because of Copy-Paste Driven Development
- JavaScript and Python when a something needs to be coded for yesterday
- PhpStorm because it saves me like 300 "Ctrl+F" key strokes a minute
- cURL because terminal all the way
I liked Sublime Text for its speed, simplicity and keyboard shortcuts which synergize well when working on scripting languages like Ruby and JavaScript. I extended the editor with custom Python scripts that improved keyboard navigability such as autofocusing the sidebar when no files are open, or changing tab closing behavior.
But customization can only get you so far, and there were little things that I still had to use the mouse for, such as scrolling, repositioning lines on the screen, selecting the line number of a failing test stack trace from a separate plugin pane, etc. After 3 years of wearily moving my arm and hand to perform the same repetitive tasks, I decided to switch to Vim for 3 reasons:
- your fingers literally don’t ever need to leave the keyboard home row (I had to remap the escape key though)
- it is a reliable tool that has been around for more than 30 years and will still be around for the next 30 years
- I wanted to "look like a hacker" by doing everything inside my terminal and by becoming a better Unix citizen
The learning curve is very steep and it took me a year to master it, but investing time to be truly comfortable with my #TextEditor was more than worth it. To me, Vim comes close to being the perfect editor and I probably won’t need to switch ever again. It feels good to ignore new editors that come out every few years, like Atom and Visual Studio Code.
- Free529
- Open source449
- Modular design343
- Hackable321
- Beautiful UI316
- Backed by github147
- Built with node.js119
- Web native113
- Community107
- Packages35
- Cross platform18
- Nice UI5
- Multicursor support5
- TypeScript editor5
- Open source, lots of packages, and so configurable3
- cli start3
- Simple but powerful3
- Chrome Inspector works IN EDITOR3
- Snippets3
- Code readability2
- It's powerful2
- Awesome2
- Smart TypeScript code completion2
- Well documented2
- works with GitLab1
- "Free", "Hackable", "Open Source", The Awesomness1
- full support1
- vim support1
- Split-Tab Layout1
- Apm publish minor1
- Consistent UI on all platforms1
- User friendly1
- Hackable and Open Source1
- Publish0
- Slow with large files19
- Slow startup7
- Most of the time packages are hard to find.2
- No longer maintained1
- Cannot Run code with F51
- Can be easily Modified1
related Atom posts
I liked Sublime Text for its speed, simplicity and keyboard shortcuts which synergize well when working on scripting languages like Ruby and JavaScript. I extended the editor with custom Python scripts that improved keyboard navigability such as autofocusing the sidebar when no files are open, or changing tab closing behavior.
But customization can only get you so far, and there were little things that I still had to use the mouse for, such as scrolling, repositioning lines on the screen, selecting the line number of a failing test stack trace from a separate plugin pane, etc. After 3 years of wearily moving my arm and hand to perform the same repetitive tasks, I decided to switch to Vim for 3 reasons:
- your fingers literally don’t ever need to leave the keyboard home row (I had to remap the escape key though)
- it is a reliable tool that has been around for more than 30 years and will still be around for the next 30 years
- I wanted to "look like a hacker" by doing everything inside my terminal and by becoming a better Unix citizen
The learning curve is very steep and it took me a year to master it, but investing time to be truly comfortable with my #TextEditor was more than worth it. To me, Vim comes close to being the perfect editor and I probably won’t need to switch ever again. It feels good to ignore new editors that come out every few years, like Atom and Visual Studio Code.
We use Visual Studio Code because it allows us to easily and quickly integrate with Git, much like Sublime Merge ,but it is integrated into the IDE. Another cool part about VS Code is the ability collaborate with each other with Visual Studio Live Share which allows our whole team to get more done together. It brings the convenience of the Google Suite to programming, offering something that works more smoothly than anything found on Atom or Sublime Text
Kakoune
- Multiple selections7
- Fast editing7
- Interactivity5
- Consistency of the underlying language4
- UNIX citizen4
- Self documented3
related Kakoune posts
- Vast array of extensions65
- Have all you can imagine44
- Everything i need in one place40
- Portability39
- Customer config32
- Your config works on any platform16
- Low memory consumption13
- Perfect for monsters11
- All life inside one program10
- Extendable, portable, fast - all at your fingertips8
- Enables extremely rapid keyboard-only navigation6
- Widely-used keybindings (e.g. by bash)5
- Extensible in Lisp5
- Runs everywhere important5
- FOSS Software4
- Powerful multilanguage IDE4
- Git integration4
- May be old but always reliable4
- Asynchronous3
- Powerful UI3
- Huge ecosystem1
- So good and extensible, that one can get sidetracked4
- Hard to learn for beginners4
- Not default preinstalled in GNU/linux1
related Emacs posts
- Easy to get started with4
- Easy to update4
- Attractive default theme3
- Realtime Guide3
- Setting up language servers just works2
- Better default2
related SpaceVim posts
Spacemacs
- Advanced support for Vim key bindings14
- Discoverability12
- Easy setup10
- Never have to touch the mouse10
- Community-driven configuration7
- Cross-platform7
- Documentation6
- Emacs5
- Fast-paced development4
- Evil4
- Nice UI4
- Git Integration2
- Autocompletion1
related Spacemacs posts
- Distributed version control system1.4K
- Efficient branching and merging1.1K
- Fast959
- Open source845
- Better than svn726
- Great command-line application368
- Simple306
- Free291
- Easy to use232
- Does not require server222
- Distributed28
- Small & Fast23
- Feature based workflow18
- Staging Area15
- Most wide-spread VSC13
- Disposable Experimentation11
- Role-based codelines11
- Frictionless Context Switching7
- Data Assurance6
- Efficient5
- Just awesome4
- Easy branching and merging3
- Github integration3
- Compatible2
- Possible to lose history and commits2
- Flexible2
- Team Integration1
- Easy1
- Light1
- Fast, scalable, distributed revision control system1
- Rebase supported natively; reflog; access to plumbing1
- Flexible, easy, Safe, and fast1
- CLI is great, but the GUI tools are awesome1
- It's what you do1
- Phinx0
- Hard to learn16
- Inconsistent command line interface11
- Easy to lose uncommitted work9
- Worst documentation ever possibly made8
- Awful merge handling5
- Unexistent preventive security flows3
- Rebase hell3
- Ironically even die-hard supporters screw up badly2
- When --force is disabled, cannot rebase2
- Doesn't scale for big data1
related Git posts
Our whole DevOps stack consists of the following tools:
- GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
- Respectively Git as revision control system
- SourceTree as Git GUI
- Visual Studio Code as IDE
- CircleCI for continuous integration (automatize development process)
- Prettier / TSLint / ESLint as code linter
- SonarQube as quality gate
- Docker as container management (incl. Docker Compose for multi-container application management)
- VirtualBox for operating system simulation tests
- Kubernetes as cluster management for docker containers
- Heroku for deploying in test environments
- nginx as web server (preferably used as facade server in production environment)
- SSLMate (using OpenSSL) for certificate management
- Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
- PostgreSQL as preferred database system
- Redis as preferred in-memory database/store (great for caching)
The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:
- Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
- Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
- Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
- Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
- Scalability: All-in-one framework for distributed systems.
- Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).
It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up
or vagrant reload
we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.
I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up
, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.
We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.
If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.
The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).
Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.
GitHub
- Open source friendly1.8K
- Easy source control1.5K
- Nice UI1.3K
- Great for team collaboration1.1K
- Easy setup868
- Issue tracker504
- Great community487
- Remote team collaboration483
- Great way to share449
- Pull request and features planning442
- Just works147
- Integrated in many tools132
- Free Public Repos122
- Github Gists116
- Github pages113
- Easy to find repos83
- Open source62
- Easy to find projects60
- It's free60
- Network effect56
- Extensive API49
- Organizations43
- Branching42
- Developer Profiles34
- Git Powered Wikis32
- Great for collaboration30
- It's fun24
- Clean interface and good integrations23
- Community SDK involvement22
- Learn from others source code20
- Because: Git16
- It integrates directly with Azure14
- Standard in Open Source collab10
- Newsfeed10
- Fast8
- Beautiful user experience8
- It integrates directly with Hipchat8
- Easy to discover new code libraries7
- It's awesome6
- Smooth integration6
- Cloud SCM6
- Nice API6
- Graphs6
- Integrations6
- Hands down best online Git service available5
- Reliable5
- Quick Onboarding5
- CI Integration5
- Remarkable uptime5
- Security options4
- Loved by developers4
- Uses GIT4
- Free HTML hosting4
- Easy to use and collaborate with others4
- Version Control4
- Simple but powerful4
- Unlimited Public Repos at no cost4
- Nice to use3
- IAM3
- Ci3
- Easy deployment via SSH3
- Free private repos2
- Good tools support2
- All in one development service2
- Never dethroned2
- Easy source control and everything is backed up2
- Issues tracker2
- Self Hosted2
- IAM integration2
- Very Easy to Use2
- Easy to use2
- Leads the copycats2
- Free HTML hostings2
- Easy and efficient maintainance of the projects2
- Beautiful2
- Dasf1
- Profound1
- Owned by micrcosoft55
- Expensive for lone developers that want private repos38
- Relatively slow product/feature release cadence15
- API scoping could be better10
- Only 3 collaborators for private repos9
- Limited featureset for issue management4
- Does not have a graph for showing history like git lens3
- GitHub Packages does not support SNAPSHOT versions2
- No multilingual interface1
- Takes a long time to commit1
- Expensive1
related GitHub posts
I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.
I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!
I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.
Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.
Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.
With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.
If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.
Context: I wanted to create an end to end IoT data pipeline simulation in Google Cloud IoT Core and other GCP services. I never touched Terraform meaningfully until working on this project, and it's one of the best explorations in my development career. The documentation and syntax is incredibly human-readable and friendly. I'm used to building infrastructure through the google apis via Python , but I'm so glad past Sung did not make that decision. I was tempted to use Google Cloud Deployment Manager, but the templates were a bit convoluted by first impression. I'm glad past Sung did not make this decision either.
Solution: Leveraging Google Cloud Build Google Cloud Run Google Cloud Bigtable Google BigQuery Google Cloud Storage Google Compute Engine along with some other fun tools, I can deploy over 40 GCP resources using Terraform!
Check Out My Architecture: CLICK ME
Check out the GitHub repo attached