{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihv5klmfdcig5eapzwe76nx67pfr73flsjoywrfg2aer4xf7m7thi",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mixopf2izya2"
  },
  "path": "/t/ann-css-class-bindings-library-generates-haskell-bindings-for-css-classes/13857#post_11",
  "publishedAt": "2026-04-07T18:08:34.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "dyaitskov:\n\n> how many ids do you expect on in an app you maintain?\n\nI tend to automatically use IDs instead of classes for things that I know will only appear at one position in the DOM. In theory at least, this makes CSS selectors more efficient. It’s also a slight aid to reading the CSS as a human. This is the first time I’ve found any downside to it. I don’t quite see the analogy with global variables.",
  "title": "[ANN] css-class-bindings library generates Haskell bindings for CSS classes"
}