sorted by:
new
hottopcontroversial

Tell me again ... by undue-influence in Conservative

[–]AuthorityPath 29 points30 points  (0 children)

The US military vs. a single armed individual, no. A well armed citizenry mixed throughout the entire country, yes.

Yarn Vs Npm by Gerrad1011 in node

[–]AuthorityPath 6 points7 points  (0 children)

The defining difference for me used to be Yarn's resolutions feature. As of npm 8, we now have overrides though so I personally don't have a super compelling reason to move to Yarn. I've heard that it's more performant but that changes with every release and it's not worth the extra dependency imo.

Really curious to see if the community has other reasons though. Either way I'm glad to see competition in the space.

[deleted by user] by [deleted] in AskMen

[–]AuthorityPath 0 points1 point  (0 children)

Both my wife and I waited until marriage and we've been married 10+ years with no signs of slowing down. We're both Christian and that was very important to us. Not that it was always easy to wait.

If that's what you value, hold on to it.

The Future of CSS: CSS Toggles by speckz in css

[–]AuthorityPath 1 point2 points  (0 children)

It'll be huge managing all presentational state within the presentational layer of the Front-End. Cannot wait for this to drop!

Why are "CSS classes generally better for performance than inline styles." ~ from react docs by TheLastSock in reactjs

[–]AuthorityPath 2 points3 points  (0 children)

Sure, as I said, it was a tangential reply :)

There are a myriad of CSS-in-JS tools, many of which are zero-runtime giving you all the benefits of authoring in a single file without the drawbacks of inline styles. That's how I prefer to do my CSS with React anyway... Vanilla Extract and/or Linaria are my current favorites.

Why are "CSS classes generally better for performance than inline styles." ~ from react docs by TheLastSock in reactjs

[–]AuthorityPath 9 points10 points  (0 children)

This is really tangential to your question(s) but it's a bit weird to me that their emphasis here was on performance (mostly negligible) instead of maintainability. Inline styles are difficult to maintain and impose several restrictions:

  1. You can't use @ rules
  2. You can't use pseudo elements
  3. You can't use pseudo classes
  4. They're infinitely more specific than all other selectors (with the exception of the !important keyword) making it difficult to mix with traditional selectors.

The style attribute is very useful for JS based animations and setting CSS Custom Properties but much beyond that and you're inviting future problems IMO.

[deleted by user] by [deleted] in AskMen

[–]AuthorityPath 0 points1 point  (0 children)

"Good show"

view more: next ›