Your shopping website is not an SPA.
I repeat: your shopping website is not an SPA.
Stop trying to sculpt David with a JS chainsaw and get yourself an HTML/CSS chisel.
I repeat: your shopping website is not an SPA.
Stop trying to sculpt David with a JS chainsaw and get yourself an HTML/CSS chisel.
Like, it *could* be an SPA, in the same sense that one *could* use a solid rocket booster to power one's car.
How do I know it's ridiculous to apply this much JS to the problem?
Because I helped build e-commerce sites with similar features (filtering, carts, etc.) that had to work on 4.0 browsers over 33.6 modems to WebTV boxes in 1999.
Because I helped build e-commerce sites with similar features (filtering, carts, etc.) that had to work on 4.0 browsers over 33.6 modems to WebTV boxes in 1999.
So you're starting from the now-usual React/Redux/GraphQL/SSR disaster, what can you do?
Turn off JS on the client and keep the SSR. There will be things to fix, ofc, but you needed to fix them anyway for a11y and resilience.
Turn off JS on the client and keep the SSR. There will be things to fix, ofc, but you needed to fix them anyway for a11y and resilience.
"but we want interactivity!", you say.
OK. Find the *small* part of your team that owns performance and who will be the only people licensed to approve JS (preferably as web components you can drop into SSR output)
OK. Find the *small* part of your team that owns performance and who will be the only people licensed to approve JS (preferably as web components you can drop into SSR output)
Can you still make mistakes w/ that set of choices? Absolutely. But JS is special-occasion-food, and "full stack" is a lie, full stop.
You *must* put controls on your JS emissions.
You *must* put controls on your JS emissions.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
