It is Orwellian to blame Linux for the lion's share of security problems, when the Microsoft platform is far less secure, as evidenced by the many Outlook related e-mail viruses. Correct me if I'm wrong, but this study doesn't include viruses, which are security vulnerabilities. Neither does it include exploits against the commonly installed Microsoft Office programs. OTOH, does the study include Linux security bugs from both the core OS and distro packages?
I apologize grievously if my assumptions are incorrect. The "winformant" article is Slashdotted, and the NT Bugtraq chart was not entirely clear to me.
This is racist and ignorant. What do you think the people who live on the equator will think of this? Would you care if they were white?
What about marine life? What about the environment?
I'm so disappointed by Slashdot. So many bright people, and so many closed minds.
The beliefs of Slashdot, in summary: (1) space elevators are obviously good and have no drawbacks at all; (2) there is no need for any patent or copyright; (3) people who blame their health symptoms on "RF fields" or cell phones not only are wrong in assessing blame, but obviously have no health symptom except mass hysteria; (4) RSI and ergonomic injuries are believable, in contrast to other maladies; (5) if there is a proposed technology involving computers or robots, it will obviously work; (6) if there is a proposed technology involving a potential new energy source, it will by definition never work (not because it is fraud, but because we have already discovered all of those); (7) spelling, grammar, and style in the English language is unimporant; (8) spelling, grammar, and style in the C language is crucial; (9) critics of Slashdot get a -1 offtopic or -1 overrated; (10) critics of critics of Slashdot get +1 interesting; (11) the Simpsons is funny; (12) making fun of Slashdot is not funny; (13) Star Office is good enough for word processing, because no real person needs to do more than type a two page letter; (14) technology never has a downside; (15) South Africa is on the equator; and (16) all the tech stocks like LNUX are coming back, soon, higher than ever.
Last December 19 on Slashdot, it was an 8 megabyte PDF, not a 15. That Slashdot article is found here.
I agree with your dire forecast. It would be terrible for such a huge thing to crash to the Earth. It could wrap around the entire Earth. Besides, this "space elevator" would be a giant, provactive, easy target for terrorists.
From the TechTV article: "Edwards admits the elevator could be a terrorist target. But, he said, "It's away from everything. There are few, if any, airline routes through there. And a few well-deployed ships would be able to protect the station, the anchor station, and the cable."
How comforting. The safety of potentially millions of people will depend on the cable being "away from everything," and on the competence of a "few" ships. How bizarrely foolish.
Among others, this "space tether" would be vulnerable to the following terrorist attacks: missle, bullet, bomb, acid, human piloted aircraft, remote controlled aircraft, ground vehicle, laser, and fire. Will those "few" ships include an aircraft carrier? Will they carry anti-missile batteries? What about the possibility of one of "our" planes accidentally running into the cable?
The true believers need to wake up. Space elevators will never be safe, and thus will never be feasible.
I was replying to a comment that rejected that proposal, and supported Linus's position.
Like I was saying, under either the "Bad Lieutenant" proposal, or the proposal in the comment I was replying to, there are problems. Although people will continue to give deference to the decisions of Linus, who will accept the authority of his lieutenants? The depth of the hierachy, in theory or practice, is irrelevant. Compared to a corporate structure where orders are given and received, Linux development proceeds in a more anarchistic fashion. While this is advantageous in many ways, it leads to scalability problems, like we are seeing today.
The real problem with these proposals is that it gives Linus zero input. For all practical purposes, all he really would have is veto power. Once Linus applies a patch that someone sends directly to him, then the authority is broken down.
I don't see how these proposals would change anything.
Linus is trying to be both lead developer and CEO. That's just too much to ask of anyone. Linus needs to stop micromanaging Linux. He doesn't have time to look at every line of code anymore, but he doesn't want to give up coding, either. The proposal doesn't suit his needs.
What you describe is not non-hierarchical, it's the opposite. If Linus is CEO, and he has 4-5 human lieutenants, who each have 4-5 human lieutenants, what you have is an org chart.
Nevertheless, there's no reason why that hierarchical system couldn't scale. The real problem is that Linux software development has no clear lines of authority, but it's organized as if there were. Everyone respects Linus, but will anyone respect his chosen lieutenants?
Replace 'BTW' with 'By the way.' Acronyms should be expanded the first time they are used.
There are certain conventions on the Internet. If this were a newspaper, I would have expanded it.
They have no responsibility to do anything. If you don't like the site - leave, or start your own at www.LanguagePendantsSlashDot.org (I doubt it's taken)... oh wait, you can't do that because there is no spaces and no tick mark in the possessive
LOL. That was really funny. BTW, the only reason I went on a rampage today was because I *do* care about Slashdot. I want to see it improved. Maybe my approach is wrong and unhelpful. We'll see if anything changes. Like you, I am pessimistic.
xah (What!!! A proper name which is not capitalized? The shame of it all is terrifying!) would do well to purchase some Valium. It's a fine sedative.
See my comment, to which you responded, where I did not suggest capitalizing "kcurtis," an obvious username. This is following the Internet convention, of course.
xah@myrealbox.com
It's called "SPAM-armoring" in Slashdot's preferences, BTW. Go ahead and spam. I only spend time reading mail that is delivered by one of my filters to one of my mail folders. The rest is spam, or cause for a new filter.
Slashdot should adopt the ordinary journalistic practice of editing submissions for grammar, spelling, punctuation, and, when absolutely necessary, style.
The analogy is to letters to the editors of newspapers. If a person sends in a letter with the word "the" spelled as "hthe," every editor of every newspaper will correct the error for publication. The Slashdot editors should do no less.
Again, I don't blame the submitters. Are the submitters paid? No. Until they are, they're not to blame for Slashdot publishing the cumulative raft of troublous language that it does.
Of course, I have made many grammatical and spelling errors myself, including on IRC.
My point is that the Slashdot editors should aim for a higher standard.
Look at our usual criticism of corporate media like Ziff-Davis. At least they don't make such obvious, such frequent errors of language in their publications as do the editors of Slashdot!
Why use the letters e-m-a-i-l together in all lowercase, when there is already "Email?" There is prececedence for capitalizing acronyms, like VAX or AMD. The same principle can apply in Email. It is cumbersome, though, in verb form. That is why e-mail is best.
My chief objection to "email" is that it breaks the usual pronunciation rules, and creates yet another exception that must be learned.
IMHO, soon will be the day when we just say "mail," because the paper kind won't exist aside from greeting cards and unsolicited offers. That will be a sad day, yet I think it is inevitable.
Slashback tonight brings you updates to previous stories on computer-class cheating, Smoothwall, AIBO hacking, the Open Source Directory, and the fate of Loki's CVS.
It's just "computer class cheating."
Read on below for the details! Jon Masters was one of the many to write in after recent articles about automated cheat-detection employed in undergraduate CS classes to catch plagiarists. "Hi, cheat detection is hardly new.
This isn't even consistent. It's either "cheat-detection" or "cheat detection." I would advise the latter.
For example The University Of Nottingham have developed an automated marking/plagarism detection system as part of their CourseMaster software.
Insert a comma after "example." It should be "the University of Nottingham has."
Personally I don't agree with automated assessment in general, however plagarism detection can be useful."
Insert commas after "Personally" and "however." Change "can" to "would."
From the email I've gotten on it, it seems like a whole passel of schools have at least a homegrown solution to CS cheats.
That's either "e-mail" or "Email."
[...] SteveMallett writes "We at Open Source Directory (OSD) have opened the directory to volunteer editors now that we've given app authors and maintainer's a good chance to start and/or maintain their own listings.
That should be "maintainers." Don't use the horrible formation "and/or." The word "or" is sufficiently ambiguous.
Unlike dmoz, which has volunteer editors, we _will_ delete unupdated or neglected editor work in accordance to our Social Contract.
Capitalize "DMOZ." The word "unupdated," is, IMNSHO, a monstrosity. How about "out of date?"
We hope that editors will help fill in the missing apps, take over those listings that they can do a better job of or have become neglected, and find those diamonds in the rough."
At this point, the language has become so bad that it is impossible to understand what is being said.
Yes, someone has to read all those emails.
It's a personal decision now on whether "e-mail" is in plural form without the suffix "s," but it simply cannot be written as "emails." If you add the "s," it's either "e-mails" or "Emails."
kcurtis writes "Boston.com's tech site has this AP article about the large response to the Court's request for comment on the MS case's proposed settlement."
As journalists, you need to be more careful in your use of the word "court." Either say "the court request," or "the United States District Court's request." (I'm not sure which court we are talking about here, so I guessed.) Regarding style, you should make it clearer who proposed the settlement.
[...]Shadow passwords are now in, but it looks like the ppp secrets file is still open (they describe it as being a "non-vulnerability").
Capitalize "PPP." Turn the words in parentheses into a different sentence.
[...] Once that site is set up we'll point the loki domains that direction. They'll also be adding some Loki projects to public CVS which were never completed."
Be consistent. Always capitalize "Loki."
Here's to a better Slashdot. The Slashdot editors would do well to purchase a copy of Garner's "Modern American Usage." It's a fine reference book.
BTW, my caustic comments are all addressed to Slashdot's editors, and not to submitters. It's Slashdot's responsibility to use good language.
The Slashdot editors are all fluent in English. They should edit comments before posting them. That's standard journalistic practice here in the US.
My comments on spelling and grammar are all directed at Slashdot, not individual posters who, as you state, may not be very fluent in English, or have the time to sit down and write something without errors. These excuses do not apply to Slashdot's editors.
As seen at Mandrake's website, Mandrake Linux 8.2 Beta seems to be available for download at different places.
That should be "from different places."
The new features include the ability to install a Mandrake as small as 65Mb on the HD, and encrypted file-system support.
It's not clear what number "65Mb" represents. The combination "a Mandrake" is nonsensical. One way to fix these problems would be to rewrite the phrase as, "to install Mandrake in as little as 65MiB." There should be no hyphen in "file system."
I guess it's the good time to report all bugs we don't want to see in the final version.
It should be "a good time." The use of the word "we" here is unnecessarily inclusive.
Very promising release, worth a look at!~
This is a fragmentary sentence that I would expect from a commercial advertisement. What is the tilde doing at the end of the sentence?
Swedish Gnuheter has a story on Nick Moffitt arranging with his X-headers in way that makes it impossible to read his email with Microsoft WebTV or Outlook Express.
The word "arranging" is misused. The verb "arrange" is transitive, and thus takes a direct object. To fix the sentence, just remove the word "with." There are various ways to shorten "electronic mail," including "Email" and "e-mail," but not "email," which would be pronounced with a soft "eh" sound.
Moffitt states: 'The folks using Outlook Express have locked themselves into a limited subset of the information that can flow over the Internet, and are blaming me personally for not limiting my transmissions to that outlook-centric subset.'
Capitalize "Outlook." The combination "Outlook-centric subset" is confusing, and should be rewritten.
See also original email (in English).
This is a fragmentary sentence. It is more appropriate in a footnote. The word "email" is a problem again.
Immoral? Or just right?" Looks like Moffit's "Who, me?" attitude is tongue in cheek, but the creative header changes here are hilarious.
No problems in the last sentences. Let's hope that starts a trend.
According to this CNN article here it looks like Verizon has beat all the other to the punch on launching the first 3g wireless network in the US.
The placement of the word "here" in this sentence is bad English. Just say, "this CNN article." Insert a comma after "article," as well. Later in the sentence, it should be "the others."
I was at a loss to find any good information on this at Verizon's website.
It's "web site."
One would thing they would want to publicize these items.
I think that's just a delay, not cutting out actual footage. In most live broadcast productions, including sports, there's a few second delay so some guy can hit a big red button when the guest speaks profanely, or something really terrible happens that they don't want to let you see, like a bench clearing brawl.
Twenty seconds seems like too much, though. Maybe five seconds?
The US Government does fund public broadcasting, including both PBS and NPR, with the "Corporation for Public Broadcasting," or CPB. The CPB is a quasi-governmental agency. Thus, Congress does not have a direct say in how CPB spends its money. A few years ago, however, the Rush Limbaugh types raised a stink over the CPB funding the supposedly liberal programs on PBS and NPR. I guess they never heard of the McLaughlin Group or Louis Ruykeyser. Public broadcasting is different in America, because in America there is no official "voice of the government" directed at citizens. We only direct the Voice of America at the rest of the world.
I found something that you could say peaked my interest.
The word is "piqued," although here it is used improperly. From M-W, it means "to excite or arouse by a provocation, challenge, or rebuff."
It seems Symantec (purchasers of former company Quarterdeck) has release DeskView/X into public domain and can be downloaded now.
It's "DesqView/X." It's "released." It's "the public domain." It's a run-on sentence.
DesqView/X was a GUI and OS extender that installed into DOS very much like MS Windows does.
Here we have an inconsistent use of tense. The last word should be "did." I wonder what "installed into DOS" could mean.
This little GUI can run X-Windows and MS Windows 3.x software and can even gateway serve MS Windows applications to remote X terminals.
It's either "X" or "X Window System." We have another run-on sentence. I wonder what "gateway serve" is. DesqView/X was both an X client and an X server, I believe. Of course, the X Client is what would run on the DesqView/X machine to be displayed on a remote X Server.
It was way ahead of its time and is a pretty decent toy to play with if you have a old 486 laying around.
Insert a comma after "time." It's "an old 486."
Anyways there is a petition being started that is petitioning Symantec to release the source code as OpenSource.
It's "open source."
I think this is a really good idea and could possiably help alot of other existing projects like WINE for example.
It's "possibly." It's "a lot." Insert a comma after WINE.
It can load X and rexec X apps with 16mb RAM for Pete sakes!
It's usually stated as "for Pete's sake," referring to Saint Peter.
How utterly abominable. What a disservice Slashdot does its readers, acting as its readers were unintelligent, and uncaring about either spelling or grammar. What a disservice Slashdot does to the English language.
It was the ol' duck and roll, the ol' feint and lunge, the ol' slice and jab. I don't know if they planned it that way, but that's how it worked. It was a strategy error that a typical Risk player would make. They should have kept two planes in the launch area, and sent just two to NYC. They forgot to cover home base. It's like they sent the catcher to third base, or brought the safety on a blitz.
Slashdot Mirror
I apologize grievously if my assumptions are incorrect. The "winformant" article is Slashdotted, and the NT Bugtraq chart was not entirely clear to me.
What about marine life? What about the environment?
I'm so disappointed by Slashdot. So many bright people, and so many closed minds.
The beliefs of Slashdot, in summary: (1) space elevators are obviously good and have no drawbacks at all; (2) there is no need for any patent or copyright; (3) people who blame their health symptoms on "RF fields" or cell phones not only are wrong in assessing blame, but obviously have no health symptom except mass hysteria; (4) RSI and ergonomic injuries are believable, in contrast to other maladies; (5) if there is a proposed technology involving computers or robots, it will obviously work; (6) if there is a proposed technology involving a potential new energy source, it will by definition never work (not because it is fraud, but because we have already discovered all of those); (7) spelling, grammar, and style in the English language is unimporant; (8) spelling, grammar, and style in the C language is crucial; (9) critics of Slashdot get a -1 offtopic or -1 overrated; (10) critics of critics of Slashdot get +1 interesting; (11) the Simpsons is funny; (12) making fun of Slashdot is not funny; (13) Star Office is good enough for word processing, because no real person needs to do more than type a two page letter; (14) technology never has a downside; (15) South Africa is on the equator; and (16) all the tech stocks like LNUX are coming back, soon, higher than ever.
If all we needed was a "hanging" beanstalk, however, why attach it to the Earth at all? Just let it blow around in the wind.
I agree with your dire forecast. It would be terrible for such a huge thing to crash to the Earth. It could wrap around the entire Earth. Besides, this "space elevator" would be a giant, provactive, easy target for terrorists.
From the TechTV article: "Edwards admits the elevator could be a terrorist target. But, he said, "It's away from everything. There are few, if any, airline routes through there. And a few well-deployed ships would be able to protect the station, the anchor station, and the cable."
How comforting. The safety of potentially millions of people will depend on the cable being "away from everything," and on the competence of a "few" ships. How bizarrely foolish.
Among others, this "space tether" would be vulnerable to the following terrorist attacks: missle, bullet, bomb, acid, human piloted aircraft, remote controlled aircraft, ground vehicle, laser, and fire. Will those "few" ships include an aircraft carrier? Will they carry anti-missile batteries? What about the possibility of one of "our" planes accidentally running into the cable?
The true believers need to wake up. Space elevators will never be safe, and thus will never be feasible.
Like I was saying, under either the "Bad Lieutenant" proposal, or the proposal in the comment I was replying to, there are problems. Although people will continue to give deference to the decisions of Linus, who will accept the authority of his lieutenants? The depth of the hierachy, in theory or practice, is irrelevant. Compared to a corporate structure where orders are given and received, Linux development proceeds in a more anarchistic fashion. While this is advantageous in many ways, it leads to scalability problems, like we are seeing today.
The real problem with these proposals is that it gives Linus zero input. For all practical purposes, all he really would have is veto power. Once Linus applies a patch that someone sends directly to him, then the authority is broken down.
I don't see how these proposals would change anything.
Linus is trying to be both lead developer and CEO. That's just too much to ask of anyone. Linus needs to stop micromanaging Linux. He doesn't have time to look at every line of code anymore, but he doesn't want to give up coding, either. The proposal doesn't suit his needs.
Nevertheless, there's no reason why that hierarchical system couldn't scale. The real problem is that Linux software development has no clear lines of authority, but it's organized as if there were. Everyone respects Linus, but will anyone respect his chosen lieutenants?
What Linus really needs is a full-time secretary.
I know, I know. "Precedent." Everybody's human.
There are certain conventions on the Internet. If this were a newspaper, I would have expanded it.
They have no responsibility to do anything. If you don't like the site - leave, or start your own at www.LanguagePendantsSlashDot.org (I doubt it's taken) ... oh wait, you can't do that because there is no spaces and no tick mark in the possessive
LOL. That was really funny. BTW, the only reason I went on a rampage today was because I *do* care about Slashdot. I want to see it improved. Maybe my approach is wrong and unhelpful. We'll see if anything changes. Like you, I am pessimistic.
xah (What!!! A proper name which is not capitalized? The shame of it all is terrifying!) would do well to purchase some Valium. It's a fine sedative.
See my comment, to which you responded, where I did not suggest capitalizing "kcurtis," an obvious username. This is following the Internet convention, of course.
xah@myrealbox.com
It's called "SPAM-armoring" in Slashdot's preferences, BTW. Go ahead and spam. I only spend time reading mail that is delivered by one of my filters to one of my mail folders. The rest is spam, or cause for a new filter.
The analogy is to letters to the editors of newspapers. If a person sends in a letter with the word "the" spelled as "hthe," every editor of every newspaper will correct the error for publication. The Slashdot editors should do no less.
Again, I don't blame the submitters. Are the submitters paid? No. Until they are, they're not to blame for Slashdot publishing the cumulative raft of troublous language that it does.
My point is that the Slashdot editors should aim for a higher standard.
Look at our usual criticism of corporate media like Ziff-Davis. At least they don't make such obvious, such frequent errors of language in their publications as do the editors of Slashdot!
I think Slashdot should standardize on one kind of English. Thus, my admonition to use "has" still holds.
My chief objection to "email" is that it breaks the usual pronunciation rules, and creates yet another exception that must be learned.
IMHO, soon will be the day when we just say "mail," because the paper kind won't exist aside from greeting cards and unsolicited offers. That will be a sad day, yet I think it is inevitable.
It's just "computer class cheating."
Read on below for the details! Jon Masters was one of the many to write in after recent articles about automated cheat-detection employed in undergraduate CS classes to catch plagiarists. "Hi, cheat detection is hardly new.
This isn't even consistent. It's either "cheat-detection" or "cheat detection." I would advise the latter.
For example The University Of Nottingham have developed an automated marking/plagarism detection system as part of their CourseMaster software.
Insert a comma after "example." It should be "the University of Nottingham has."
Personally I don't agree with automated assessment in general, however plagarism detection can be useful."
Insert commas after "Personally" and "however." Change "can" to "would."
From the email I've gotten on it, it seems like a whole passel of schools have at least a homegrown solution to CS cheats.
That's either "e-mail" or "Email."
[...] SteveMallett writes "We at Open Source Directory (OSD) have opened the directory to volunteer editors now that we've given app authors and maintainer's a good chance to start and/or maintain their own listings.
That should be "maintainers." Don't use the horrible formation "and/or." The word "or" is sufficiently ambiguous.
Unlike dmoz, which has volunteer editors, we _will_ delete unupdated or neglected editor work in accordance to our Social Contract.
Capitalize "DMOZ." The word "unupdated," is, IMNSHO, a monstrosity. How about "out of date?"
We hope that editors will help fill in the missing apps, take over those listings that they can do a better job of or have become neglected, and find those diamonds in the rough."
At this point, the language has become so bad that it is impossible to understand what is being said.
Yes, someone has to read all those emails.
It's a personal decision now on whether "e-mail" is in plural form without the suffix "s," but it simply cannot be written as "emails." If you add the "s," it's either "e-mails" or "Emails."
kcurtis writes "Boston.com's tech site has this AP article about the large response to the Court's request for comment on the MS case's proposed settlement."
As journalists, you need to be more careful in your use of the word "court." Either say "the court request," or "the United States District Court's request." (I'm not sure which court we are talking about here, so I guessed.) Regarding style, you should make it clearer who proposed the settlement.
[...]Shadow passwords are now in, but it looks like the ppp secrets file is still open (they describe it as being a "non-vulnerability").
Capitalize "PPP." Turn the words in parentheses into a different sentence.
[...] Once that site is set up we'll point the loki domains that direction. They'll also be adding some Loki projects to public CVS which were never completed."
Be consistent. Always capitalize "Loki."
Here's to a better Slashdot. The Slashdot editors would do well to purchase a copy of Garner's "Modern American Usage." It's a fine reference book.
BTW, my caustic comments are all addressed to Slashdot's editors, and not to submitters. It's Slashdot's responsibility to use good language.
My comments on spelling and grammar are all directed at Slashdot, not individual posters who, as you state, may not be very fluent in English, or have the time to sit down and write something without errors. These excuses do not apply to Slashdot's editors.
That should be "from different places."
The new features include the ability to install a Mandrake as small as 65Mb on the HD, and encrypted file-system support.
It's not clear what number "65Mb" represents. The combination "a Mandrake" is nonsensical. One way to fix these problems would be to rewrite the phrase as, "to install Mandrake in as little as 65MiB." There should be no hyphen in "file system."
I guess it's the good time to report all bugs we don't want to see in the final version.
It should be "a good time." The use of the word "we" here is unnecessarily inclusive.
Very promising release, worth a look at!~
This is a fragmentary sentence that I would expect from a commercial advertisement. What is the tilde doing at the end of the sentence?
Grade F.
The word "arranging" is misused. The verb "arrange" is transitive, and thus takes a direct object. To fix the sentence, just remove the word "with." There are various ways to shorten "electronic mail," including "Email" and "e-mail," but not "email," which would be pronounced with a soft "eh" sound.
Moffitt states: 'The folks using Outlook Express have locked themselves into a limited subset of the information that can flow over the Internet, and are blaming me personally for not limiting my transmissions to that outlook-centric subset.'
Capitalize "Outlook." The combination "Outlook-centric subset" is confusing, and should be rewritten.
See also original email (in English).
This is a fragmentary sentence. It is more appropriate in a footnote. The word "email" is a problem again.
Immoral? Or just right?" Looks like Moffit's "Who, me?" attitude is tongue in cheek, but the creative header changes here are hilarious.
No problems in the last sentences. Let's hope that starts a trend.
The placement of the word "here" in this sentence is bad English. Just say, "this CNN article." Insert a comma after "article," as well. Later in the sentence, it should be "the others."
I was at a loss to find any good information on this at Verizon's website.
It's "web site."
One would thing they would want to publicize these items.
It's "think."
Yet another horrifying misuse of language.
That would fit in nicely with Slashdot's subversive campaign to destroy the English language.
Twenty seconds seems like too much, though. Maybe five seconds?
The US Government does fund public broadcasting, including both PBS and NPR, with the "Corporation for Public Broadcasting," or CPB. The CPB is a quasi-governmental agency. Thus, Congress does not have a direct say in how CPB spends its money. A few years ago, however, the Rush Limbaugh types raised a stink over the CPB funding the supposedly liberal programs on PBS and NPR. I guess they never heard of the McLaughlin Group or Louis Ruykeyser. Public broadcasting is different in America, because in America there is no official "voice of the government" directed at citizens. We only direct the Voice of America at the rest of the world.
The word is "piqued," although here it is used improperly. From M-W, it means "to excite or arouse by a provocation, challenge, or rebuff."
It seems Symantec (purchasers of former company Quarterdeck) has release DeskView/X into public domain and can be downloaded now.
It's "DesqView/X." It's "released." It's "the public domain." It's a run-on sentence.
DesqView/X was a GUI and OS extender that installed into DOS very much like MS Windows does.
Here we have an inconsistent use of tense. The last word should be "did." I wonder what "installed into DOS" could mean.
This little GUI can run X-Windows and MS Windows 3.x software and can even gateway serve MS Windows applications to remote X terminals.
It's either "X" or "X Window System." We have another run-on sentence. I wonder what "gateway serve" is. DesqView/X was both an X client and an X server, I believe. Of course, the X Client is what would run on the DesqView/X machine to be displayed on a remote X Server.
It was way ahead of its time and is a pretty decent toy to play with if you have a old 486 laying around.
Insert a comma after "time." It's "an old 486."
Anyways there is a petition being started that is petitioning Symantec to release the source code as OpenSource.
It's "open source."
I think this is a really good idea and could possiably help alot of other existing projects like WINE for example.
It's "possibly." It's "a lot." Insert a comma after WINE.
It can load X and rexec X apps with 16mb RAM for Pete sakes!
It's usually stated as "for Pete's sake," referring to Saint Peter.
How utterly abominable. What a disservice Slashdot does its readers, acting as its readers were unintelligent, and uncaring about either spelling or grammar. What a disservice Slashdot does to the English language.
I wonder what that nebula sounds like.
It was the ol' duck and roll, the ol' feint and lunge, the ol' slice and jab. I don't know if they planned it that way, but that's how it worked. It was a strategy error that a typical Risk player would make. They should have kept two planes in the launch area, and sent just two to NYC. They forgot to cover home base. It's like they sent the catcher to third base, or brought the safety on a blitz.
Maybe it's broken on just your platform. I'd encourage you to post a bug report to bugzilla.mozilla.org.
The new litany for anyone who was hurt by a DoS attack should be, "Did you install IPv6?"
It can't be perfectly secure, but it would improve the situation.