iphone 8 plus, bought refurb in early 2019. replaced the battery once (and got a replacement since the battery wouldn't pair). it's getting to be time.
usb-c is a big feature increment for me, and I need to finish the leap away from google voice, since I absolutely know they are not going to bother implementing RCS and will just shutter the service instead. LiDAR also seems extremely useful/cool. On the other hand, I was kinda hoping for thunderbolt support on the pro models eventually. Not sure if I will buy a refurb 15 Pro or a new 16 Pro Max or wait for the next cycle.
that's how you avoid e-waste for real and not as a fashion statement. simply consume less - and that includes not consuming a $300 android phone every 18 months, not just apple - and have it repaired when it needs it. with OEM parts that will last the long-haul and not something off amazon that will need to be changed again in 6 months.
I have been taking 300mg of Magnesium Bisglycinate 30 mins before sleep for the past 5 months or so. I have anxiety which can lead to insomnia. It has been a great help.
It could be that you have an anxiety disorder, obsessive personality disorder or OCD. Or perhaps not, but the obvious red flag is trouble sleeping. If you’re typically a good sleeper but find yourself sleepless when in one of your spirals it's a good indicator that you need to take a step back, take a deep breath and reset your mental state because its not the refactoring thats not letting you sleep its all the stuff that you have built up in your head.
Also complete rewrites in general are overwhelming and tend to turn out not the way you imagined anyway. Small incremental improvements and isolated refactors over a sustained period of time yield the best results.
D3 is from jQuery era so there are a lot of methods for manually manipulating the DOM like d3.select() and then selection.attr() etc. but those patterns tend to lead to components that are lengthy, hard to read and hard to maintain. Arguably a better approach is to group each D3 module based on whether it "modifies DOM" or "doesn't modify DOM". Then use React/Svelte to declaratively render the DOM and only use the D3 modules from the latter group for their math utilities.
I’ve been using D3 on and off for quite some time. I’m just starting now with react and visx definitely looks very promising as it bridges the gap nicely. Do you find it limiting though (like you have to fight the tool) to achieve something more custom vs. using plain D3?
VisX starts with low-level primitive components that match very closely to D3 primitives. It then builds some chart primitives on top of those and then builds some charts on top of that. You can build pretty much anything using the lowest-level primitives and still have a better developer experience than D3 IMO.
If you don't need any real customizability (and know you won't need it in the future), I'd stick with something with something less customizable, but faster to setup. If you know you need custom, take the 10-20% more time to setup and be able to change in the future as that'll be faster than porting your charts over.
Why spread misinformation?