@melroy @NanoSector Honestly, I've found ESLInt to be more of an annoyance than anything.
The amount of indentation is managed by Prettier most of the time. Plus, ESLint (even with the TypeScript-specific rules) fails to recognize edge-cases.
One very annoying oversight is how it handles TSDoc imports: if you import a type only to reference it in TSDoc (think @link, or @see) it claims the type is unused -- this goes against what TypeScript says.
In this specific case, it feels a bit strange to have TypeScript saying one thing and ESLint saying something completely different.
Totally off Twitter now so introducing myself
I'm &y, software engineer really into #golang & #javascript and lifelong learner in tech in general. Love teaching what I learn in tech, and you can find my blog on dev.to/andyhaskell. I also just spoke at #GopherCon a couple days ago abt @charmcli's fun #BubbleTea TUI framework!
Also #ActuallyAutistic and passionate about advocacy to demystify #neurodiversity and make the future more healthy and inclusive for people of every neurotype!
@rachel_norfolk @brucelawson Definitely!
Don't even get me started on blogs that fetch and parse Markdown in-browser. Boggles the mind.
@rachel_norfolk @brucelawson Ahh, this is such a good take -- I've always thought doing as much as possible during compile-time is the best choice.
After all, isn't that the whole point ...? There's a counter argument that we shouldn't have to compile websites at all, but IME that just makes things harder for content-oriented stuff :/
&y HaskellSymbol.species and some spec talk around it, and I have to say... I'm absolutely baffled. #javascript