3 ms·
Google Closure's advanced optimizations require annotations throughout your codebase- in many codebases it may require significant effort to get this working. W
by randomfool 6y ago
Google Closure's advanced optimizations require annotations throughout your codebase- in many codebases it may require significant effort to get this working. When you need that extra optimization it's great but can be a lot of effort otherwise.
I'm most excited about esbuild though and I'm curious how it'll fit into a larger codebase & ecosystem. The author is aggressive about keeping it simple (for good reason!!)- the focus on speed is awesome.
- lenz2020 6y agoActually no. You rarely need to annotate anything. They type checking is independent from the optimization of you turn off the type based optimizations. You still get good results. This doesn't get you away from the requirements for advanced optimizations (property use restrictions in particular).
- capableweb 6y ago> it may require significant effort to get this working You're right, the author probably didn't provide externs and/or exports, so the tests fails. It's not really that much of an effort, especially if you're supposed to be testing the tool itself. Considering that the author is already testing libraries that have externs/exports written for them already, just shows the lack of care of the tests.
- newlisper 6y agoGoogle Closure is the best at minification but it's also the worst less pragmatic option for 99% of projects.