by mk » Jun 30th, '12, 16:29
I guess this topic will remain hot for a bit longer than C# and Mono. :)
Ok, my 1 cent.
Yes, every x86 base machine will be able to disable SB, no problem. Complaints about having to go to EFIed 'BIOS' to disable it are rather funny if we talk about Linux users though.
On one side, Linux users want complete control over their systems, I got that, I like it too. Why else I would use just openbox with gmrun for all my needs then.
But on the other, they complain about such a trivial thing, sorry, I'm missing some pieces here.
In general, the whole SB issue is just a waste of people's time, much more than Linux trademark was. Like it or not, we live in a world driven by money. MS has money and a BIG desktop market share, thus huge influence over OEMs selling desktop machines.
This whole thing is only about OEMs, not MS at all. MS as a company has no rights to tell users what to do if they buy an retail MB from somewhere. And here is the catch. Actually, it's good OEMs who want to have the W8 logo must provide the off switch, because no doubt, majority of them will want to have it. In case they would be free to do whatever they want (OEMs not caring about W8 logo can of course), we may likely end up with much more mobos that will not allow to disable SB. In this case, MS actually helps.
But sure, it's not because MS being *nix friendly, no no. Simple reason for x86 being able to get rid of SB is, yeah, you guessed it - older MS op. systems. 7,Vista and XP (support of which ends in 2014) know nothing about SB and people having those OSes would be angry on MS. No other reason behind it. MS can't afford cornering some *nix users and loosing much more of it's own customers by doing so. Again, money driven decision, but in *nix favor this time. Hmm, thinking about it, when such an MS' decision happened last time? :)
RH/Fedora selling out to MS, aaaahh.
OK, it may seem rather obscure to have MS key on your system, but really, after getting rid of the religious view, there is nothing wrong about it. If for nothing else, than just because MS has the resources to prevent the key from being exposed, hard to say if any *nix based company has the same kind of resources, but I would say not. Well, the way I see it is, money is the loyalty factor here. Verisign needs to live somehow, MS is well, MS, so it's not a good idea to even allow some small chance of the key being exposed. Also, those 99$ are going to Verisign, not MS.
Reading Garret's blog, I found the reasoning behind RH's decision perfectly logical. I admit there can be some part of RedHat influence in regards to it's profit, but again, we live in such world and without RH, no Fedora. I would love to see decisions being made without money concerns, but that is unfortunately impossible. But again, I'm talking about in-between-lines possibility, I'm not implying anything.
It's like the mentioned C# issue. RH declared that they will never support it. I guess it has something to do with those known license concerns (namely WinForms related), because in case they get real, RH could be in trouble, but Fedora can't, it's not a commercial entity, so they provide Mono without problem, although it's not installed by default.
It's rather sad, C# is great stuff to work with, namely in terms of cross-platform development, especially if you graphical app uses GTK#, simply installing Mono with GTK# on Windows machine is usually enough to directly run it there, if you chose GTK# as the toolkit of choice.
Comparison between porting C/C++ and C# code is out of question here. Than there are reasons not to use it like the fact it's managed code, sigh. Java,Python, PHP, Ruby - the same, yet no problem. Religion is always a problem.
But I got where I didn't intend to, sorry. :)