vim is arguably the best tool for editing large, self-contained, "rollup"
files like bootstrap.css, jquery.datatables.js, highcharts.js, jslint.js,
etc. it (and emacs) are the few mainstream editors i'm aware of with
search-as-you-type and bookmark-location functionalities, enabling
sub-second tra
Really?! That actually surprises me!
I haven't used vim to develop for quite a while, but always saw it as a
reference in performance.
For instance, I'm right now with 5 different VSCode windows opened (each
one with a different workspace, for each project I'm currently working on),
and each of t
My anecdotal data point is I use Netbeans to build my javascript 3D engine, all
in modules (where each module is a single class where the class definition is
the default export.). This works really well for me, the only problem being the
regular nature of the language problems. Hundreds of file
i agree vim is efficient for switching between existing files/buffers. but
*opening* new files is a PITA, which subtly affects programming-behavior of
its users -- towards javascript-programming tending less towards
fragmenting code with multiple files/modules (and more towards
code-locality).
on
I would agree for Vim in its basic form but have successfully used vim, for
several years, with the Ctrl+P extension to quickly and efficiently get
around codebases with many files. It also has a buffer lookup for accessing
already open files, and other shortcuts like Ctrl+B/Ctrl+6 make switching
b
3 frontend-devs is reasonable and maybe ideal -- but reality is most shops
can only afford 1 frontend-dev. i remain convinced 5 js-devs is around the
practical limit for most products. going over that magic-number, and
people become confused about their areas-of-responsibility -- allowing
mediocr
As much as I like vim, this seems like more of an argument against using
vim than anything for the language - also it's not "usually" just 1
frontend developer; altho that may be your experience. I often like to say
it's *never* just one - even if it's you, it's also "you in 6 months", and
that per
adding a datapoint on effects of vim-editor on my javascript coding-style.
this is to expand on discussion of "JavaScript and Syntax Research Methods"
in tc39-notes [1].
vim has the following file-editing properties:
1. poor UX in opening new files
2. efficient content-search/jump/traversal of lar
8 matches
Mail list logo
