2 ms·
>The obvious tradeoff for a buildless workflow is performance. We use bundlers mostly to concatenate files for fewer network requests generally small parallel
by bryanrasmussen 2y ago
>The obvious tradeoff for a buildless workflow is performance. We use bundlers mostly to concatenate files for fewer network requests
generally small parallel requests perform better than large single requests in a modern situation - modern browsers, HTTP 2+ etc. - in my experience - but there can be a lot of caveats about that statement.
However the import statements in the css are not downloaded in parallel last time I checked - and probably never would be because of ways css works, so this using import statements inside css instead of having a build of a single css is actually the worst possible solution I think (ok there is probably something even worse that you could build if you really wanted to but worst "reasonable" solution)
- hinkley 2y agoThe goal of buildless is to avoid friction in the code-build-test cycle. There are time cutoffs beyond which the human brain tries to multitask, and the multitasking involves making multiple adhoc estimates per hour, which we all know are always off by 2. Every three minute pause wants to become six. So the trick is if you can keep the build to seconds you don’t change your workflow. Which means you might be able to pick one transpiler like Less, and throw a watch on it, and still be fine. As long as, that is, you make a cultural decision not to go fucking nuts with the CSS. You need a low threshold for triggering tech debt cleanup.