3 ms·
I have transitioned my entire team (comprising people ranging from fresh-out-of-a-bootcamp to senior 20-years-in-the-web). Next.js and GraphQL are interesting
by kilburn 6y ago
I have transitioned my entire team (comprising people ranging from fresh-out-of-a-bootcamp to senior 20-years-in-the-web).
Next.js and GraphQL are interesting technologies, but I would say they will eventually fade. They do solve some problems, but they introduce new (hard to fix) ones.
Typescript is here to stay. The improvement it brings to the development experience cannot be understated.
It helps the inexperienced to avoid lots of (minor) bugs and providing much more useful autocompletion/inline docs than any javascript analyzer can.
For the experienced people, it is an invaluable tool when the time for largeish refactorings comes. For the first time you can "follow-the-trail-of-errors refactor" in frontend-land.
- shriek 6y agoThis question probably varies on who I'm asking but how long does the transpiling process take for you on a, let's say, fairly large project?
- kilburn 6y agoWe were already using Webpack + babel. Adding transpilation there is fairly inexpensive (done by babel, without type checking). Type checking did roughly double our build time. Even then, we do run type checking during builds because we prefer the added safety even with this extra time. Developers run with an incremental checking watcher. It does add a significant tax, and takes a few seconds after saving in some cases (3-4). We would love that delay to go away, but it is a cost we are more than willing to bear if the alternative is not having type checking at all.