As an amateur vim user, may I ask what is the alternative to using file trees or tabs?

Telescope[1] is pretty central to navigation in Neovim these days. Think Ctrl-P in VSCode, but for any entity in your editor or workspace, not just files. Files in workspace, buffers (open files), ripgrep results, LSP symbols / references, etc. Also provides a live preview of search results without having to open them. Plus easily add results to your quickfix list, making large-scale edits easy.

[1]:https://github.com/nvim-telescope/telescope.nvim

I am not the person you asked, but with Telescope you can check/toggle open buffers very quickly, once you get used to it, its far quicker than using tabs(for open buffers).

I do have nvim-tree installed but I rarely use it as most times I either navigate files from within definition or go to file from imports or use grep or just search to open from Telescope.

Check out TJDevries's videos about Personal IDE and about kickstart nvim, he is a neovim and Telescope maintainer so he highlights is various usage very well.

IMO, when switching to neovim you have to struggle for a week or so to learn its ways than trying to make it identical to VSCode. I did not switch to neovim until I learned basic file navigation through vim emulator on VSCode.As that was the hardest thing for me when I first tried vim/neovim.

Buffers. Telescope.

I remember learning vim and not understanding how people used it because you couldn't change files. Using buffers, and some kind of search to load files in made it clear.

Telescope is a good option for file search, and this also has grep.

  Location: Ukraine
  Remote: Yes
  Willing to relocate: No
  Technologies: TypeScript/React, JavaScript, HTML, CSS, Jest, Node.js, and all other parts of modern frontend stack.
  Résumé/CV: https://drive.google.com/file/d/19a7Wi_AIN_Z3BvJFVtAJPDKcD-m4XmZC/view?usp=sharing
  LinkedIn: https://www.linkedin.com/in/stasgavrylov/
  Email: stasgavrylov@gmail.com

Senior frontend engineer / lead with 7+ years of broad experience. For the last 6 years I've been building SPAs in React (mostly) for startups and enterprises, leading and owning frontend development on most of the projects.

I'm looking for a full-time remote position in a tech-oriented startup (preferably). Also, possibilities to grow to full-stack are welcome.

  Location: Ukraine
  Remote: Yes
  Willing to relocate: No
  Technologies: TypeScript/React, JavaScript, HTML, CSS, Jest, Node.js, and all other parts of modern frontend stack.
  Résumé/CV: https://drive.google.com/file/d/19a7Wi_AIN_Z3BvJFVtAJPDKcD-m4XmZC/view?usp=sharing
  LinkedIn: https://www.linkedin.com/in/stasgavrylov/
  Email: stasgavrylov@gmail.com

Senior frontend engineer / lead with 7+ years of broad experience. For the last 6 years I've been building SPAs in React (mostly) for startups and enterprises, leading and owning frontend development on most of my projects.

I'm looking for a full-time position in a tech-oriented startup (preferably). Also, possibilities to grow to full-stack are welcome.

It's open source and they're actively looking for contributors.

Great resource. I'm wondering whether the examples are your own or copied from across the web?

I just wanted to point out that some of them are a bit outdated, and I belive it'd be nice to maintain this list as a reference with modern approaches.

For example, there's no need to use `appendChild`, because DOM today has a more versatile `append` method.

And `[].forEach.call(cols, function(col) {...}` would look much better and more declarative as `for (const col of cols) { ... }`.

These are just first 2 examples that I noticed.

Your proposed changes are not supported in IE 11. The snippets are advertised as IE 11+ compatible on the landing page.

You're correct, but let/const don't have full support in IE11 either. I understand that people are still supporting IE, but still, this website could stay relevant longer if the examples were written in ESNext.