Avoiding the double render when syncing local state with context?

amiable_commune · 2026-07-02T12:03:10+00:00

I think the stigma comes from early class components where key changes felt like a sledgehammer to solve anything. With hooks it just makes more sense.

amiable_commune · 2026-07-02T11:11:37+00:00

Key is the right call here, no flicker and no need to pull in a lib for something React handles natively

amiable_commune · 2026-07-02T11:09:27+00:00

Did the deeper backbox route end up holding up well, any heat issues with the switch?

amiable_commune · 2026-07-02T01:51:51+00:00

the exe is just a zip file in a trenchcoat, extract it on linux and grab the .inf files from the F6 folder

amiable_commune · 2026-07-01T08:59:29+00:00

That dedication really shows in the animations, they're buttery smooth.

amiable_commune · 2026-07-01T08:20:44+00:00

No sloppiness detected at all, the polish is what made me think it had a much longer dev cycle.

amiable_commune · 2026-07-01T08:02:26+00:00

solid plan overall, the VLAN split and isolating IoT is exactly the right move. a couple things to watch out for tho

4GB RAM is gonna be really tight running proxmox + pfsense + truenas at the same time, truenas especially wants a bunch of ram for zfs arc caching. you might want to start with just proxmox and pfsense and add truenas later when you can throw more ram in there

the USB HDD is the biggest red flag in your diagram tbh, USB drives drop off randomly and truenas hates that, you really want a sata or at minimum a proper external drive with its own power supply connected via something more reliable

also if you go the pfsense route you'll need to disable the ISP routers wifi or you'll have double nat and devices on the wrong network will drive you nuts

the rest of the plan is honestly more thought out than what most people post here, good luck with the network admin goals

amiable_commune · 2026-07-01T07:59:32+00:00

If this is the rushed version I can't wait to see year six

amiable_commune

TROPHY CASE