ShellfishMeme
Joined 14 years ago
Joined 14 years ago
So they never make the change easy because every change is easy to them... until the lack of structure and re-use makes any further changes almost impossible.
That fried another device when I plugged it in.
This is non compliant in the EU, but when I reported it to the responsible authorities, they didn't feel like doing anything about it.
We are talking about a charger that can fry any device and potentially cause a fire, coming with a product aimed at people with babies, that's clearly non compliant to be sold in the EU, and they are doing nothing at all. Pretty shocking if you ask me.
Instead, no real improvements are coming to iPad OS and if you're not gaming or video editing, all you get to do is marveling at how powerful your YouTube player is in benchmarks.
Please Apple, let the Pro device finally be a Pro device and let us use virtualization.
It integrates very nicely, has very low CPU idle usage and also lets you quickly spawn VMs with bidirectional file sharing set up.
Since I switched I haven't looked back.
If a developer can jump into an unknown part of a codebase and quickly see that following a certain structure will automatically make their code work for them without needing to read all the code first and double checking if it's just a random convention versus a strict interface so they don't reinvent the wheel or build code that doesn't fit in with the existing structure, then that's worth a lot and something you cannot simply cover with tests.
The best I can do is apply the categorical imperative influenced by my cultural context, upbringing and personal experiences.
useMemo returns a value which is the result of calling the function it is given once the dependencies change.
So useCallback is basically useMemo called with a function that returns a function.