Ok, at the risk of opening myself to flames, I would say that the tests (for once) look valid. Doesn't look good for Linux, and we all know Microsoft is gonna have a blast in the PR dept.
I think it is important to note though that in MS you have NT 4 to pay for, then IIS, and all the rest. So Linux certainly is cheaper, and it's uptime is better. And Linux has better SMP support. Also add in tech support (assuming you outsource for both NT and Linux) and Linux still kinda-sorta comes out on top.
IMHO (strapping on the asbestos) they both have their uses. Like it or not, there are some things that NT is simply better for. And ditto for Linux too. I personally believe Linux is a better server platform despite the Mindcraft tests because of uptime and efficiency.
Makes sense - personally all my friends Palms (I don't own one right now) I can't stand the input, although I'm told it's fast enough once you get to it. But, honestly, I'd rather have to learn a new input method than use a tiny tiny keyboard. And what about that researcher that found that Grafitti can cause physical problems in the hands similar to CTS or worse?
Also thought I'd make a mention - a lot of people here are talking about NDAs. Granted, an NDA gives you some legal protection. But honestly, folks. How many news sites out there have violated NDAs (this is especially bad in the consumer 3D graphics accelerator and gaming industries) to bring the scoop? Or, if it's an idea, short of notarizing what's to keep them from making a similar-but-unrelated-enough-to-pass-muster patented thingy? An NDA relies on trusting the other party, and as much as I hate our friends at the U.S. Patent Office for their shoddy checking, I likely would attempt to raise the money for getting a patent if possible before going the NDA route.
Basically it all boils down to whom you decide to go to. There are venture capitalists who have reputations for being very ethical about this sort of thing, and others who have become known for dumping inventors and redoing it themselves, then patenting it.
My immediate thought would be to grab copies of the schematics, code if needed, etc. and have those babies notarized. Backup tapes rule. Get some solid proof that you had it first. Then see who you can talk to.
Hell, who needs venture capitalists - if it's cool and it runs Linux, you'd probably take in just as much money by putting on banner ads and posting the site here as a news item;-)
Sega does have to make a choice between cable and DSL, though.. I don't have cable, so I'm not sure how many cable modems out there have Ethernet hookups. Also worrying are those people who are now buying DSL modems on a card instead of an external modem with Ethernet jack.
To be honest, perhaps the most worrying of all to me is if they rig (is this possible at all? it might be...) it to not support hubs or PC NICs, only DSL/cable/etc, or if they did a DSL setup but gave special preference to people going through provider X...
Also keep in mind they have more opportunities for profit in their modem stuff than in opening their servers to ethernet hookup (and thus possibly to remote attacks). You can't ping flood a Dreamcast or the server it's playing on - do they want that? (And, on a more amusing note, do we want to introduce to Dreamcat the plague upon gaming society that is LPB whining? =D)
One thing is for sure, if the modem IS soldered on, the resulting controversy could just be a fatal kick in the jimmy, after the bad ROM fiasco.
Hmm. Null modem cables were the bomb, but they're a bit slow these days. Myself, everything in my room is done either with a small hub and short patch cables, or with crossover cables for small stuff. Anything slower than 10MBit just doesn't cut it realistically these days.
Or I could just be a speed freak. I miss my 300 baud modems. =-)
Fragmentation of KDE/GNOME components...
on
KDE Looks Ahead
·
· Score: 2
I have a question to pose out there... despite the efforts to make the KDE (or GNOME if you prefer) a unified-feeling interface, it still has the distinct feel of being separated. Part of this is just the UNIX mindset - you write what you need/want, and only that, lots of small stuff over one huge program.
However, I just want to pose a question for my own notes (i.e. PLEASE comment) at what point does it become worthwhile to integrate closely related programs, and at what point is it better to keep them separate? Obviously it's different for every situation, but case examples are fine. For example, while web and e-mail may be better off separate, what about combining kpackage and kfm? (Or leave them alone and provide a third executable that does this?) This applies to libraries too. One large QT/GTK/etc library and header that does it all, separate libraries and headers for core and components?
One of the points on the dual-edged sword that is *nix is that although things are cleanly separated and non-bloated it also does make things genuinely difficult for new users to get around in. Whether or not this is a goal that should be overcome or something to leave in to preserve *nix style is a whole other brand of flamebait. =-)
Just some random thoughts that popped into my head.
But, as I said, it's year old information on what is likely to be an machine with a relatively low level of classification. DoD guidelines say that anything above level x (I don't know the #) cannot be connected to the outside Internet, and word is the Pentagon's network is not only physically set apart but encrypted on the packet level also. So it was not likely something big. (altho granted the DoD has had viruses before from people bringing in disks, a no-no as well).
Just a quick post-note: also keep in mind that this happened nearly a year ago, and just NOW got traced to Russia. That's an awfully wide margin, and would have trouble holding up even in a LA court of law.;) And as it is no doubt between the rise in hacking, nuclear proliferation, etc. things have likely changed quite a bit.
Still, it's sad. Perhaps the Pentagon should follow a short little motto: The most secure box on the earth is one that's turned off. (Or at least not connected to the internet without a firewall.)
Routing can be spoofed, after all. And because the school has ties to Russia's military, it doesn't mean the cracks (if they really happened) were driven by military forces. It could just be college CS students on the rampage, happens all the time.
I just think people need to be careful (especially with the press and its tendencies to blow up "cyberterrorism"/defacement stories) that they don't blow things out of proportion.
Build it and they will come... but not if they have to cross an ocean.
You have to write software for its users, not for your own enhancement. And the sad fact is that as it stands right now Linux is simply NOT at a level where my mother could use it. Until that point, she'll stick with buggy old Windows, because its something she can use without calling me every 10 minutes.
If I write software for geeks like me, only geeks like me are going to use it. I don't know about you guys, but when I sit down to write a bit o code, I do it with the intent of helping somebody out. Most of the people on Linux either already coded it themselves or don't need it. Whereas on Windows, people will use it.
One of the downsides of Windows opensourcing is that there really isn't the equivalent of a freshmeat out there for OS products. Also is the point that the average Windows user (say, my mother) doesn't really care about the virtues/etc of open source software, and is more likely to pick up a lesser quality boxed piece of $oftware merely because it's easier (to their perspective) than downloading it from the internet and installing it themselves. In contrast, the average Linux user is (for the most part) a bit more saavy about computers if not a self-proclaimed geek, and is in an environment where open source is practically the norm.
Two interesting mini-essays that are fairly relevant below, both from the same guy (over at geeknews); the first re why Windows programming is actually fun, and the second about Linux and the common user.
Didn't your mother tell you, don't say anything if you can't say something nice? You're entitled to your opinion, but form it first.
If you intend to call names and make blanket stereotyping statements, not even mentioning the article or what you dislike about his writing style, you come across as a 12-year old child throwing a temper tantrum - and this looks bad for us, for the Linux community, and for yourself.
If there are specific parts of Jon Katz's writing style or his previous articles that you find offensive or annoying, you can always feel free to post them to him as a private e-mail. Even if you rant, post it as e-mail, although ranting won't have much more effect.
Katz is a newbie in the Linux scene trying to report on both inside and outside topics from a newbie's point of view, and I for one think it's important to see the newbie's side and the outside world's view. And he's not a half bad writer Either. Learn from your enemies =P
In short, save the flame for e-mail, and actually find something to flame about instead of just rapid-fire insulting him. It's best for both of you.
Slashdot Mirror
Ok, at the risk of opening myself to flames, I would say that the tests (for once) look valid. Doesn't look good for Linux, and we all know Microsoft is gonna have a blast in the PR dept.
I think it is important to note though that in MS you have NT 4 to pay for, then IIS, and all the rest. So Linux certainly is cheaper, and it's uptime is better. And Linux has better SMP support. Also add in tech support (assuming you outsource for both NT and Linux) and Linux still kinda-sorta comes out on top.
IMHO (strapping on the asbestos) they both have their uses. Like it or not, there are some things that NT is simply better for. And ditto for Linux too. I personally believe Linux is a better server platform despite the Mindcraft tests because of uptime and efficiency.
Just my random unorganized thoughts.
Makes sense - personally all my friends Palms (I don't own one right now) I can't stand the input, although I'm told it's fast enough once you get to it. But, honestly, I'd rather have to learn a new input method than use a tiny tiny keyboard. And what about that researcher that found that Grafitti can cause physical problems in the hands similar to CTS or worse?
Also thought I'd make a mention - a lot of people here are talking about NDAs. Granted, an NDA gives you some legal protection. But honestly, folks. How many news sites out there have violated NDAs (this is especially bad in the consumer 3D graphics accelerator and gaming industries) to bring the scoop? Or, if it's an idea, short of notarizing what's to keep them from making a similar-but-unrelated-enough-to-pass-muster patented thingy? An NDA relies on trusting the other party, and as much as I hate our friends at the U.S. Patent Office for their shoddy checking, I likely would attempt to raise the money for getting a patent if possible before going the NDA route.
Just my $0.04.
Warning: I am by no means a lawyer.
;-)
Basically it all boils down to whom you decide to go to. There are venture capitalists who have reputations for being very ethical about this sort of thing, and others who have become known for dumping inventors and redoing it themselves, then patenting it.
My immediate thought would be to grab copies of the schematics, code if needed, etc. and have those babies notarized. Backup tapes rule. Get some solid proof that you had it first. Then see who you can talk to.
Hell, who needs venture capitalists - if it's cool and it runs Linux, you'd probably take in just as much money by putting on banner ads and posting the site here as a news item
Sega does have to make a choice between cable and DSL, though.. I don't have cable, so I'm not sure how many cable modems out there have Ethernet hookups. Also worrying are those people who are now buying DSL modems on a card instead of an external modem with Ethernet jack.
To be honest, perhaps the most worrying of all to me is if they rig (is this possible at all? it might be...) it to not support hubs or PC NICs, only DSL/cable/etc, or if they did a DSL setup but gave special preference to people going through provider X...
Also keep in mind they have more opportunities for profit in their modem stuff than in opening their servers to ethernet hookup (and thus possibly to remote attacks). You can't ping flood a Dreamcast or the server it's playing on - do they want that? (And, on a more amusing note, do we want to introduce to Dreamcat the plague upon gaming society that is LPB whining? =D)
One thing is for sure, if the modem IS soldered on, the resulting controversy could just be a fatal kick in the jimmy, after the bad ROM fiasco.
Hmm. Null modem cables were the bomb, but they're a bit slow these days. Myself, everything in my room is done either with a small hub and short patch cables, or with crossover cables for small stuff. Anything slower than 10MBit just doesn't cut it realistically these days.
Or I could just be a speed freak. I miss my 300 baud modems. =-)
I have a question to pose out there... despite the efforts to make the KDE (or GNOME if you prefer) a unified-feeling interface, it still has the distinct feel of being separated. Part of this is just the UNIX mindset - you write what you need/want, and only that, lots of small stuff over one huge program.
However, I just want to pose a question for my own notes (i.e. PLEASE comment) at what point does it become worthwhile to integrate closely related programs, and at what point is it better to keep them separate? Obviously it's different for every situation, but case examples are fine. For example, while web and e-mail may be better off separate, what about combining kpackage and kfm? (Or leave them alone and provide a third executable that does this?) This applies to libraries too. One large QT/GTK/etc library and header that does it all, separate libraries and headers for core and components?
One of the points on the dual-edged sword that is *nix is that although things are cleanly separated and non-bloated it also does make things genuinely difficult for new users to get around in. Whether or not this is a goal that should be overcome or something to leave in to preserve *nix style is a whole other brand of flamebait. =-)
Just some random thoughts that popped into my head.
s/deep trouble/federal offense/g actually.
But, as I said, it's year old information on what is likely to be an machine with a relatively low level of classification. DoD guidelines say that anything above level x (I don't know the #) cannot be connected to the outside Internet, and word is the Pentagon's network is not only physically set apart but encrypted on the packet level also. So it was not likely something big. (altho granted the DoD has had viruses before from people bringing in disks, a no-no as well).
Just a quick post-note: also keep in mind that this happened nearly a year ago, and just NOW got traced to Russia. That's an awfully wide margin, and would have trouble holding up even in a LA court of law. ;) And as it is no doubt between the rise in hacking, nuclear proliferation, etc. things have likely changed quite a bit.
Still, it's sad. Perhaps the Pentagon should follow a short little motto: The most secure box on the earth is one that's turned off. (Or at least not connected to the internet without a firewall.)
Routing can be spoofed, after all. And because the school has ties to Russia's military, it doesn't mean the cracks (if they really happened) were driven by military forces. It could just be college CS students on the rampage, happens all the time.
I just think people need to be careful (especially with the press and its tendencies to blow up "cyberterrorism"/defacement stories) that they don't blow things out of proportion.
Build it and they will come... but not if they have to cross an ocean.
You have to write software for its users, not for your own enhancement. And the sad fact is that as it stands right now Linux is simply NOT at a level where my mother could use it. Until that point, she'll stick with buggy old Windows, because its something she can use without calling me every 10 minutes.
If I write software for geeks like me, only geeks like me are going to use it. I don't know about you guys, but when I sit down to write a bit o code, I do it with the intent of helping somebody out. Most of the people on Linux either already coded it themselves or don't need it. Whereas on Windows, people will use it.
One of the downsides of Windows opensourcing is that there really isn't the equivalent of a freshmeat out there for OS products. Also is the point that the average Windows user (say, my mother) doesn't really care about the virtues/etc of open source software, and is more likely to pick up a lesser quality boxed piece of $oftware merely because it's easier (to their perspective) than downloading it from the internet and installing it themselves. In contrast, the average Linux user is (for the most part) a bit more saavy about computers if not a self-proclaimed geek, and is in an environment where open source is practically the norm.
Two interesting mini-essays that are fairly relevant below, both from the same guy (over at geeknews); the first re why Windows programming is actually fun, and the second about Linux and the common user.
Just my $0.02.
Why Penguins Can't Fly On The Desktop
Who Needs a Road Map?
Didn't your mother tell you, don't say anything if you can't say something nice? You're entitled to your opinion, but form it first.
If you intend to call names and make blanket stereotyping statements, not even mentioning the article or what you dislike about his writing style, you come across as a 12-year old child throwing a temper tantrum - and this looks bad for us, for the Linux community, and for yourself.
If there are specific parts of Jon Katz's writing style or his previous articles that you find offensive or annoying, you can always feel free to post them to him as a private e-mail. Even if you rant, post it as e-mail, although ranting won't have much more effect.
Katz is a newbie in the Linux scene trying to report on both inside and outside topics from a newbie's point of view, and I for one think it's important to see the newbie's side and the outside world's view. And he's not a half bad writer Either. Learn from your enemies =P
In short, save the flame for e-mail, and actually find something to flame about instead of just rapid-fire insulting him. It's best for both of you.