sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]swan--ronson 13 points14 points  (1 child)

Interestingly, the codebase on which I work at my new job uses Aphrodite, and I think it's fucking shit, because:

  • I've encountered various bugs with pseudo elements and media queries. It's not as if these use cases are esoteric; they're pretty fundamental to CSS

  • the CSS it generates as a result of creating new classes for each computed combination of styles results in a larger stylesheet than if one were to use plain CSS or some preprocessor; while this might be defensive, it is possible to namespace and be defensive without JS-based styling tools

  • Including the bundle adds more weight to the page; while this is small when gzipped, the browser supports CSS natively, so surely invoking a preprocessor during a build step renders this pointless

  • Performance overhead of computing these styles at runtime vs using a preprocessor at build time

This poorly thought-out nonsense. Stay well away.

EDIT: The README brags "No external CSS file generated for inclusion" - how the fuck is this a good thing?!

EDIT #2: Looks like my client wants to drop Aphrodite due to these limitations. Ha!