3,485 karma · joined August 10, 2017
Apple chose not to allow people to keep a cable connected not just for the aesthetics but also to keep them from reusing existing cables (instead of an hypothetical lightning mouse cord) and getting a poor UX.
It's pretty infuriating and definitely an intentional dark pattern.
Prioritizing fixing old bugs over developing new features isn't a call an IC can really make so I'd kinda argue that the issue is either "overstaffed with designers+execs who spend engineer time on UI changes" or "understaffed with engineers in general" and not an issue with the mindset of the current engineers.
If that changes I'll regret having used 23andme, but so far I'm not worried.
Calling memcpy with an arbitrary value always has to call out to libc but a specific value can be inlined into a single instruction or two for smaller values, so you can have an if-else chain or switch with a few common ones for your program and it's a noticeable speedup.
You should, considering it's really the only bottleneck to getting more perf
I feel like this entirely disregards the caching costs of using >2x more memory in some cases, speed of float32 vs float64 operations on CPU, and potential CPU <-> GPU memory transfers.
EDIT: Nvm disregard this comment, I just noticed the existence of: PackedByteArray, PackedInt32Array, PackedInt64Array, PackedFloatArray, PackedDoubleArray
Anything set of numbers needed by the GPU or big enough to affect the cache will probably use those arrays.
Also, your implication that a company is performing illegal activity just because they're successful is rude and uncharitable at best.
- Multiple cameras per eye, and at a very short distance from your eye
- The screen is fixed relative to the cameras for all devices, there's no worry about that half of the equation getting off calibration or differing for every customer
- OS is built around eye tracking, which means there won't be any actions that are unnaturally hard to perform with eye tracking
Because of that, I'm also sure that eye tracking will go mainstream in other areas once the Vision Pro is released once everyone else catches on to it as a great input method.
E.g. you could use this in your GitHub Pages site, which is just served from a CDN without any real backend.
You are comparing one of the easier languages to write a compiler for (C) with one of the hardest (Rust), and that's not due to UB but due to other facets of the languages. I could make up a new language that's equivalent to C in every way except replace all UB with defined behavior and it wouldn't make the naive compiler any different.
Additionally, writing a compiler for a language should really be a thing that happens only a handful of times while executing the code happens trillions of times so I hope we don't sacrifice safety to save compiler authors some work.