The issue he had with the “move to” operation is that it forced you into a mode where you had to pick a destination right away. I wonder if OP’s proposal was ever brought up at the time—it does seem like a promising middle ground!
To be clear, you’re advocating for women to lose the right to vote? The misogyny in this thread was disappointing already, but seeing this comment being voted up is maybe a sign I should not be on this website any more.
The article points out that the problem is deeper than this:
> Once I compared my personalized sloper to commercial patterns and retail garments, I had a revelation: clothes were never made to fit bodies like mine. It didn’t matter how much weight I gained or lost, whether I contorted my body or tried to buy my way into styles that “flatter” my silhouette, there was no chance that clothes would ever fit perfectly on their own.
I was surprised at the audible difference it made to reset the RNG seed for the hi-hat noise function every time it triggered. I’m curious what the justification for doing this is—does the randomness arise from the geometry of the hi-hat itself and not the way you hit it? Is the idea to imitate the sound of sample-based percussion?
He’s also built a popular movement invested in getting his policies implemented. He may not “control the busses” as an individual government official, but his movement can pressure the people who do.
Apple relies on internal feedback and executive reviews rather than user testing. They likely received a lot of different feedback internally, but the execs decided to ship it anyway. I think they would rather ship something half-baked than change the yearly release process that has been continuously operating since the early days of iOS, and at the scale of the whole platform, it's hard to turn back once you've committed to making the changes.
This sounds nice until you think more closely about the framing implicit in “follow the rules and make the nation better”. Who makes the rules and defines what is good for a nation?
The correct way to do "anticipation" is to apply it as something is being pressed, then finish the animation on release. Putting both together in a single easing function is missing the point, IMO.
It’s frustrating to have to find the right place to report a bug, learn the specific format the project is expecting, then have the bug closed by a “stale bot” after a few weeks. I wish there were an independent, cross-product bug tracker that focused on cataloguing and diagnosing bugs for the benefit of users rather than on tracking work for the benefit of the developer.
Also, be angry at those who didn't follow through with promises to severely reduce funding to their police departments in 2020. If an organization consistently behaves in a way we don't like, we should seek alternatives to that organization, not continuously act surprised when they act out and keep giving them more money.
The problem with adult-only transition is that it dooms trans people (at least, those who go on HRT) to go through two puberties, which has visible physical effects that then have to be undone or worked around (breast growth, facial hair, deeper voice, etc.). The ideal for most people is that you'd just go through one.
One possible resolution is that these interests are male-dominated not because of an inherent gender-based preference, but because women (or, more precisely, people who are perceived to be women) are excluded from them. Trans women who are still perceived as men are able to avoid some of these exclusionary processes, and they maintain their interest even after they start to be seen as women.
I wrote something similar a while ago for doing lon/lat -> congressional district reverse geocoding. Instead of simplifying the polygons, it splits the U.S. into tiles using a k-d tree and fetches the proper tile as a static file to do the final lookup: https://github.com/ianh/district-tiler
Swift wasn't designed to solve any of the problems Apple engineers had writing customer-facing software. It was a shiny new language which could be marketed to third parties as something modern and familiar, unlike Objective-C with its odd mix of C and square brackets.
Another cool thing you could do is fuzz test a version of the code that actually does take both branches (in separate runs with fresh memory etc.) and aborts if they give different results.
If you don’t mind explaining, I’m curious how you test something like this before it goes live. It seems like it would be hard to simulate all the things that could happen at scale.