What's everyone's obsession with storing everything in…
0 reactions
What's everyone's obsession with storing everything in localStorage?
Stop treating localStorage like a BOTTOMLESS PIT!!
This is my 3rd employer where I have dealing with a production outage caused by a `QuotaExceededError` (DOM Exception 22), and it's incredibly frustrating how avoidable this is. Developers keep digging this grave because they treat client-side storage as if it’s free real estate. It isn't. It’s a strictly limited resource, and most of what is being shoved in there like massive base64 strings for "image caching" or bloated analytics objects simply doesn't belong there.
If you’re storing entire LaunchDarkly objects on every render or piling up Snowplow events in localStorage, you’re building a ticking time bomb. It’s not "free" just because it's convenient. You are effectively breaking your application for the sake of lazy architecture.
Take a moment today and ask your AI agents to wrap your `setItem` with a `try-catch` blocks so you don't crash the entire app when the limit is hit. Better yet, use SessionStorage for data that doesn't need to outlive the tab, or move to IndexedDB if you genuinely need to handle large datasets. Stop treating the browser like a dumping ground and start respecting the limits of the platform.
#technology #programming #dev
source
Stop treating localStorage like a BOTTOMLESS PIT!!
This is my 3rd employer where I have dealing with a production outage caused by a `QuotaExceededError` (DOM Exception 22), and it's incredibly frustrating how avoidable this is. Developers keep digging this grave because they treat client-side storage as if it’s free real estate. It isn't. It’s a strictly limited resource, and most of what is being shoved in there like massive base64 strings for "image caching" or bloated analytics objects simply doesn't belong there.
If you’re storing entire LaunchDarkly objects on every render or piling up Snowplow events in localStorage, you’re building a ticking time bomb. It’s not "free" just because it's convenient. You are effectively breaking your application for the sake of lazy architecture.
Take a moment today and ask your AI agents to wrap your `setItem` with a `try-catch` blocks so you don't crash the entire app when the limit is hit. Better yet, use SessionStorage for data that doesn't need to outlive the tab, or move to IndexedDB if you genuinely need to handle large datasets. Stop treating the browser like a dumping ground and start respecting the limits of the platform.
#technology #programming #dev
source
| 0 mlx | |
| 0 | |
| 0 |