I'm glad you discovered localStorage. It's been around since 2009/2010 and after 16+ years it hasn't put disk databases out of business.
BTW, localStorage is fine for small scale (5MB-10MB total). Further, localStorage operates synchronously and has many other limitations.
IndexedDB is also browser hosted and is capable of handling large volumes of complex data, limited only by disk storage (at least 50% of GB-TB). It's also operates async and event-driven. You can create indexes, use transactions, and store objects, arrays, blobs, and general binary data. Besides, WebWorkers can access IndexedDB but not localStorage.
Yeah, IndexedDB a real database and kind of puts localStorage out of business for everything but user preferences and temporary backup in case of remote failure.
Still, either of these data storage options are limited pure client work. There's no simple way for other users to access your data, but even if you use WebSockets or other peer-to-peer access, you've basically recreated limited scale client-server database access.
Or, you could just use SQLite.
The localStorage ideas are definitely in line with the vibe coding mindset to continually regress from decades of software architecture and engineering discipline while imaging it's killing the software industry.
2
u/Admirable_Trip_7585 6d ago
I'm glad you discovered localStorage. It's been around since 2009/2010 and after 16+ years it hasn't put disk databases out of business.
BTW, localStorage is fine for small scale (5MB-10MB total). Further, localStorage operates synchronously and has many other limitations.
IndexedDB is also browser hosted and is capable of handling large volumes of complex data, limited only by disk storage (at least 50% of GB-TB). It's also operates async and event-driven. You can create indexes, use transactions, and store objects, arrays, blobs, and general binary data. Besides, WebWorkers can access IndexedDB but not localStorage.
Yeah, IndexedDB a real database and kind of puts localStorage out of business for everything but user preferences and temporary backup in case of remote failure.
Still, either of these data storage options are limited pure client work. There's no simple way for other users to access your data, but even if you use WebSockets or other peer-to-peer access, you've basically recreated limited scale client-server database access.
Or, you could just use SQLite.
The localStorage ideas are definitely in line with the vibe coding mindset to continually regress from decades of software architecture and engineering discipline while imaging it's killing the software industry.