481–490 of 501 posts
Earlier quoted context omitted.
Its a miss on qa end. so if the qa in my company is good they are assholes ?
QA found it. Management decided not to fix it and ship. Who's the asshole?
Earlier quoted context omitted.
I am a programmer. And if I shipped a crap like this, I would agree that I deserve to be yelled at. But the problem is probably not at developer level, it's higher ups who don't care about quality control, which permeate downwards.
You didn’t answer the question, but I’ll go ahead and suggest that you are motivated to create good software, not by a fear of being yelled at, but rather something else. Maybe you think the product you are making is of actual value, and are proud of it. Maybe you want to impress your boss with the quality so you can get a raise. Maybe you don’t want to be fired. In any case, I would be shocked if there was anyone, a…
Do you seriously think anyone would answer "yes i love getting yelled at"? If yes, then I'm done here. If no, then ask yourself why you asked that question. it's a rhetorical question to control your narrative, which has nothing to do with what GP said. GP never said it's a good thing to yell at others, and neither did I. You're the one who turned it into this narrative for the sake of your argument.
Earlier quoted context omitted.
> What is debunked? I'll help you a bit. > > [...] Apple had liberally sprinkled wait() into the iOS 11 code base so that I'd feel like my ole A9 CPU just wasn't cutting it any more From the article > Are older iPhones being deliberately slowed? [...] maintain a consistent level of performance across iOS versions Sure, as you snarkily remark, your CPU/GPU hasn't changed, but neither has the iOS version inherently mad…
Tired of people bringing up that "article" and the sensationalist media headlines. All that articles shows is that the CPU, given 100% utilization, does the same result as it did on iOS 10. Really surprising for sure. So what was the point of you posting that article? People saying "Apple is slowing my device" don't actually mean "the CPU has become slower". There goes the entire premise that benchmark. The CPU is th…
But that is LITERALLY what people were accusing Apple of doing, actually slowing their devices to make them buy newer models. There might have been less conspiracy-esque claims, but jesting they were "sprinkling wait() calls in the code to make me upgrade" is not in that category - so I disagree with your claim that people weren't meaning that.
Anyways, this discussion has derailed, so I'm just gonna leave it at that.
Earlier quoted context omitted.
Not the best example. Lots of bugs and issues happened under Jobs, but this was the usual press BS. The iPhone 4 went on to sell 50 millions of devices or so with that antenna and nobody in the real world had much of an issue with it.
Seems you are cutting and pasting, but Apple gave away free bumpers with the 4, so yes, it was an issue.
You wanted a totally original rephrase for a response to the exact same topic on a different subthread?
>Apple gave away free bumpers with the 4, so yes, it was an issue
Which few really used in the wild, so no, it wasn't.
Earlier quoted context omitted.
You mean the iPhone 4 antenna non-issue? Lots of bugs and issues happened under Jobs, but this was the usual press BS. The iPhone 4 went on to sell 50 millions of devices or so with that antenna and nobody in the real world had much of an issue with it.
A relative's phone calls got disconnected very regularly until she covered the antenna with tape. If nobody in the real world had any issues with it nobody would have discovered it in the first place.
If only media worked that way and never discovered problems where they don't exist or are totally marginal...
By the same logic, if nobody listened any difference with $1000 "hi-fi cables" they wouldn't be buying them...
Earlier quoted context omitted.
Maybe we should start worrying about "animation creep" as much as we do feature creep or other kinds of unnecessary complexity.
One of the main reasons I don't use iOS or macOS anymore is because of the animations. Even very, very short animations make the whole experience excruciating for me. It feels slow and unresponsive.
One reason I moved from Windows phone was the massive delay in switching apps.
Now on iPhone the animations are annoying, yes, but they are at least consistent in length, meaning I expect them and know how long to take a (tiny) pause. I know some work is happening that’s being disguised and that’s why they can’t (all) be turned off.
Earlier quoted context omitted.
The worst thing for me is the Camera. If I want to take a photo of something that's just happening I don't even bother anymore since I can expect it to take 10 seconds to wake the phone, get into the camera, and have the shutter button respond and have it actually take a photo (sometimes it looks like it took a photo but it actually didn't save!).
Yes! Especially if what I'm wanting to do is take a video of my kid. By the time I get the photo app to respond well enough to swipe over to video and let it readjust itself, I have missed the moment by seconds.
Back in the 90s I decided we needed a real-time UX - hard real-time guarantees. I had no idea how to even start with this, especially as the only OSes I knew well were UNIX-like, none of which did real-time. There was QNX(?) but I didn’t have access to play with it.
So do we need an effort to make a new real-time phone OS? Kinda like the Firefox phone OS project but built on an OS that allows guarantees?
Earlier quoted context omitted.
I remember people doing that on an AS/400 ramming keystrokes for 5 seconds and then waiting 15 seconds for the system to arrive in the right screen, sometimes even already filling the fields from muscle memory. The first five lines of address data were already entered before the screen loaded.
When I was in high school I had a job after school where they still had a PDP/11 w/real DEC VT-100 terminals. The kid next to me used to do data entry and would get far ahead of the input screen. Except when he made a mistake, and he often did, it would beep. But because he was so far ahead when he made a mistake it would beep for 2 minutes straight. Every time. Max-volume. Soo.. When he left his desk, I went in and…
Earlier quoted context omitted.
Keyboard buffers are decidedly not on the physical keyboard. The keyboard might have a very small one, but the IRQ is triggered on every input. The buffer in question is, for a tty, a driver-level buffer that holds on to the data until something reads it. If a command doesn't read it (which things like apt-get update don't) then it'll get read as the next command. Of course, most terminals these days are ptys accesse…
ah, the more you know :) I would have been shocked if i remembered all that correctly