The dots do help a little, but not much. I wouldnt use my phone for long while in a vehicle, though at the very least I no longer dread having to briefly read a text message if I have to.
I found your note on bad drivers interesting. For me, it's the quick acceleration, braking and turning that's the worst. A bit anecdotal, but I also experience car sickness less with women drivers. Maybe because they're usually easier on the acceleration and brakes?
The double space after a period, with the added effort to avoid browser whitespace condensing, is an interesting style choice. Is it meant to mimic old academic publications?
While present in some of their previous articles sparingly, this is the first one to use it consistently.
> What should this function be named? I didn't care. Where should this config live? I didn't care. My brain was full. Not from writing code - from judging code.
Does it matter anymore? Most good engineering principles are to ensure code is easy to read and maintain by humans. When we no longer are the target audience for that, many such decisions are no longer relevant.
Of course it could have been done without Svelte. Thats the only stack their team know and/or wanted to work with. Nothing wrong with that, but would be nice if they were more upfront about that instead of "impossible for a different solution to exist".
There was a psychological term for it, making a decision first and only then finding supportive arguments in favour of the decision?
> I've found that people that learned class-based React first and then switched to modern function-based React often have more trouble with useEffect than people who learned functional components directly
I’d say its the opposite; people who used lifecycle methods know that useEffect and friends eliminates an entire class of bugs. People who started with hooks dont understand the problems it solved, and only see the quirks