f-word
Being able to stuff it on its own little instance with no "back" to go to would allow people getting a cursory look at it to divert attention from the whole usability etiquette and concentrate on the thing itself, plus there might be some interesting gains in doing so too.
One other thing I'd love to have is an interactive tutorial, I'd love to be able to follow some steps to understand the thing better.
For a statement noone thought to make until black people started asking to stop being wantonly murdered by cops and which only the sickest people would think to abuse into a "response" to such cries against what is in effect ethnic cleansing it does sure attract a lot of controversy.
Apple needs to be made to stop; clearly not just for this random crab app lol but their absolutely heinous business practices need to be put to an end.
The main reason this are used vs (or sometimes along!) other technologies is that they function rather happily in super crappy conditions we don't -unless some world-ending event happens soonish- usually have on Earth.
It simply should not be possible, this is about literal tons of money, they shouldn't rely on something this banal.
Simple safeguards can be put in place to prevent this. They don't even need to be very fancy:
Fairly sure a simple trained-human-readable description of what was about to happen (think: this money will go to this acct, this money here and this other money over there) would have saved this people a whole lot of grief.
How is this preventing me from recreating my own shit `random()` when it's entirely too late in the evening, deadlines are looming and the garbage office politics preclude me from disabling this asinine thing?
I used to regularly trip on this damned reified rituals where we're only supposed to use a single type of quotes, or maybe using short vars like `i,j,k` on for loops and other garbage "rules" that might have sounded great when originally put in place but are horrible on a day-to-day basis.
There's also the behavioral cost, I've noticed more and more people simply don't the code in code reviews anymore. Most feedback I get these days is stuff like "that's not supposed to be snake_case" or "a single space should be put between methods", and sometimes a glaring logic bug will crop up after 3 or 4 people who "approved" the review will gladly and openly admit _they_ _did_ _not_ _read_ _the_ _code_, and I think this is related to us overstressing the importance of all this tiny "form" misshaps and disregarding the "function" bits because it's harder to write a roadblock that checks for them.
I refuse to use Google products for critical infrastructure until they prove they won't kill the product as soon as they lose interest to chase the next shiny trinket or maybe build their 78th chat app
Exactly how is it legal to forego your right to a fair trial on an "agreement" between two parties who for any intents and purposes do not know each other?
You can think of it like this: There is an very large pool about 2/3 full of human crap, being filled by a number of spouts. Some of the spouts kinda stop ocasionally, but not for long.
There is a sinkhole, but it's not big enough, so it keeps filling.
When it fills up, you and everyone you love included, along with all of humanity, will have to drink from that pool forever as their sole form of sustenance, possibly dying of it. It's taking the plants and kelp with it, too, so eventually there will be nothing we can recognize as good.
The only way out is to make the sinkhole bigger or close every spout and try to make it _very_ clear what happened so future generations don't mess with it. Every other path leads to everyone and everything dying a horrible death.