On 10/27/14 3:16 AM, Peter Astrand wrote: > I totally agree with you on this one. I guess people thinks it's more fun > to work with new projects and new code, than to maintain old stuff. But > this idea of "new" = "always better" is present in the entire industry; > not just in the open source community.
Indeed it is, and although I still prefer Mac to Windows, Apple is actually one of the worst culprits here lately in terms of shoving new stuff down the user's throat instead of fixing long-standing bugs. They force you to upgrade your O/S in order to run the latest versions of their applications (and often the latest versions of 3rd party applications as well, because each new version of Xcode drops support for all but the latest O/S.) But they are lax about fixing driver bugs with older hardware in their new O/S's, thus forcing you to upgrade your hardware as well. A literally 2-year-old driver bug in Mavericks that Apple, in their typical fashion, won't own up to has prevented me from upgrading (the bug basically prevents firewire drives from going to sleep.) I read an article a while ago -- probably written in response to some epic software-related failure in a NASA space probe or something like that -- that discussed why software should, from the point of view of testing, be treated like a physical machine. We would never accept "bugs" in physical engines, yet we consider buggy software to be an inevitable fact of life. It doesn't have to be, though. I go one step further and consider not only the stability of the "engine" but also its performance. If your car can only go 30 miles per hour, then it doesn't matter how bug-free the engine is. The fact that its performance is severely limited is, from the end user's point of view, a bug as well. ------------------------------------------------------------------------------ _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
