Every time I checked it out over the years, it always seemed to have the massive kerning bugs. So I just bounced off. It's been several years since anyone mentioned it, though. The only reason I ever encounter it is due to the excellent kcachegrind.
Me as well. It's quite noticeable. One key distinction (also noted by others) is whether the context switch is externally imposed or internally generated. The latter are relatively painless, and probably actually productive as long as I'm not procrastinating excessively as a result.
The former are just unpleasant, usually. Sometimes, though, when being pulled off of some bullshit, make-work task, I actually rather enjoy it.
Am 51, and for the last decade I've experience some, yes. The most overt was for a Bay Area startup position that was going swimmingly until I did a Skype with the (much younger) DoE, and he saw I was "old". (Guess he couldn't read a resume.) But the more annoying ageism is a general assumption by some of the kids that if there is a difference of opinion on an engineering question, it's because the old guy is clinging to his anachronistic ways. Version control? Testing? Even a one-page design doc? Don't be such an old fuddy duddy!!:-)
It has its plusses, though. As an old guy, you realize that there's serious money to be made cleaning up after the kids. And experience can often tell you which projects are sure failures, which can save working on something hopeless for a year.
After all of these years, volume controls on phones still suck ass. The physical buttons are on the edge of the phone and you either butt-mute and butt-blare your phone all day long, or they're stupid hard to press and you can't tell without looking at the phone whether your change has even taken. On top of that, some apps "steal" the buttons, so you're never sure whether you're actually adjusting the volume or talking to the app.
On top of that, there are actually multiple settings, i.e., for ringer volume, media volume, etc. And some apps seem to have their own "private" volume setting that is only adjustable when the app is in the foreground. Or when the app _thinks_ it's in the foreground. Or when the OS has stopped lagging and gets around to thinking it's in the foreground.
And don't forget about headphones. Various things behave differently if headphones are plugged in. Some sounds go to the headphones and others continue to come out of the phone, for no obvious reason.
All of that assumes that you haven't tripped over the various OS bugs that make the volume unchangeable, etc.
So yeah, I still have a few hundred $$$ burning a hole in my pocket for any manufacturer that can solve this problem.
My God you're right! How could we have been so stupid! Clearly the reason 40,000 people are killed each year by cars is that they're all leaping in front of them! Kill the pedestrians! Kill! Kill!!!
Slashdot Mirror
Every time I checked it out over the years, it always seemed to have the massive kerning bugs. So I just bounced off. It's been several years since anyone mentioned it, though. The only reason I ever encounter it is due to the excellent kcachegrind.
That was kind of unexpected. Will they also be making America great again?
Me as well. It's quite noticeable. One key distinction (also noted by others) is whether the context switch is externally imposed or internally generated. The latter are relatively painless, and probably actually productive as long as I'm not procrastinating excessively as a result.
The former are just unpleasant, usually. Sometimes, though, when being pulled off of some bullshit, make-work task, I actually rather enjoy it.
Am 51, and for the last decade I've experience some, yes. The most overt was for a Bay Area startup position that was going swimmingly until I did a Skype with the (much younger) DoE, and he saw I was "old". (Guess he couldn't read a resume.) But the more annoying ageism is a general assumption by some of the kids that if there is a difference of opinion on an engineering question, it's because the old guy is clinging to his anachronistic ways. Version control? Testing? Even a one-page design doc? Don't be such an old fuddy duddy!! :-)
It has its plusses, though. As an old guy, you realize that there's serious money to be made cleaning up after the kids. And experience can often tell you which projects are sure failures, which can save working on something hopeless for a year.
After all of these years, volume controls on phones still suck ass. The physical buttons are on the edge of the phone and you either butt-mute and butt-blare your phone all day long, or they're stupid hard to press and you can't tell without looking at the phone whether your change has even taken. On top of that, some apps "steal" the buttons, so you're never sure whether you're actually adjusting the volume or talking to the app.
On top of that, there are actually multiple settings, i.e., for ringer volume, media volume, etc. And some apps seem to have their own "private" volume setting that is only adjustable when the app is in the foreground. Or when the app _thinks_ it's in the foreground. Or when the OS has stopped lagging and gets around to thinking it's in the foreground.
And don't forget about headphones. Various things behave differently if headphones are plugged in. Some sounds go to the headphones and others continue to come out of the phone, for no obvious reason.
All of that assumes that you haven't tripped over the various OS bugs that make the volume unchangeable, etc.
So yeah, I still have a few hundred $$$ burning a hole in my pocket for any manufacturer that can solve this problem.
My God you're right! How could we have been so stupid! Clearly the reason 40,000 people are killed each year by cars is that they're all leaping in front of them! Kill the pedestrians! Kill! Kill!!!
Works well. Available Everywhere.
If we use up all of our clay, we'll be in deep trouble.
Real science is cute, too.