On: State of JavaScript 2020

[worble]

>All the front end devs are like, "You have to wait how many minutes for compile times?" for instance.

This is funny because waiting for typescript to build is probably double or even triple waiting for my .NET project to compile at this point. I swear it gets slower every update.

[robin21 → worble]

Yeh Babel and webpack blow out compile times to epic proportions.

Any app that grows to a certain size will slow down to a crawl on incremental builds.

[esperent → robin21]

Try esbuild. I thought the following benchmarks must be fake until I tried it myself.

https://raw.githubusercontent.com/evanw/esbuild/master/image...

[robin21 → esperent]

I really can’t believe that.

But I will try!

[astrod → robin21]

There has been some interesting tooling being written in Rust, swc[1] compiles very fast. Not quite production ready but getting there.

[1]https://swc.rs/

[_qwfv → worble]

I'm not familiar with TS compile times, most of the engineers I know working on FE code use JS.

[pjmlp → worble]

Thankfully on my projects FE and BE are separate builds, so I only do FE builds when needed, I save so much minutes.

[williamdclt → pjmlp]

Genuine question: in what sort of setup do you have a single build for your frontend and backend?

[pjmlp → williamdclt]

JEE and .NET, where the build takes care of handling JavaScript, CSS and HTML files, provided they are on the expected project layout structure.

Naturally I am not doing SPAs in this case, just vanilla JS and web components.

The FE/BE split builds are only in SPA projects, with BE being mostly about WebAPIs.