2024-06-15 01:58 UTC
@polotek@polotek.net @agocke@hachyderm.io +1 to all of this. TS is helpful in orgs w/ a lot of scale, and most teams are *deeply* confused about where they sit on the continuum. If you have less than 50 frontend folks contributing code to the same repo on a daily basis and less than 1 full-time infra person, TS is hard to justify given the upgrade treadmill.
Replies (1)
-
@slightlyoff@toot.cafe 2024-06-15 02:00
@polotek@social.polotek.net @agocke@hachyderm.io On the upside, TS doesn't obscure your relationship to DOM by default (except via the need to then pull in a bundler). Unfortunately, very few teams have the discipline to use TS *without* the usual JS framework cruft. The best I can think of here is the VSCode team, who are baller, and stay top of their game by being *extremely* intentional about these choices and investing deeply in the infra they *do* pick up.