Slashdot Mirror
Ask Slashdot: How Often Do You Update Your OS?
An anonymous reader writes: A couple friends of mine have been having a debate recently. One is constantly updating all of his operating systems (desktop, phone, and otherwise), often as soon as a new patch is available. He tries betas and nightlies. He has a different ROM on his phone every other week. The other friend is much more conservative with his updates. Once his systems are running smoothly, he wants to leave them alone for as long as possible. He'll do some serious security updates, but he's extremely wary of anything involving major UI changes or functionality differences. What's your preference? Are you constantly tweaking? Waiting for the early adopters to work out the kinks? How does your preference change between work machines and personal machines?
the Emacs vs VI war is over (Emacs won) ...
Yeah I'm thinking not. I've been a Unix sysadmin for over 15 years and I've never worked with a single person who uses Emacs.
Nothing to see here
Automotive control interfaces change all of the time.
Into about 1980 all American cars and trucks had, for many years, placed the headlights control on the dash at the left. Wiper blade control was usually on the lower left side of the dash near the knee bolster. They placed the turn signal on the left side of the column, placed the gearshift on the right side of the column, and placed the brights control on the floor, operated by the left foot. The radio was generally low on the right side. If a fancy car had an interior dome light with dimming capability it was usually placed on the left with the headlight control, and if there was cruise control, the function was integrated with the turn signal indicator stalk, with a slider on the side for set/coast and a button on the tip for on/off.
In the late seventies and eighties they started playing with multifunction stalks and all bets were off. Some cars integrated nearly every function into the stalk, and if the car had a floor shifter instead of a column shifter sometimes a second multifunction stalk was added to the right side. Floor controls were mostly eliminated and most low, hard to reach controls were relocated to stalks. Tilting telescoping steering columns added a third stalk on the lower-left of the column. When Mercedes Benz took over Chrysler they attempted to add a fourth stalk to the column, low on the right, for the cruise control. Steering wheels got controls on the front, then on the back. At one point early on there was a "rim blow" steering wheel where squeezing the wheel would activate the horn.
My point is that automotive controls are very much NOT standard. Even basic functions like gear selection could be pushbutton, could be a column stalk, could be a dash stalk, could be a floor stick, could be a dash-mounted knob, could be a center-console knob, and there are probably more variations yet. Drivers have to get used to each and every configuration.
Do not look into laser with remaining eye.
What is the entire lab doing planning to run Win 10 Home? That's the only edition that forces mandatory updates. Pro lets you defer them; Enterprise lets you completely control the process
"Blinkers" are both turn signal and hazard indicators. Cars I have owned manufactured in the past 20 years have had at least three distinct control methods to turn on and off the hazard indicators. So no, "blinkers" haven't been standard for 35 years.
It doesn't hurt to be nice.
This is aggressively missing the point. The original poster was discussing the fact that you can hop in any modern car and know with certainty how to actuate the left or right hand turn indicators. His/her point is valid and true, but instead of addressing it you are now on about hazard lights.
Yeah... no. They broke cron, they inflicted that insane "app nap" nonsense on us (broke damned near every real-time application out there... I spend a *lot* of time explaining to OS X users that it needs to be turned off or OS X will summarily stop giving the required amount of CPU time to the app) there's sand-boxing, the changes in spaces functionality, they utterly broke UTF-8 console printing (and didn't fix it... just left it broken unless you upgraded -- and yes, they knew about it in time, I talked to "Mr. CUPS himself about it), dropped PPC emulation, moved image support from apps to OS (which broke the dickens out of Aperture upgrades, among other things), they broke getting to local websites on your LAN, and they quit giving us actual media, which I simply find annoying and short-sighted. And they still haven't fixed many of the OS bugs, for instance, you still can't have more than one app listening to a UDP broadcast reception port as far as I know. I don't have any idea whose brilliant think it was to decide that "broadcast" meant only one app can listen, but there you go.
Definitely quite a few reasons to be reticent about moving to a new version of OSX. These things matter.
Sure -- if you don't mind a good deal of your stuff breaking. Inconveniently enough, I do mind. Hence, 10.6.8, and staying there as long as possible, too.
I've fallen off your lawn, and I can't get up.