70 karma · joined December 17, 2016
If you have to re-engineer all your code to avoid content shift, why bother using a mega-framework like Next in the first place? Also the point of SSR and hydration is to improve performance and page loads, if you have a ton of work to do again on the client that's very small actual performance gains, but that's not so much of a surprise considering Next is one of the heaviest frameworks out there (in bundle size)
Script and sources: https://docs.google.com/document/d/1MZinEbqdCyvssBWHsX2Qjrv9...
French researcher and youtuber Lê Nguyên Hoang tries in this video essay to demonstrate that the ML research community is plagued by unfounded claims of algorithms being privacy-preserving, and lack of accountability over ethical concerns. This video seems to be the continuation of papers co-authored by Lê:
> SoK: On the Impossible Security of Very Large Foundation Models https://arxiv.org/abs/2209.15259
> An Equivalence Between Data Poisoning and Byzantine Gradient Attacks https://proceedings.mlr.press/v162/farhadkhani22b.html
Basically because MDX mixes JSX and markdown, you need knowledge of JSX/JS (which non-devs might not have), and tooling dedicated to build, parse it and so on. Markdoc is more of a "separation of concerns" approach.
But I agree that having in native apps the UI patterns people are used to seeing in webapps is simpler for the majority of users.
iirc Webpack uses it extensively in its codebase