We bought a shuttle bus in California, ripped out most of the seats, put in beds, then drove it over to Florida and back again. Literally hours away from flying back to Australia tonight. I’ll go through and review each site on Campendium when I have a minute.
@isaacforman on IG for anyone interested. Lots of action in the stories.
We camped in a mixed of national parks/monuments, state parks, water authority areas, BLM, etc.
I've often had to resort to google satellite photos and referenced flat dirt patches with BLM territory maps to make sure I wasn't on private land. Wish there was an easier way.
For $280, right this second, you can buy a Pocophone F1 from Amazon which has essentially the same size screen as the Pixel 3 XL, 6GB RAM, an SD845, an SD card slot and decent support from Xiaomi so far. Hell, the beastly Razer Phone 2 is only $499 right now and has some crazy specs relative to the 3a XL.
I know I'm dreaming but Google needs to get back to what made it great in the first place: Put flagship specs into midrange priced phones.
And then, if you are doing anything full stack or have a middleware/backend-for-frontend, for god's sake, look into tRPC and let your mind be blown.
Putting these two together, in a simple vite project (no full stack "framework" needed"), it will seriously just change the way you look at data, loading, and API interactions.
It just feels somewhat like the OP's problems with React are all skill issues and a lack of desire to explore and learn correctly.
I think the author is kind of a mediocre frontend eng but it's also true that modern react + hooks are full of footguns that can get very ugly. It's the opposite outcome of what react was originally designed for, to make it easy to do the right thing.