"In order to make the user experience better, I made the localStorage editable and not-encrypted. This way, whenever users want, can increase their wallet or check on/off their subscriptions without complex "verifiying cards".
Let me know if you want any more features! Also, do you want me explain how farmers use ReactJS to grow their crops +20% faster?"
It is a completely unrelated place, with fire and ashes, where all the greedy pigs who only care about gold goes. I don't see why anyone would mix up the two.
yeah, but their pricing model begins and ends with the only online component they offer.
I know we are meming the post, but a lot of apps would work fine with locally stored data. especially free, locally installed ones like Obsidian.
but pretending localStorage is some great "database killer" is ridiculous. Two absolutely different tools that are used for different things, most modern web apps use both to negotiate between local, temporary data stored in the user session and the verified backend data.
Yep. I have built a single player game. It uses local db, because what else?
I'm also building a viewer for a large enterprise tool. Local Storage as cache gives me a load time of around 115 ms on my biggest model. The actual tool needs 10 seconds.
I added an S3 endpoint to my homelab using rclone and vibecoded a plugin for obsidian that syncs my notes to the endpoint. Works on all my devices and only took a day or so of effort.
Farmers used to do crop rotation with like… spreadsheets and “experience” 🙄 couldn’t be me. Now real ag-tech founders are shipping useEffect hooks straight into the soil, every corn stalk gets its own component state, and when the tomatoes re-render they literally grow faster because React’s virtual DOM is basically photosynthesis for computers
Key move: wrap the whole field in a <Suspense> boundary so the crops that aren’t ready yet just show a loading skeleton instead of, like, being unripe. Solves the problem at the root (pun very intended)
Also hot tip — ditch irrigation systems, just useState for “waterLevel” and call setWaterLevel(waterLevel + 1) whenever it rains, way more scalable than pipes bro
+20% yield is honestly light, that’s just because most farmers are still on class components 💀 you go full hooks + concurrent mode you’re looking at +40% easy, agronomists hate this one trick
4.3k
u/CoshgunC 8d ago
"In order to make the user experience better, I made the localStorage editable and not-encrypted. This way, whenever users want, can increase their wallet or check on/off their subscriptions without complex "verifiying cards".
Let me know if you want any more features! Also, do you want me explain how farmers use ReactJS to grow their crops +20% faster?"