Lmao they have a different font and text color on every single page, what are you talking about? It looks like absolute, pure garbage. I would never want that to be my company website if I was a CEO, even if my company did just support systems that are 20+ years out of date.
Honestly, the more I look at this, this may be the worst website I have seen in quite a few years. I can't believe this is a currently-existing tech company.
Yes, beacuse they we're losing out as web development exploded, and realized no one wanted to pay for an editor when there we so many great free alternatives. They did it out of necessity, not out of innovation. Just like everything they do when it comes to their "open source movement"
Sorry for the late reply. I'm actually a huge fan of modal editing as well, can't live without it, so I use evil - and it's perfect. GUI emacs does everything that any other IDE does, and that's what I like so much about it. With vim or any of it's GUIs, normal IDE features feel like "duct tape" on top of the program. Whereas, emacs was meant to be used in this context. I mean, for example, when programming in C I can even use emacs to debug (it has a GUI for gdb). And those kind of advanced IDE features are available for any language. Not even touching the fact it's just a lisp machine and you can build any kind of program you want in it, it takes extensibility to the next level with a lisp dialect that's relatively easy to learn, whereas extensibility in vim is limited to googling for vimscript code someone else wrote (unless you take the time to learn vimscript shudders). Emacs gave me everything you said you were looking for, at a time when I was looking for those exact things. I wanted a modal editor like vim that actually was an IDE, had IDE features, and was completely extensible. Emacs checks all of those boxes.
If you're a vimmer and want to start out with emacs, try spacemacs. I used it for a year before building my own emacs config. It's an incredible program, won't take you long to get running if you're used to vim, and after a week I'd bet you'll have a hard time going back to gVim.
Emacs is a gui editor. It has a shell mode, but it's primarily supposed to be used through the GUI. GUI Emacs is literally everything you described looking for above - an advanced GUI with more features than you could evere learn, yet one that still retains first class focus on keyboard UX.
I remember seeing the talk on this at Lua Workshop 2017. daurnimator gave a great demo. Glad to see it get more publicity and an actual release - looks really promising
Who really says that though? As a regular lurker on the vim/neovim subreddits and mailing lists, I've never seen anyone try to fix someone's issue in vim by telling them to get neovim (literally never). Because, in the end, they're going to end up with the same issue. You already know what neovim is....so why would switching solve anything? Say they don't know how to use tabs, omnicompletion...why would neovim be any different?
Now what you may see, to your point, is people pushing (one of the many versions of) Spacevim on those forums. And they are shat upon rather immediately. It does happen though. But that at least makes sense, because those programs make using vim "easier", therefore eliminating issues users may have.
But neovim? Certainly not. The only time that would be a suggestion for someone is if they want some of the features neovim has over stock vim (maybe they want saner defaults, for example, or don't like tmux and want an integrated terminal).
It's seamless. I've been using it for the past 6 months for almost all of my coding. The windows build is brand new and still has some problems, but assuming you're using *nix/mac, you won't have any issues.
Honestly the GitHub repo explains about everything. I check in on r/neovim, as the main contributor posts there often and helps people with problems/questions (I mostly just like reading about the new stuff their doing on the subreddit).
You should use a different completion plugin then. YCM is the only one that needs to be compiled. If you use regular vim, check out neocomplete, and if you use neovim, well, you should know about deoplete (it's kickass). Both of these pretty much work out of the box; they have accompanying clang sources (vim-clang or deoplete-clang) that feed the suggestions to neocomplete/deoplete.
Frankly, I would use neovim + deoplete. Modern, async, and a big user community right now (almost everyone with neovim runs deoplete).