3 ms·

To your point about using Linux, unfortunately working with specific tools that only run on Windows, I don't have that option. Windows is forced on me and I don

To your point about using Linux, unfortunately working with specific tools that only run on Windows, I don't have that option. Windows is forced on me and I don't think that is by accident. Again this leads me to seriously question that they indeed could have turned "good" as the parent comment asks.

KGIII 9y ago
Yeah, that was why I mentioned that it may not be a viable option for them. I'm not sure the answer is in one license over another, nor in one OS over another. I'm not sure it is, realistically, solved by any one company being 'good' or 'evil.' I think the most realistic hope for the future is open standards being used and people opting to support them. If we get rid of proprietary standards, we can more easily have alternative software to do the same work. As far as Microsoft goes, I do not really expect them to be good or evil. I expect them to do things that increase their profitability. I recognize that their goals don't always align with my best interests, so I generally avoid them. At the same time, I'm grateful that they exist as an option. I do use a Windows phone, but that's because it suits my needs better than the alternatives. So, I don't dislike Microsoft, I just avoid them most of the time. I don't think they are as bad as they used to be. They seem to have come to grips with open source and have made some steps in the right direction. VSCode is pretty nice to work with and they have a Shared Source Initiative program that many don't know about, which is another example. Anyhow, I think using open standards and enforcing it by demanding support in the products we buy is probably our best chance at changing the industry. Our applications output something. There's no realistic reason, that I can think of, for that something to not conform to open standards. Then, we can select vendors of our choice, licenses of our choice, or create our own, by ourselves or through paying someone. I will note that it is understandable but sad that more companies aren't willing to write their own software. I see that as related to the problem. They'd prefer to use COTS software. Yeah, it's less expensive and does sometimes make sense, but if they wrote it themselves they could more easily port it to various operating systems and architecture. Ideally, those OSes and architecture would conform to open standards and make it even easier as time progresses. I'm not sure if we will reach that point, but it'd be nicer - I think.

KGIII 9y ago

Yeah, that was why I mentioned that it may not be a viable option for them. I'm not sure the answer is in one license over another, nor in one OS over another. I'm not sure it is, realistically, solved by any one company being 'good' or 'evil.' I think the most realistic hope for the future is open standards being used and people opting to support them. If we get rid of proprietary standards, we can more easily have alternative software to do the same work. As far as Microsoft goes, I do not really expect them to be good or evil. I expect them to do things that increase their profitability. I recognize that their goals don't always align with my best interests, so I generally avoid them. At the same time, I'm grateful that they exist as an option. I do use a Windows phone, but that's because it suits my needs better than the alternatives. So, I don't dislike Microsoft, I just avoid them most of the time. I don't think they are as bad as they used to be. They seem to have come to grips with open source and have made some steps in the right direction. VSCode is pretty nice to work with and they have a Shared Source Initiative program that many don't know about, which is another example. Anyhow, I think using open standards and enforcing it by demanding support in the products we buy is probably our best chance at changing the industry. Our applications output something. There's no realistic reason, that I can think of, for that something to not conform to open standards. Then, we can select vendors of our choice, licenses of our choice, or create our own, by ourselves or through paying someone. I will note that it is understandable but sad that more companies aren't willing to write their own software. I see that as related to the problem. They'd prefer to use COTS software. Yeah, it's less expensive and does sometimes make sense, but if they wrote it themselves they could more easily port it to various operating systems and architecture. Ideally, those OSes and architecture would conform to open standards and make it even easier as time progresses. I'm not sure if we will reach that point, but it'd be nicer - I think.