110 karma · joined May 11, 2021
For future reference, you tap the green bar.
> approve it in some well hidden sub-section
I have a feeling this might be deliberate friction to make social engineering harder.
This is the flaw with the Apple back gesture, sadly, as although it's generally really easy to support this in native app — essentially it comes for free and you just don't break it — plenty of developers just don't care about invisible quality of life things.
The gesture is properly called 'Interactive Pop'.
I'll take a slightly slower phone (in reality not noticeable on most tasks) over unplanned restarts. My partner only just stopped using the iPhone 6 I bought in 2014, original battery all the way, and she had the throttling turned on for years without knowing or caring.
It's pretty crazy that people might be depending* on an Ultra model doing some extreme outdoors activity, and it turns itself into a little brick because it's tapping against something slightly conductive.
*—Don't do this with any tech.
This simply isn’t borne out by fact. The entire iPod, iPhone and iPad (non-Pro) range, going back over 20 years, have had exactly two connectors.
I bet there isn’t someone at Samsung or Motorola who can even tell you how many different connectors their products have used over that period of time, let alone what they were.
Xcode projects still keep files in the order you leave them in, unless you tell it to sort them. I'd guess 99% of people, like me, sort a group every time they add a file though.
Revealing a card PIN to anything other than ATM/POS hardware seems fundamentally wrong too.
It was always a struggle for JetBrains to keep up with Apple dropping new stuff with no notice though, and I can’t remember when I last tried AppCode
Authy get it, they prompt you to enter your backup password, just to check you know it, but you can skip so it doesn't get in your way when you're in a hurry.
I have one bank that never re-prompts for their passcode, and I've been locked out of the app since I got a new phone and put the wrong code in; because they name everything differently from all the other banks too. N.B. I can see the same accounts via my business login and phoning them is pain, so...
I think this is confusingly phrased and the replies relate to that confusion.
A free Apple developer account allows 'sideloading' for a limited time, currently a week IIRC, and a paid account extends this to a year, which is technically limited but probably not what most people would understand by the phrase.
I have a few, but sadly I don't have the space to keep a CRT monitor too.
The Lyons Electronic Office would beg to disagree. https://en.wikipedia.org/wiki/LEO_(computer)
The first business application to be run on LEO was Bakery Valuations, which computed the costs of ingredients used in bread and cakes [and] LEO took over Bakery Valuations calculations completely on 29–30 November 1951
I got 5.447 seconds on my first try in 55thegame.com
And I’m going to quit while I’m ahead!
Whilst I always used a full keyboard with a PC, for the reasons you give, the Mac has practically all of those things mapped to cursors + meta keys so your hands don't need to move from the normal typing position. I now see the extended bit of the full keyboard as dead space that makes me reach further to get to mouse/trackpad. But as you say, everyone is different.
I have found NSDate/NSCalendar to be the best designed API for date and time calculations, and I never knew it was built on top of ICU. It discourages bad assumptions while many others try to make a more 'fluent' interface that encourages them.
When I first tried Joda in Java it had a builder interface that stank, I was able to easily write tests that produced the wrong date or threw an exception simply by changing the order of construction. But I think that's long gone.