My initial ~/.vimrc for #vim after 3-4 years of using #neovim:

filetype plugin indent on
syntax enable

let g:mapleader = ","

set autoindent
set autoread
set formatoptions+=j
set guifont=MesloLGM\ Nerd\ Font\ Mono\ 12
set hidden
set history=500
set hlsearch
set listchars=tab:→\ ,trail:•,extends:›,precedes:‹,nbsp:␣,eol:↲
set nobackup
set nonumber
set noswapfile
set nowrap
set path+=**
set scrolloff=1
set showbreak=↪\
set showmatch
set sidescroll=1
set smarttab
set tags=./tags;/
set termguicolors

nnoremap <silent> <C-l> :nohl<C-R>=has('diff')?'<Bar>diffupdate':''<CR><CR><C-L>
nnoremap <silent> <leader>lcd :lcd %:p:h<CR>:pwd<CR>
nnoremap <silent> <leader>n :set number!<CR>

if !empty(globpath(&rtp, 'autoload/plug.vim'))
  call plug#begin()
  Plug 'ap/vim-buftabline', { 'as': 'buftabline' }
  Plug 'dracula/vim', { 'as': 'dracula' }
  Plug 'editorconfig/editorconfig-vim', { 'as': 'editorconfig' }
  Plug 'kaarmu/typst.vim', { 'as': 'typst' }
  Plug 'tpope/vim-commentary', { 'as': 'commentary' }
  Plug 'vim-scripts/git_patch_tags.vim', { 'as': 'git_patch_tags' }
  call plug#end()
endif

silent! colorscheme dracula

It’s quite short but does pretty much what I would ever want from a text editor:

$ wc -l .vimrc 
42 .vimrc

@jarkko yeah mine was pretty similar. All in one file with vim script code. Actually I think I saved it in some part as well.

@jarkko Not sure why you're still using NERDTree; Vim's built-in file explorer is much superior.

@seve_py I was thinking the same actually today ;-)

@seve_py after doing some work for few days i stripped down the stuff that i don't need. just wanted see what kind of fancy stuff is out there ;-) [see above]

I love that I don't need cross my fingers every time the plugins update to a new version, like I had to with neovim for past four years :-) Often a plugin update could cause editor to collapse if it wasn't a bleeding edge version.

@jarkko Unfortunately, this also happens with Vim, although probably less frequently. Developing a plugin for various platforms is not trivial, and maintenance can be a significant burden.

@seve_py It happens with any software sometimes but with lower probability with vim than neovim.

Especially if you want to use your text editor on remote machines, neovim can be a bitch... One big reason for returning back to the roots so to speak.