If Apple didn't want to avoid the bad PR, they could just terminate their business relationship permanently, and they'd be in the right, even morally, since it was Kapeli who violated the trust.
229 karma · joined August 1, 2016
If Apple didn't want to avoid the bad PR, they could just terminate their business relationship permanently, and they'd be in the right, even morally, since it was Kapeli who violated the trust.
He has registered an account using his credentials, the account was involved in fraudulent activity, that makes him responsible, as an individual. Why is Apple supposed to even care that he doesn't control the other account anymore? He's supposed to control the account, according to the terms of service he agreed to. If he doesn't control it and he doesn't want to be responsible, he has to close it.
Apple is giving him the opportunity to get back to having a business relationship, but he doesn't understand the problem. Apparently, neither do many of the other users on here. Apple has every right to terminate their business relationship,so how is it blackmail? It's more like a plea bargain...
There's no notion of "unsaved" changes. There's the notion of form data that hasn't been submitted, which is entirely different. Many web apps don't use "submit" at all, ever.
So what? There's a lot of people who actually lose data due to this "feature". Even if there was more of "your kind" (which I doubt), preventing data loss is more important than slight convenience. You can easily change a setting or a commandline option or install an extension. A lot of other people would need to call tech support for that, because they're afraid they'll break their computer...
"Read carefully, slow down, and pay attention to what you're doing."
For someone beyond their twenties, you're certainly a wise-ass, I have to say.
"That goes back to my original suggestion of having a prompt dialog, and making it configurable for those who don't want the "permanent training wheels"
Your suggestion doesn't work. It would literally break some applications and make others so annoying to use that the prompt would be the first thing users disable, bringing us back to square one.
The underlying problem is unsolvable for a browser vendor. All that can be done is to mitigate it by reducing accidental back-navigation. If that means people like you are inconvenienced, so be it.
I'm sorry, but maintaining your little piece of convenience isn't worth denying other users a more forgiving user experience.
You're probably a twenty-something with sharp reflexes. What's "not that hard" to you on whatever websites you happen to use may be a significant challenge for older people who are forced to use terribly designed websites/webapps for work or other services.
You'd think they do, but they don't, at least not all of them. The problem isn't the properly designed webapps, it's the improperly designed ones. That's what you somehow don't understand/recognize.
Also, the problem with the redirect happens on a certain popular bulletin board software that works without Javascript (and therefore doesn't provide such a prompt in the first place).
There's numerous things that can go wrong, here's two common ones:
1) The page you are going back to is a login prompt, which immediately redirects you, overwriting your "forward" state.
2) Javascript. Everything can happen. Everything will happen. Your worst nightmares will come true.
It is not overloaded. It doesn't start deleting characters depending on where your last tap may have (accidentally) been. Well, maybe some app does that, but I hope you get my point.
Oh wait, that's not funny. That's sad.
If this never happened to you, good for you, you lucky bastard. Now get out of the way, this is a quality of life improvement for millions of real people out there. Hard working people. Mothers and Grandmothers. Think of them while you are bothered to work around this slight inconvenience of yours.
"Android has back key and home key that users hit accidentally all the times."
The back and home buttons are not overloaded with other meaning based on context. Android applications tend to handle accidental "back" presses gracefully. Accidental "home" presses are usually of no consequence whatsoever.
"Why can't the Web apps save their state to better handle the accidental exit of the app?"
Who cares? They don't and they won't.
"It's not just the backspace, Ctrl-R and Ctrl-W all exit the app."
It's way less likely to accidentally hit those combinations. For backspace, it happens all the time.
"Don't break existing functionality!!"
The functionality isn't broken, it's just that the few people who actually use this shortcut will have to use another shortcut now. Big Deal.
IRs, ASTs and bytecodes are not programming languages. If you insist otherwise because "some might consider it that way", you have no business criticizing the use of words, to be honest.
There are textual representations for these things, but even then people rarely program in those (LISP being an exception). Assembly language is a textual representation for humans to read and sometimes program in. If you have some program that actually translates to assembly language as a target, by all means, call it a transpiler if you want.
If you're not prepared for that situation at all times, you are using computers wrong.
Everything else is pretty much obsolete.
The problem is in how it doesn't really work reliably, especially with C extensions, which are much more common in Python-Land than with anything Javascript/NodeJS-related. You're also comparing with something that, by virtue of its age, has far less technical debt. Also, NPM is a "commercial product", PyPI is a community effort. Maybe the comparison to something like Anaconda would be more apt.
The author acknowledges most problems anyway, he just comes to the wrong conclusion: It's not "good" now, it's still terrible, but everything else is more-or-less as bad or worse.
I'm surprised that in the land of (apparently ) limitless legal liabilities, so many people are bullish on self-driving cars, let alone self-driving trucks.
You should be highly concerned that the push towards this by big players is going to lead to laws where ultimately nobody will have to take up personal responsibility for accidents anymore.
"True" readability is achieved through a consistent structuring of your program, which has to conform to the expectations of the reader.
Programmers must first build this expectation from picking up patterns in the code, which emerge no matter if you use pattern matching or an equivalent structure using the available language constructs.
Untold amounts of energy (and dollars) must have been wasted on the "convenience" of writing some program in Python that scales over cluster of MapReduce nodes, without investigating how an in-core solution in a straightforward native implementation would have performed.
I don't think there is a solution for the small-time criminals having access to guns, all you can do at this point is try and drive the black market price up, by making it tougher to get new guns.
Either problems require new legislation, which the gun lobby is blocking at every step of the way.
You cannot stop cartels from dealing drugs, despite massive efforts, what could you do to prevent them from dealing weapons?
Furthemore, while cartels are certainly important, the majority of gun-related homicides within the US are caused by small-time criminals, within a social fabric that facilites small-time illegal gun sales.
You basically want to increase legal liabilities (which already exist) to an extreme, but you will then have trouble finding any insurance company that is willing to cover the kinds of damages that can be caused by guns at a rate affordable to an individual.
Either of these things will require legislation that will receive massive pushback from the gun lobby. In a country where even basic background checks or limiting of certain weapon types hasn't been realized, your ideas seem almost utopian.
Having said that, I don't disagree in principle.
The same statistic probably applies to countries with stricter gun laws, it's the sheer amount of weapons available that make the difference. The US gun laws have created a flood of weapons into black markets, especially in South America, where the Mafia is often armed better than the police.
It's safe to say that this development cannot be reversed at this point, but it can still be curbed.