Remote: Yes

Willing to relate: Yes (Preferably: Seattle, WA or CO)

Technologies: Javascript, React, Node.js, Static Websites, Progress Web Apps (PWA), Golang, AWS, RESTful APIs

Resume/CV: https://hhsnopek.com/resume.pdf

Email: hhsnopek at gmail dot com (also see resume)

Website: https://hhsnopek.com

Github: https://github.com/hhsnopek

LinkedIn: https://www.linkedin.com/in/hhsnopek

Experience frontend and lead developer, who's well-vised in the full-stack.

Native English Speaker, Available full-time, interview ready, willing to relocate (prefer remote), No contracting.

Comments URL: https://news.ycombinator.com/item?id=16934584

Points: 3

# Comments: 1

Edit: ~3-5 cups a day

I was hoping for Apple to switch it up this year with start of their new backend for Safari, rather I don't expect it to turn out as I have wished.

I'm fine with the OP switching editors, I could careless which editor someone is using or switching to, but don't place the blame on plugin performance, plugin bloat, or building an IDE; Vim isn't an all-in-one solution and that's okay, we can push it to be an all-in-one solution.

My constructive criticism is that these problems are in every editor, don't pin it on vim plugins or the amount of plugins you're loading into vim. "releativenumber" is a valid reason to switch editors, but the rest of the reasons are applicable to all editors.

Edit: "switching terminals" -> "switching editors"

If you were already using Alacritty and Neovim, you should expand on why these did not solve your problems as many if not all speed/optimizations can be matched or better than Sublime Text

"Why I'm no longer using vim and now using X" typically result from not digging into Vim enough. All the issues the OP is having have been resolved from either updates to vim, switching terminals, or just understanding vim basics.

NOTE: Plugs can be slow and the OP is correct that some are hacky, but typically there's the Vanilla Vim solution to a problem that takes a little bit of reading and/or finding to solve.

If plugin/loading speed is really an issue then switch to using Alacritty and Neovim, use vim-plug for async & lazy loading plugins. You get truecolor support and you're using your GPU to render everything. If plugin speed is still a problem, learn why they're loading slowly, then dig into why rather than just saying "they're hacky or clunky". Silver search is great, but if you understand how to execute terminal commands from vim (:!) then you can grep everything and remove the need for silver search. I use FZF (https://github.com/junegunn/fzf) which is another fuzzy searcher that's optimized for speed, built with Go.

For those that don't want to put in the time to optimize and learn vim, then by all means switch editors. But don't blame the editor ("I will not use shitty software just because it’s open source.") unless it's truly the root of the problems, explore and find better ways. A key thing to remember as a Vim user is there's always a faster way and your .vimrc will always be different from another's.

Edit: For those interested in my setup (https://github.com/hhsnopek/dotfiles/blob/master/.nvimrc)

Honestly the author just lacked the time and knowledge to go ahead and learn basic bash tools and utilize them.

Then it seems that Go isn't the language for you. With that Go nor any language, unless intended, is suppose to be a one-all solution for every problem. We can accomplish a majority, if not all, problems in a language, but this shouldn't assumed that a language is intended to do so.

Comments URL: https://news.ycombinator.com/item?id=13323502

Points: 1

# Comments: 1