{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreia6jqt7fiv4aq4dshwqxna4kyhfdco6tkrzoq7jshhgcvdnteiv7q",
    "uri": "at://did:plc:4n6wgsqsqm6q2hjncgwmreey/app.bsky.feed.post/3mj7s5wu67b22"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreifclr7sl4ixquuekrj6btctqtpna4xkp5gwxbvnzhifo2ecfasc54"
    },
    "mimeType": "image/png",
    "size": 40295
  },
  "path": "/post/48600519",
  "publishedAt": "2026-04-10T15:38:32.000Z",
  "site": "https://programming.dev",
  "tags": [
    "Web Development",
    "codeinabox",
    "webdev",
    "5 comments",
    "https://blog.logrocket.com/dx-shift-web-interoperability/"
  ],
  "textContent": "submitted by codeinabox to webdev\n8 points | 5 comments\nhttps://blog.logrocket.com/dx-shift-web-interoperability/\n\n> These days, developer experience (DX) is often the strongest case for using JavaScript frameworks. The idea is simple: frameworks improve DX with abstractions and tooling that cut boilerplate and help developers move faster. The tradeoff is bloat, larger bundles, slower load times, and a hit to user experience (UX).\n>\n> But does it have to work like that? Do you always have to trade UX for DX? And are frameworks really the only path to a good developer experience?",
  "title": "The DX shift no one noticed: Web interoperability"
}