This is not Vim fault per se. I am not sure what exactly Vim exposes as API to create syntax highlights, but to create accurate themes is a not so easy. Also, is time consuming task.
Yesterday I started to port (to port, not to create from scratch) a VSCode theme to (n)Vim and I can relate that the raw experience is not so thrilling (but I wonder if VSCode would recognize any syntax without specific implementation).
I now decided to rely on language packs (specific syntax/regex/etc implementation) and the (n)Vim colorscheme is getting almost exactly as the original VSCode theme (I still have to cover a few edge cases).
In general, vim-polyglot (or specific syntax highlighting / indentation bundles) + a decent colorscheme should help to avoid aesthetics nightmares.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is not Vim fault per se. I am not sure what exactly Vim exposes as API to create syntax highlights, but to create accurate themes is a not so easy. Also, is time consuming task.
Yesterday I started to port (to port, not to create from scratch) a VSCode theme to (n)Vim and I can relate that the raw experience is not so thrilling (but I wonder if VSCode would recognize any syntax without specific implementation).
I now decided to rely on language packs (specific syntax/regex/etc implementation) and the (n)Vim colorscheme is getting almost exactly as the original VSCode theme (I still have to cover a few edge cases).
In general, vim-polyglot (or specific syntax highlighting / indentation bundles) + a decent colorscheme should help to avoid aesthetics nightmares.