Actually, this person is somewhat involved with the Open Source Energy Network. It's open source, even if it isn't software, so it's on-topic here at Slashdot.
While his analysis might be incorrect, how do you know that his back is not affected by weather changes? Indeed, that is often something that is reported by people who sustain injuries.
When I was young, there was a farmer down the road who took shrapel in his knee in WWI. Just before a storm came his knee would swell up, and right after the storm was gone it'd stop. You could sit there watching it happen. Now, I'm not sure why it happened. But it did happen, and it happened frequently.
It's possible that somebody like hkmwbz, who I have proven wrong numerous times, was responsible. He often considers the moderation system as something that should be used as a weapon.
Much of the Linux documentation applies just as well to the BSDs.
But don't forget that the users in this case are IT professionals. They should know UNIX, and they should know Linux. If they don't, then they shouldn't be in the IT business. So for such people, adapting to OpenBSD shouldn't be a problem at all.
Theo is often portrayed as some awful person, but that is not the case. He is a fantastic coder, one of the supreme software engineers alive today, and by far a very helpful fellow when you don't waste his time. Yes, he's blunt, but that's because he's far too busy of a man to waste his time with extreme diplomacy.
Frankly, I'd rather him give a short, blunt answer to a question and then spend the rest of his time developing OpenBSD, instead of wasting a lot of time writing an answer that makes everyone feel all warm inside.
Have you ever actually used OpenBSD? If you have, then you would know that it's a massive time and money saver. Why is that? Because it just works. It's a well-engineered product. Your risk of security issues is virtually nil, and the support from the mailing lists often rivals that of anything from Microsoft or Red Hat.
Perhaps you could if you took a more professional approach. Have you performed any serious analysis regarding such a transition? Can you show that there would be definite savings? Don't forget to cover non-technical issues, such as how long it will take for users to adjust, and how easy the adjustment period will be.
Often times managers are more than willing to consider improvements, just as long as you're providing solid, reputable evidence to back up your claims. Don't waste their time by saying "Omg Linux oR 0p3nbSD is SOOOO rOx beKuz sUm/. gUy said it K00! leTz switcH 2day!1!@!!" Instead, provide them with an analysis that focuses on how the transition will benefit them directly, be it in increased productivity or decreased expenses.
And if they can't train themselves, then get rid of their sorry asses. Let's be honest, with the wealth of easily accessible documentation out there, there's no excuse for any somewhat competent IT person to not be able to pick up OpenBSD. Since any decent person in the field would also have ample amounts of UNIX and Linux background, OpenBSD should be a relatively minor change for them. If they still can't pick it up, then they just shouldn't be in the IT field.
Perhaps he was misquoted? Indeed, any decent IT manager would understand that it is necessary to plan ahead. Coming up with proposals, performing various cost/benefit analyses, and discussing with other IT people will often lead to many potential problems being dealt with early.
What has been the quality of their previous ports of games to Mac OS X? Indeed, when Loki was porting games to Linux the quality was always top-notch. Often the games would perform far better under Linux than under Windows, on exactly the same hardware.
Can you tell us more about the systems you ran into problems with? Were they all running a common version of Windows, for example? I cannot say that I have ever run into such problems while playing that particular game. It has always been rock-solid, unlike most EA games, for instance.
I just want to thank Peter Molyneux for all the work he's done on these games. Black and White was truly a fantastic game, but more importantly it was innovative, perhaps to the point of being revolutionary. The gaming industry needs more geniuses like him.
Would you support a publication that repeatedly pointed out you myriad of flaws, poor reasoning and simple idiocy?
If I were the president of the United States, then yes. After all, any true American knows that the press should be there to do exactly that. Of course, it doesn't actually work that way in America these days, because of the corporate ties that the mass news media has. Perhaps that's why so many government mistakes, intentional or not, are allowed to pass over there.
Games like Half-Life 2 are hardly innovative. Yeah, the graphics are a bit spiffier, but they're still basically the same as they were over a decade ago.
If you want to talk about real innovation, you have to look towards the fields of medical visualization. Even some of the geophysical visualization technology is far more advanced and innovative than some PC game. The physics simulations are far superior, and the graphics themselves are beginning to hit a whole new level. This is software that is performing algorithms so complex, and pushing so much data, that they need to use the best possible hardware from SGI.
Sure it's a clone. That's what a non-innovative reimplementation is. Yeah, the Mono people have thrown together Gtk#, for instance, but it'll most likely remain a "proprietary" Mono class library. So it's innovation, but not within the context of.NET as a whole. Thus Mono, and Portable.net, are nothing more than clones.
Slashdot Mirror
Actually, this person is somewhat involved with the Open Source Energy Network. It's open source, even if it isn't software, so it's on-topic here at Slashdot.
While his analysis might be incorrect, how do you know that his back is not affected by weather changes? Indeed, that is often something that is reported by people who sustain injuries.
When I was young, there was a farmer down the road who took shrapel in his knee in WWI. Just before a storm came his knee would swell up, and right after the storm was gone it'd stop. You could sit there watching it happen. Now, I'm not sure why it happened. But it did happen, and it happened frequently.
It's possible that somebody like hkmwbz, who I have proven wrong numerous times, was responsible. He often considers the moderation system as something that should be used as a weapon.
You should realize that Barry Norton is an expert on these matters. He's the Real Deal.
Much of the Linux documentation applies just as well to the BSDs.
But don't forget that the users in this case are IT professionals. They should know UNIX, and they should know Linux. If they don't, then they shouldn't be in the IT business. So for such people, adapting to OpenBSD shouldn't be a problem at all.
Theo is often portrayed as some awful person, but that is not the case. He is a fantastic coder, one of the supreme software engineers alive today, and by far a very helpful fellow when you don't waste his time. Yes, he's blunt, but that's because he's far too busy of a man to waste his time with extreme diplomacy.
Frankly, I'd rather him give a short, blunt answer to a question and then spend the rest of his time developing OpenBSD, instead of wasting a lot of time writing an answer that makes everyone feel all warm inside.
Have you ever actually used OpenBSD? If you have, then you would know that it's a massive time and money saver. Why is that? Because it just works. It's a well-engineered product. Your risk of security issues is virtually nil, and the support from the mailing lists often rivals that of anything from Microsoft or Red Hat.
.
Perhaps you could if you took a more professional approach. Have you performed any serious analysis regarding such a transition? Can you show that there would be definite savings? Don't forget to cover non-technical issues, such as how long it will take for users to adjust, and how easy the adjustment period will be.
/. gUy said it K00! leTz switcH 2day!1!@!!" Instead, provide them with an analysis that focuses on how the transition will benefit them directly, be it in increased productivity or decreased expenses.
Often times managers are more than willing to consider improvements, just as long as you're providing solid, reputable evidence to back up your claims. Don't waste their time by saying "Omg Linux oR 0p3nbSD is SOOOO rOx beKuz sUm
But you're grub! You can do magical things like that.
And if they can't train themselves, then get rid of their sorry asses. Let's be honest, with the wealth of easily accessible documentation out there, there's no excuse for any somewhat competent IT person to not be able to pick up OpenBSD. Since any decent person in the field would also have ample amounts of UNIX and Linux background, OpenBSD should be a relatively minor change for them. If they still can't pick it up, then they just shouldn't be in the IT field.
Perhaps he was misquoted? Indeed, any decent IT manager would understand that it is necessary to plan ahead. Coming up with proposals, performing various cost/benefit analyses, and discussing with other IT people will often lead to many potential problems being dealt with early.
What has been the quality of their previous ports of games to Mac OS X? Indeed, when Loki was porting games to Linux the quality was always top-notch. Often the games would perform far better under Linux than under Windows, on exactly the same hardware.
Can you tell us more about the systems you ran into problems with? Were they all running a common version of Windows, for example? I cannot say that I have ever run into such problems while playing that particular game. It has always been rock-solid, unlike most EA games, for instance.
Does this game play well with Wine, or any of the Wine derivatives, on a fairly modern Linux system?
I just want to thank Peter Molyneux for all the work he's done on these games. Black and White was truly a fantastic game, but more importantly it was innovative, perhaps to the point of being revolutionary. The gaming industry needs more geniuses like him.
Would you support a publication that repeatedly pointed out you myriad of flaws, poor reasoning and simple idiocy?
If I were the president of the United States, then yes. After all, any true American knows that the press should be there to do exactly that. Of course, it doesn't actually work that way in America these days, because of the corporate ties that the mass news media has. Perhaps that's why so many government mistakes, intentional or not, are allowed to pass over there.
Do you have an equally large penis to grasp those hands around?
It's a joke, kid. Lighten up a little bit.
Yes, if you read his post it does appear as though he was saying just that!
As I said, you have resorted to ad hominem attacks, and thus have lost the debate.
That's deals with the Semantic Web model. If you didn't know, Barry Norton is a leading expert in that field.
Sadly, it's difficult to tell these days which people who talk like that are serious, and which are joking.
Then you have to slap your cock down on it instead, and it'll read your big purple penis vein.
Games like Half-Life 2 are hardly innovative. Yeah, the graphics are a bit spiffier, but they're still basically the same as they were over a decade ago.
If you want to talk about real innovation, you have to look towards the fields of medical visualization. Even some of the geophysical visualization technology is far more advanced and innovative than some PC game. The physics simulations are far superior, and the graphics themselves are beginning to hit a whole new level. This is software that is performing algorithms so complex, and pushing so much data, that they need to use the best possible hardware from SGI.
Sure it's a clone. That's what a non-innovative reimplementation is. Yeah, the Mono people have thrown together Gtk#, for instance, but it'll most likely remain a "proprietary" Mono class library. So it's innovation, but not within the context of .NET as a whole. Thus Mono, and Portable.net, are nothing more than clones.