Show HN: Goodbye Old Editor – Reinventing coding with the cloud

Show HN: Goodbye Old Editor – Reinventing coding with the cloud
friendco.de

    - auto completion, file names, var names, classes and functions, words in general etc. (like in: vim - omnicomplete, emacs: auto-complete)

    - fill column marker (v: colorcolumn, e: many, fill-column-indicator)

    - code outline (v: TagBar, e: Speedbar)

    - refactoring support, rename var/fun/class (many options)

    - go to definition (for Python v: python-mode, e: elpy; or generically with ctags, etags)

    - comment region (v: NERDCommenter, e: comment-region)

    - declare and insert snippets (v: vim-snipmate, e: yasnippet and others)

    - rectangular selection and operations (v: Ctrl-v, e: C-x r ... or rect-mark)

    - find file in project (fuzzy matching optional) (v: Command-T, e: find-file-in-project, ifind, others)

    - find in files (v: :(vim)grep or other, e: lgrep or multiple others)

    - change/set surrounding "'([{ chars (v: surround, e: wrap-region or (somewhat) paredit)

I don't want to sound like I'm saying the product is a bad idea or that what we have now is sufficient and we don't need new things. I'm honestly very used to these features and they make me more productive; if I was a hobbyist, I could switch to less featureful editor right now, but for a professional your productivity determines your income for the large part. So, while I like the idea of in-browser editors, I cannot use them unless they have the features I need. If they are in different places then ok, but not if they are lacking.