Changed my mind about VS Code extensions after a month of fighting with setup

I was dead set on keeping my editor bare bones because I thought extensions just bloat things. Spent about 3 weeks manually formatting code and hunting for typos. Then a buddy showed me how Prettier and ESLint catch errors before you even run the file. After trying them for 2 days, I'm sold. Anyone else hold out on tools like this for too long?

2 comments

2 Comments

josephs262d ago

3 weeks manually formatting code? Dude that is brutal. I almost lost my mind after just 3 days of doing that before I caved and installed Prettier.

miller.paul2d ago

Prettier actually broke one of my projects last week by reformatting a chain of ternary operators into something completely unreadable. I spent 45 minutes undoing its changes line by line because it kept fighting with how I wanted the logic structured. ESLint is nice in theory but half the time it flags stuff that works perfectly fine in production, so you either disable half the rules or waste time fixing things that aren't broken. Meanwhile I can write a clean file in vim with no plugins in under 10 minutes and know exactly what's gonna happen when I run it. Not saying bare bones is for everyone but there's something to be said for knowing your tools inside out instead of letting extensions think for you.