Yes, I can come up with a thousand free market answers. And yes, that pretty much answers your question.
Would you buy a vehicle from any company whatsoever if you knew that parts were difficult to acquire? A manufacturer can play a game with parts availability only if they don't plan to stay in business.
Maybe we should go back to renting our phones from ATT as well.
What about the setting "Let me choose one scaling level for all my displays"
Was waiting for someone to mention that. It doesn't work. I have noticed no appreciable effect. And to clarify, by "re-size" in my above post, i mean that it does a really shitty job of scaling things to what seems like non-native monitor resolution - exactly like if you were to say, run you 1920x1080 monitor in 1680x1050 resolution. Blurred fonts, head-ache inducing and difficult to read. My laptops internal screen is 1920x1080. My 23" monitor is 1920x1080. In 6 months I was unable to get this behavior to stop. Yes, i understand what Windows 8.1 is TRYING to do - make my windows the same physical size on both screens, but it doesn't work and makes things nasty to use - and can't be disabled, it would appear. Whether that is due to a driver issue or what i have no idea. But its a deal breaker for multi-monitor support for me at the moment.
What are your thoughts on code signing, and do how do you see the development of such proceeding in the free unix world. In Powershell for example, i can set a system-wide policy to only run scripts if they are signed with a trusted certificate.
This means I can, for example, delegate script development to an underling, review the script and then sign and push into production, knowing that the script will not run if it has been modified in the field without authorization - enabling proper change management process to be enforced.
Other platforms require all code to be signed before it will run.
Do you foresee anything like this (obviously with the master signing authority being the local site admin) for OpenBSD?