<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article10_01_18_1924201</id>
	<title>ReactOS Being Rewritten, Gets Wine Infusion</title>
	<author>ScuttleMonkey</author>
	<datestamp>1263802320000</datestamp>
	<htmltext>xlotlu writes <i>"ReactOS was meant as a free and open-source operating system, binary-compatible with Microsoft Windows. But after 11 years in development it never reached a satisfactory level of usability.  Due to lack of developers, reimplementing the Win32 subsystem proved to be a much too complex task, holding the project back. Given the deficiencies of the current implementation, developer Aleksey Bragin decided to <a href="http://www.reactos.org/wiki/Arwinss">rewrite it from scratch</a>, drawing heavily from the Wine project.  Bragin's announcement on the ReactOS mailing list makes a <a href="http://www.reactos.org/archives/public/ros-dev/2010-January/012709.html">compelling argument for this decision</a>."</i></htmltext>
<tokenext>xlotlu writes " ReactOS was meant as a free and open-source operating system , binary-compatible with Microsoft Windows .
But after 11 years in development it never reached a satisfactory level of usability .
Due to lack of developers , reimplementing the Win32 subsystem proved to be a much too complex task , holding the project back .
Given the deficiencies of the current implementation , developer Aleksey Bragin decided to rewrite it from scratch , drawing heavily from the Wine project .
Bragin 's announcement on the ReactOS mailing list makes a compelling argument for this decision .
"</tokentext>
<sentencetext>xlotlu writes "ReactOS was meant as a free and open-source operating system, binary-compatible with Microsoft Windows.
But after 11 years in development it never reached a satisfactory level of usability.
Due to lack of developers, reimplementing the Win32 subsystem proved to be a much too complex task, holding the project back.
Given the deficiencies of the current implementation, developer Aleksey Bragin decided to rewrite it from scratch, drawing heavily from the Wine project.
Bragin's announcement on the ReactOS mailing list makes a compelling argument for this decision.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812304</id>
	<title>Re:Just use Windows</title>
	<author>Anonymous</author>
	<datestamp>1263807780000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>I'll probably get modded down for this, but if you want to run UNIX binaries, run Solaris. I don't ask Sun to let me run Solaris or AIX Apps on my Solaris 7 OS. If I want to run a SCO App (Which I do occasionally) I either do it on my SCO Server or a SCO VM within my Solaris OS. Trying to build Cross OS support in to an OS seems like something that would cause extensive bloating.</htmltext>
<tokenext>I 'll probably get modded down for this , but if you want to run UNIX binaries , run Solaris .
I do n't ask Sun to let me run Solaris or AIX Apps on my Solaris 7 OS .
If I want to run a SCO App ( Which I do occasionally ) I either do it on my SCO Server or a SCO VM within my Solaris OS .
Trying to build Cross OS support in to an OS seems like something that would cause extensive bloating .</tokentext>
<sentencetext>I'll probably get modded down for this, but if you want to run UNIX binaries, run Solaris.
I don't ask Sun to let me run Solaris or AIX Apps on my Solaris 7 OS.
If I want to run a SCO App (Which I do occasionally) I either do it on my SCO Server or a SCO VM within my Solaris OS.
Trying to build Cross OS support in to an OS seems like something that would cause extensive bloating.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30815934</id>
	<title>Re:Re-reactOS?</title>
	<author>BronsCon</author>
	<datestamp>1263833580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>FortifiedWine</p></htmltext>
<tokenext>FortifiedWine</tokentext>
<sentencetext>FortifiedWine</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812868</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813450</id>
	<title>Do not follow in the footsteps of Duke Nukem!</title>
	<author>Anonymous</author>
	<datestamp>1263813540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I have been waiting for ROS to reach usability as a legacy gaming platform that can use windows drivers. It seemed promicing when I tried it before. I do not recommend re-writing it from scratch, because much work will be thrown out and I am afraid it will end up like Duke Nukem Forever.</p></htmltext>
<tokenext>I have been waiting for ROS to reach usability as a legacy gaming platform that can use windows drivers .
It seemed promicing when I tried it before .
I do not recommend re-writing it from scratch , because much work will be thrown out and I am afraid it will end up like Duke Nukem Forever .</tokentext>
<sentencetext>I have been waiting for ROS to reach usability as a legacy gaming platform that can use windows drivers.
It seemed promicing when I tried it before.
I do not recommend re-writing it from scratch, because much work will be thrown out and I am afraid it will end up like Duke Nukem Forever.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812252</id>
	<title>What version, and how much?</title>
	<author>tepples</author>
	<datestamp>1263807600000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p><div class="quote"><p>I'll probably get modded down for this, but if you want to run Win32 binaries, run Windows.</p></div><p>What version of Windows? The one that comes preinstalled on most PCs nowadays, or the one that Microsoft still sells? The last time I read the front page of ReactOS.org, the project's mission was to clone Windows XP and Windows Server 2003 and specifically their device driver environment. (Windows Vista and Windows 7 have a different driver model.) Then you get to the issue where a retail copy of Windows for use in Parallels Desktop is no cheaper than a Wii-size Acer Aspire Revo PC with preinstalled Windows for use in KVM Switch.</p></div>
	</htmltext>
<tokenext>I 'll probably get modded down for this , but if you want to run Win32 binaries , run Windows.What version of Windows ?
The one that comes preinstalled on most PCs nowadays , or the one that Microsoft still sells ?
The last time I read the front page of ReactOS.org , the project 's mission was to clone Windows XP and Windows Server 2003 and specifically their device driver environment .
( Windows Vista and Windows 7 have a different driver model .
) Then you get to the issue where a retail copy of Windows for use in Parallels Desktop is no cheaper than a Wii-size Acer Aspire Revo PC with preinstalled Windows for use in KVM Switch .</tokentext>
<sentencetext>I'll probably get modded down for this, but if you want to run Win32 binaries, run Windows.What version of Windows?
The one that comes preinstalled on most PCs nowadays, or the one that Microsoft still sells?
The last time I read the front page of ReactOS.org, the project's mission was to clone Windows XP and Windows Server 2003 and specifically their device driver environment.
(Windows Vista and Windows 7 have a different driver model.
) Then you get to the issue where a retail copy of Windows for use in Parallels Desktop is no cheaper than a Wii-size Acer Aspire Revo PC with preinstalled Windows for use in KVM Switch.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812680</id>
	<title>Re:Misleading summary</title>
	<author>Saint Stephen</author>
	<datestamp>1263809820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Maybe they can run Mono on it and have a big ol' circle jerk<nobr> <wbr></nobr>:-)</p></htmltext>
<tokenext>Maybe they can run Mono on it and have a big ol ' circle jerk : - )</tokentext>
<sentencetext>Maybe they can run Mono on it and have a big ol' circle jerk :-)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812032</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813374</id>
	<title>Re:Re-reactOS?</title>
	<author>Anonymous</author>
	<datestamp>1263813240000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>why not just Tschernobyl?</p></htmltext>
<tokenext>why not just Tschernobyl ?</tokentext>
<sentencetext>why not just Tschernobyl?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812056</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812724</id>
	<title>Re:Re-reactOS?</title>
	<author>Anonymous</author>
	<datestamp>1263810000000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>ReactOSForever</p></htmltext>
<tokenext>ReactOSForever</tokentext>
<sentencetext>ReactOSForever</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812056</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812242</id>
	<title>Re:Just use Windows</title>
	<author>Anonymous</author>
	<datestamp>1263807540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Even better, get the best of both worlds and run Windows in a VM on Linux as the host. That way when your Windows installation gets crusty simply revert to the original image.  Saves tons of time with reinstalling the OS and apps.</p><p>If it's a gaming rig then your scenario is better in the long run.</p></htmltext>
<tokenext>Even better , get the best of both worlds and run Windows in a VM on Linux as the host .
That way when your Windows installation gets crusty simply revert to the original image .
Saves tons of time with reinstalling the OS and apps.If it 's a gaming rig then your scenario is better in the long run .</tokentext>
<sentencetext>Even better, get the best of both worlds and run Windows in a VM on Linux as the host.
That way when your Windows installation gets crusty simply revert to the original image.
Saves tons of time with reinstalling the OS and apps.If it's a gaming rig then your scenario is better in the long run.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30811916</id>
	<title>Ummm...</title>
	<author>Anonymous</author>
	<datestamp>1263806100000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>If it's based on Wine, why not just put their energy into Wine?</p></htmltext>
<tokenext>If it 's based on Wine , why not just put their energy into Wine ?</tokentext>
<sentencetext>If it's based on Wine, why not just put their energy into Wine?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813472</id>
	<title>It's a shame that Novell doesn't pick up this.</title>
	<author>Anonymous</author>
	<datestamp>1263813600000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Just to see what Microsoft would do to a company that's implement their own version of<nobr> <wbr></nobr>.NET and a Windows-like OS.</p></htmltext>
<tokenext>Just to see what Microsoft would do to a company that 's implement their own version of .NET and a Windows-like OS .</tokentext>
<sentencetext>Just to see what Microsoft would do to a company that's implement their own version of .NET and a Windows-like OS.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30814410</id>
	<title>Focus on Mono?</title>
	<author>macintard</author>
	<datestamp>1263819120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>How about contributing to some cross-platform<nobr> <wbr></nobr>.Net development in the form of Mono?  <a href="http://www.mono-project.com/Mono:Runtime" title="mono-project.com" rel="nofollow">http://www.mono-project.com/Mono:Runtime</a> [mono-project.com]</htmltext>
<tokenext>How about contributing to some cross-platform .Net development in the form of Mono ?
http : //www.mono-project.com/Mono : Runtime [ mono-project.com ]</tokentext>
<sentencetext>How about contributing to some cross-platform .Net development in the form of Mono?
http://www.mono-project.com/Mono:Runtime [mono-project.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30814492</id>
	<title>Re:Re-reactOS?</title>
	<author>noidentity</author>
	<datestamp>1263819780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Maybe they could rename it to Kalahari and tell users it's a new Reac.. a new OS.</htmltext>
<tokenext>Maybe they could rename it to Kalahari and tell users it 's a new Reac.. a new OS .</tokentext>
<sentencetext>Maybe they could rename it to Kalahari and tell users it's a new Reac.. a new OS.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812056</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812868</id>
	<title>Re:Re-reactOS?</title>
	<author>Ken\_g6</author>
	<datestamp>1263810660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>But it's ReactOS + the good parts of Wine.  How about DistilledOS?</p></htmltext>
<tokenext>But it 's ReactOS + the good parts of Wine .
How about DistilledOS ?</tokentext>
<sentencetext>But it's ReactOS + the good parts of Wine.
How about DistilledOS?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812056</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30814432</id>
	<title>ReactOS as a waste of time</title>
	<author>Anonymous</author>
	<datestamp>1263819240000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>When it works perfectly, they'll have an open source OS that's obsolete by about 15 years.  Sounds like a great use of time.  After this, they can go pour their efforts into some other go nowhere projects like Free/Net/OpenBSD, Haiku, open source GPU drivers, and Slashdot.</p></htmltext>
<tokenext>When it works perfectly , they 'll have an open source OS that 's obsolete by about 15 years .
Sounds like a great use of time .
After this , they can go pour their efforts into some other go nowhere projects like Free/Net/OpenBSD , Haiku , open source GPU drivers , and Slashdot .</tokentext>
<sentencetext>When it works perfectly, they'll have an open source OS that's obsolete by about 15 years.
Sounds like a great use of time.
After this, they can go pour their efforts into some other go nowhere projects like Free/Net/OpenBSD, Haiku, open source GPU drivers, and Slashdot.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813004</id>
	<title>Is it that hard</title>
	<author>Anonymous</author>
	<datestamp>1263811380000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>Is it that hard to be bug for bug compatible with Windows?  I guess writing bugs is an art to itself</p></htmltext>
<tokenext>Is it that hard to be bug for bug compatible with Windows ?
I guess writing bugs is an art to itself</tokentext>
<sentencetext>Is it that hard to be bug for bug compatible with Windows?
I guess writing bugs is an art to itself</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30814080</id>
	<title>Windows Driver Compatibility layer...</title>
	<author>jameskojiro</author>
	<datestamp>1263816960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>All they need is some sort of layer that would allow Linux to use Windows Drivers.</p></htmltext>
<tokenext>All they need is some sort of layer that would allow Linux to use Windows Drivers .</tokentext>
<sentencetext>All they need is some sort of layer that would allow Linux to use Windows Drivers.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812778</id>
	<title>Re:Misleading summary</title>
	<author>Anonymous</author>
	<datestamp>1263810300000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p><div class="quote"><p>Clearly some people think a complete, Open Source, Windows-compatible OS has some real value.</p></div><p>I use ReactOS to test some <a href="http://www.mingw.org/" title="mingw.org">MinGW</a> [mingw.org] - based programs I write for windows.<br>I find the EULA for Windows <a href="http://www.theregister.co.uk/2002/08/02/microsoft\_eula\_asks\_for\_root" title="theregister.co.uk">unacceptable</a> [theregister.co.uk].<br>But I still want my software to run on it.</p></div>
	</htmltext>
<tokenext>Clearly some people think a complete , Open Source , Windows-compatible OS has some real value.I use ReactOS to test some MinGW [ mingw.org ] - based programs I write for windows.I find the EULA for Windows unacceptable [ theregister.co.uk ] .But I still want my software to run on it .</tokentext>
<sentencetext>Clearly some people think a complete, Open Source, Windows-compatible OS has some real value.I use ReactOS to test some MinGW [mingw.org] - based programs I write for windows.I find the EULA for Windows unacceptable [theregister.co.uk].But I still want my software to run on it.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812032</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30817034</id>
	<title>ReactOS is dead. Long live etc etc etc</title>
	<author>NMEismyNME</author>
	<datestamp>1263892500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This is a really interesting project. Wine is an incredible piece of software and if ARWINSS can increase the amount of collaboration between ReactOS and Wine and bring a driver-compatible NT replacement closer to reality then that's a great thing.
</p><p>
I would, however, hope that ARWINSS doesn't swallow up ReactOS whole because - while ReactOS is a fairly slow moving and cumbersome beast - it still has an extremely worthwhile goal. Even if it takes 5 years for ReactOS to reach functional beta stage, win32 software and obsolete hardware with win32 only drivers is still going to be out there. Why not use it if we can make it work?
</p></htmltext>
<tokenext>This is a really interesting project .
Wine is an incredible piece of software and if ARWINSS can increase the amount of collaboration between ReactOS and Wine and bring a driver-compatible NT replacement closer to reality then that 's a great thing .
I would , however , hope that ARWINSS does n't swallow up ReactOS whole because - while ReactOS is a fairly slow moving and cumbersome beast - it still has an extremely worthwhile goal .
Even if it takes 5 years for ReactOS to reach functional beta stage , win32 software and obsolete hardware with win32 only drivers is still going to be out there .
Why not use it if we can make it work ?</tokentext>
<sentencetext>This is a really interesting project.
Wine is an incredible piece of software and if ARWINSS can increase the amount of collaboration between ReactOS and Wine and bring a driver-compatible NT replacement closer to reality then that's a great thing.
I would, however, hope that ARWINSS doesn't swallow up ReactOS whole because - while ReactOS is a fairly slow moving and cumbersome beast - it still has an extremely worthwhile goal.
Even if it takes 5 years for ReactOS to reach functional beta stage, win32 software and obsolete hardware with win32 only drivers is still going to be out there.
Why not use it if we can make it work?
</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30814886</id>
	<title>Re:A reason not to rewrite React....</title>
	<author>izomiac</author>
	<datestamp>1263822720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Well, if ReactOS was a usable Windows replacement then you'd open up the option of using a completely open source system for Windows users that would rather not relearn how to use a computer.  Businesses could be guaranteed that their legacy software has a very good chance of working with new hardware since they aren't beholden to Microsoft's corporate decisions.  Furthermore, big businesses could roll their own version of ReactOS that best fit their own needs.<br> <br>
ReactOS has the potential to drastically weaken the Windows dominance of the desktop PC.  Once the monopoly is broken then competition explodes, much like how Firefox paved the way for Opera, Chrome, and others.  The small players, in turn, force the big ones to keep up with innovation.  So, to address your point, ReactOS becoming usable would force Windows and Linux to both improve, which is a win.</htmltext>
<tokenext>Well , if ReactOS was a usable Windows replacement then you 'd open up the option of using a completely open source system for Windows users that would rather not relearn how to use a computer .
Businesses could be guaranteed that their legacy software has a very good chance of working with new hardware since they are n't beholden to Microsoft 's corporate decisions .
Furthermore , big businesses could roll their own version of ReactOS that best fit their own needs .
ReactOS has the potential to drastically weaken the Windows dominance of the desktop PC .
Once the monopoly is broken then competition explodes , much like how Firefox paved the way for Opera , Chrome , and others .
The small players , in turn , force the big ones to keep up with innovation .
So , to address your point , ReactOS becoming usable would force Windows and Linux to both improve , which is a win .</tokentext>
<sentencetext>Well, if ReactOS was a usable Windows replacement then you'd open up the option of using a completely open source system for Windows users that would rather not relearn how to use a computer.
Businesses could be guaranteed that their legacy software has a very good chance of working with new hardware since they aren't beholden to Microsoft's corporate decisions.
Furthermore, big businesses could roll their own version of ReactOS that best fit their own needs.
ReactOS has the potential to drastically weaken the Windows dominance of the desktop PC.
Once the monopoly is broken then competition explodes, much like how Firefox paved the way for Opera, Chrome, and others.
The small players, in turn, force the big ones to keep up with innovation.
So, to address your point, ReactOS becoming usable would force Windows and Linux to both improve, which is a win.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813366</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813340</id>
	<title>Mono and GTK#</title>
	<author>Anonymous</author>
	<datestamp>1263813060000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Does Mono and GTK# work on ReactOS?</p></htmltext>
<tokenext>Does Mono and GTK # work on ReactOS ?</tokentext>
<sentencetext>Does Mono and GTK# work on ReactOS?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812286</id>
	<title>Re:Just use Windows</title>
	<author>DarkOx</author>
	<datestamp>1263807720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>ReactOS is not cross platform though its a Windows workalike.  ReactOs is to Windows as gnu/Linux is to NetBSD.  Its a differnet platform but more or less intended to run the same application layer software.</p></htmltext>
<tokenext>ReactOS is not cross platform though its a Windows workalike .
ReactOs is to Windows as gnu/Linux is to NetBSD .
Its a differnet platform but more or less intended to run the same application layer software .</tokentext>
<sentencetext>ReactOS is not cross platform though its a Windows workalike.
ReactOs is to Windows as gnu/Linux is to NetBSD.
Its a differnet platform but more or less intended to run the same application layer software.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30817472</id>
	<title>Re:if you value your time</title>
	<author>xtracto</author>
	<datestamp>1263898440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>buy windows 7 and save all the pain of using WINE or ReactOS, or ReactOS on WINE. the amount of time you save in trying to get things work (wow! my apps just work without any hacks!) will very quickly pay for the cost of the windows license</p></div><p>It amazes my how low has the Slashdot crowd been dissolved with people thinking among these lines.<br>I mean, although my<nobr> <wbr></nobr>/. ID is not that low and I do not consider myself a "complete geek" (after all, I have a wife and I cope fine with the majority of my coworkers which are women), but I still find the ReactOS software an exciting and interesting challenge.</p><p>I would be interested to know what is the reason for people with an ID higher than 1000000 to join Slashdot.  I mean, if you read Slashdot's slogan is "news for nerds, stuff that matters".</p><p>THIS is news for nerds, it is related to computers and in the "free, open source software world" having a Libre version of Windows is indeed a good thing.</p><p>However, looking at most comments from this thread in particular and other similar Slashdot threads in general, the discussion just centers in arguing whether it is something right or wrong... Compare that to <a href="http://developers.slashdot.org/article.pl?sid=03/02/02/2031252" title="slashdot.org" rel="nofollow">previous (2003)</a> [slashdot.org] stories. When did the AOL crowd invaded Slashdot?</p><p>And, does anyone knows of a Slashdot-like newsfeed/forum which is not invaded by this way of thinking?</p></div>
	</htmltext>
<tokenext>buy windows 7 and save all the pain of using WINE or ReactOS , or ReactOS on WINE .
the amount of time you save in trying to get things work ( wow !
my apps just work without any hacks !
) will very quickly pay for the cost of the windows licenseIt amazes my how low has the Slashdot crowd been dissolved with people thinking among these lines.I mean , although my / .
ID is not that low and I do not consider myself a " complete geek " ( after all , I have a wife and I cope fine with the majority of my coworkers which are women ) , but I still find the ReactOS software an exciting and interesting challenge.I would be interested to know what is the reason for people with an ID higher than 1000000 to join Slashdot .
I mean , if you read Slashdot 's slogan is " news for nerds , stuff that matters " .THIS is news for nerds , it is related to computers and in the " free , open source software world " having a Libre version of Windows is indeed a good thing.However , looking at most comments from this thread in particular and other similar Slashdot threads in general , the discussion just centers in arguing whether it is something right or wrong... Compare that to previous ( 2003 ) [ slashdot.org ] stories .
When did the AOL crowd invaded Slashdot ? And , does anyone knows of a Slashdot-like newsfeed/forum which is not invaded by this way of thinking ?</tokentext>
<sentencetext>buy windows 7 and save all the pain of using WINE or ReactOS, or ReactOS on WINE.
the amount of time you save in trying to get things work (wow!
my apps just work without any hacks!
) will very quickly pay for the cost of the windows licenseIt amazes my how low has the Slashdot crowd been dissolved with people thinking among these lines.I mean, although my /.
ID is not that low and I do not consider myself a "complete geek" (after all, I have a wife and I cope fine with the majority of my coworkers which are women), but I still find the ReactOS software an exciting and interesting challenge.I would be interested to know what is the reason for people with an ID higher than 1000000 to join Slashdot.
I mean, if you read Slashdot's slogan is "news for nerds, stuff that matters".THIS is news for nerds, it is related to computers and in the "free, open source software world" having a Libre version of Windows is indeed a good thing.However, looking at most comments from this thread in particular and other similar Slashdot threads in general, the discussion just centers in arguing whether it is something right or wrong... Compare that to previous (2003) [slashdot.org] stories.
When did the AOL crowd invaded Slashdot?And, does anyone knows of a Slashdot-like newsfeed/forum which is not invaded by this way of thinking?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812884</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812300</id>
	<title>Use a cross-platform API</title>
	<author>argent</author>
	<datestamp>1263807780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If I want to run a <i>UNIX</i> app, I can do that on Windows (Interix, Cygwin, etc), OS X, Linux, HP/UX, VMS, AIX, FreeBSD, BeOS, or Xenix.</p><p>That's because it's an API that was guided, among other things, by portability. The first cross-platform UNIX emulation was the Software Tools Virtual OS, and that came out of Bell Labs. The only modern OS that hasn't been based one way or another on the UNIX API is VMS. Windows NOT excluded.</p></htmltext>
<tokenext>If I want to run a UNIX app , I can do that on Windows ( Interix , Cygwin , etc ) , OS X , Linux , HP/UX , VMS , AIX , FreeBSD , BeOS , or Xenix.That 's because it 's an API that was guided , among other things , by portability .
The first cross-platform UNIX emulation was the Software Tools Virtual OS , and that came out of Bell Labs .
The only modern OS that has n't been based one way or another on the UNIX API is VMS .
Windows NOT excluded .</tokentext>
<sentencetext>If I want to run a UNIX app, I can do that on Windows (Interix, Cygwin, etc), OS X, Linux, HP/UX, VMS, AIX, FreeBSD, BeOS, or Xenix.That's because it's an API that was guided, among other things, by portability.
The first cross-platform UNIX emulation was the Software Tools Virtual OS, and that came out of Bell Labs.
The only modern OS that hasn't been based one way or another on the UNIX API is VMS.
Windows NOT excluded.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812698</id>
	<title>Re:Just use Windows</title>
	<author>rahvin112</author>
	<datestamp>1263809880000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Because some people like the idea of FOSS. It took FreeDOS 5-8 years to fully clone 16bit MSDOS and then improve on it. Today there is a fully functioning alternative to DOS that is used extensively in the embedded space (particularly manufacturing subsystems where it's still common). By providing a fully functional clone of MS-DOS the FreeDOS people have removed the MS yoke from an entire sector of IT.</p><p>FreeDOS and ReactOS if it's successful are useful tools in dismantling the MS monopoly or making it more customer focused. Many of the DRM components in Vista and 7 wouldn't be possible if ReactOS was a fully working clone when Vista was announced. Now that MS has fully abandoned XP it gets even easier for ReactOS because they don't need to worry with MS coming in and rewriting a big chuck of win32 to obfuscate the development. ReactOS might just provide the necessary pressure for MS to dismantle the DRM subsystem in future versions of Windows if it begins gaining significant market share. This likely won't gain any traction in the retail market, but a successful implementation could destroy sales of MS licenses in the corporate climate, something MS would take very seriously as it accounts for most of the their windows income.</p></htmltext>
<tokenext>Because some people like the idea of FOSS .
It took FreeDOS 5-8 years to fully clone 16bit MSDOS and then improve on it .
Today there is a fully functioning alternative to DOS that is used extensively in the embedded space ( particularly manufacturing subsystems where it 's still common ) .
By providing a fully functional clone of MS-DOS the FreeDOS people have removed the MS yoke from an entire sector of IT.FreeDOS and ReactOS if it 's successful are useful tools in dismantling the MS monopoly or making it more customer focused .
Many of the DRM components in Vista and 7 would n't be possible if ReactOS was a fully working clone when Vista was announced .
Now that MS has fully abandoned XP it gets even easier for ReactOS because they do n't need to worry with MS coming in and rewriting a big chuck of win32 to obfuscate the development .
ReactOS might just provide the necessary pressure for MS to dismantle the DRM subsystem in future versions of Windows if it begins gaining significant market share .
This likely wo n't gain any traction in the retail market , but a successful implementation could destroy sales of MS licenses in the corporate climate , something MS would take very seriously as it accounts for most of the their windows income .</tokentext>
<sentencetext>Because some people like the idea of FOSS.
It took FreeDOS 5-8 years to fully clone 16bit MSDOS and then improve on it.
Today there is a fully functioning alternative to DOS that is used extensively in the embedded space (particularly manufacturing subsystems where it's still common).
By providing a fully functional clone of MS-DOS the FreeDOS people have removed the MS yoke from an entire sector of IT.FreeDOS and ReactOS if it's successful are useful tools in dismantling the MS monopoly or making it more customer focused.
Many of the DRM components in Vista and 7 wouldn't be possible if ReactOS was a fully working clone when Vista was announced.
Now that MS has fully abandoned XP it gets even easier for ReactOS because they don't need to worry with MS coming in and rewriting a big chuck of win32 to obfuscate the development.
ReactOS might just provide the necessary pressure for MS to dismantle the DRM subsystem in future versions of Windows if it begins gaining significant market share.
This likely won't gain any traction in the retail market, but a successful implementation could destroy sales of MS licenses in the corporate climate, something MS would take very seriously as it accounts for most of the their windows income.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30815918</id>
	<title>Rewrite from scratch?</title>
	<author>Anonymous</author>
	<datestamp>1263833340000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Oh, rewrite from scratch...</p><p>That's a typical russian approach. Usually done with a help of number of vodka bottles and few nights. Amazingly, it usually works fine, although some russian swearwords needs to be learnt, that usually used as a black magic spell to make it work flawlessly.</p></htmltext>
<tokenext>Oh , rewrite from scratch...That 's a typical russian approach .
Usually done with a help of number of vodka bottles and few nights .
Amazingly , it usually works fine , although some russian swearwords needs to be learnt , that usually used as a black magic spell to make it work flawlessly .</tokentext>
<sentencetext>Oh, rewrite from scratch...That's a typical russian approach.
Usually done with a help of number of vodka bottles and few nights.
Amazingly, it usually works fine, although some russian swearwords needs to be learnt, that usually used as a black magic spell to make it work flawlessly.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812764</id>
	<title>ReactOS...</title>
	<author>xmason</author>
	<datestamp>1263810180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>...the Duke Nukem Forever of Open Source operating systems...<nobr> <wbr></nobr>;)</p></htmltext>
<tokenext>...the Duke Nukem Forever of Open Source operating systems... ; )</tokentext>
<sentencetext>...the Duke Nukem Forever of Open Source operating systems... ;)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812954</id>
	<title>Re:Re-reactOS?</title>
	<author>maxwell demon</author>
	<datestamp>1263811020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>RewriteOS</p></htmltext>
<tokenext>RewriteOS</tokentext>
<sentencetext>RewriteOS</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812056</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30815098</id>
	<title>I'll take it</title>
	<author>Anonymous</author>
	<datestamp>1263824280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>If it works I'd take it.</p><p>I've always wanted a non-linux free OS to fool around with. Linux is just a pain to deal with for casual everyday fooling around, it might be a lot of fun for people who want to mess with Os programming themselves and good for a corporate server environment. But it's only the kernel is ever unified, and even that is missing what casual use needs for basic OS stuff. Which is why it'll never get into everyday use unless Google manages to maintain and expand Android as an easy, de-facto build for devices.</p></htmltext>
<tokenext>If it works I 'd take it.I 've always wanted a non-linux free OS to fool around with .
Linux is just a pain to deal with for casual everyday fooling around , it might be a lot of fun for people who want to mess with Os programming themselves and good for a corporate server environment .
But it 's only the kernel is ever unified , and even that is missing what casual use needs for basic OS stuff .
Which is why it 'll never get into everyday use unless Google manages to maintain and expand Android as an easy , de-facto build for devices .</tokentext>
<sentencetext>If it works I'd take it.I've always wanted a non-linux free OS to fool around with.
Linux is just a pain to deal with for casual everyday fooling around, it might be a lot of fun for people who want to mess with Os programming themselves and good for a corporate server environment.
But it's only the kernel is ever unified, and even that is missing what casual use needs for basic OS stuff.
Which is why it'll never get into everyday use unless Google manages to maintain and expand Android as an easy, de-facto build for devices.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812056</id>
	<title>Re-reactOS?</title>
	<author>Anonymous</author>
	<datestamp>1263806760000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>Maybe they should rename it?</p><p>Re-ReactOS?</p><p>ReactOSRebooted?</p></htmltext>
<tokenext>Maybe they should rename it ? Re-ReactOS ? ReactOSRebooted ?</tokentext>
<sentencetext>Maybe they should rename it?Re-ReactOS?ReactOSRebooted?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812202</id>
	<title>Good G-d! He's RIGHT!</title>
	<author>Progman3K</author>
	<datestamp>1263807420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>In the private sector, he'd get fired by his boss for trying to do the right thing and not just kludging in another feature and shipping.<br>In the OSS world, he will (hopefully) persevere and be proven right a thousand times over!<br>That's it!!! Vindicate me, baby!</p></htmltext>
<tokenext>In the private sector , he 'd get fired by his boss for trying to do the right thing and not just kludging in another feature and shipping.In the OSS world , he will ( hopefully ) persevere and be proven right a thousand times over ! That 's it ! ! !
Vindicate me , baby !</tokentext>
<sentencetext>In the private sector, he'd get fired by his boss for trying to do the right thing and not just kludging in another feature and shipping.In the OSS world, he will (hopefully) persevere and be proven right a thousand times over!That's it!!!
Vindicate me, baby!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30815818</id>
	<title>Re:What version, and how much?</title>
	<author>cbhacking</author>
	<datestamp>1263832500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>For the record, Vista and 7 have pretty good backward compatibility in the driver ABI. It's not perfect - network drivers in particular are likely to fail - but I've leaded everything from printer drivers to video drivers, all meant for XP, into Vista and they worked fine. The catch is that the installer is usually looking for a specific kernel version (5) and when it sees the Vista kernel (6) it freaks out and claims that it won't work. Using the program compatibility mode to trick the installer into thinking it's on XP or 2000 generally solved this just fine.</p><p>As a side note, this is one of the main reasons that Win7 uses kernel version number 6.1 rather than 7.0 - they made the kernel ABI 100\% compatible with Vista, and didn't want Vista driver installers to freak out at seeing a different major version number on the kernel.</p></htmltext>
<tokenext>For the record , Vista and 7 have pretty good backward compatibility in the driver ABI .
It 's not perfect - network drivers in particular are likely to fail - but I 've leaded everything from printer drivers to video drivers , all meant for XP , into Vista and they worked fine .
The catch is that the installer is usually looking for a specific kernel version ( 5 ) and when it sees the Vista kernel ( 6 ) it freaks out and claims that it wo n't work .
Using the program compatibility mode to trick the installer into thinking it 's on XP or 2000 generally solved this just fine.As a side note , this is one of the main reasons that Win7 uses kernel version number 6.1 rather than 7.0 - they made the kernel ABI 100 \ % compatible with Vista , and did n't want Vista driver installers to freak out at seeing a different major version number on the kernel .</tokentext>
<sentencetext>For the record, Vista and 7 have pretty good backward compatibility in the driver ABI.
It's not perfect - network drivers in particular are likely to fail - but I've leaded everything from printer drivers to video drivers, all meant for XP, into Vista and they worked fine.
The catch is that the installer is usually looking for a specific kernel version (5) and when it sees the Vista kernel (6) it freaks out and claims that it won't work.
Using the program compatibility mode to trick the installer into thinking it's on XP or 2000 generally solved this just fine.As a side note, this is one of the main reasons that Win7 uses kernel version number 6.1 rather than 7.0 - they made the kernel ABI 100\% compatible with Vista, and didn't want Vista driver installers to freak out at seeing a different major version number on the kernel.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812252</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812032</id>
	<title>Misleading summary</title>
	<author>Anonymous</author>
	<datestamp>1263806700000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>If you read the actual post, what this guy is doing makes a lot of sense.  He's not re-writing ReactOS from scratch, he's just taking the parts of ReactOS that have worked out reasonably well (the kernel, bootloader, etc.) and tossing the stuff that hasn't worked out so well (the Win32 API subsystem).  It just so happens that another project, WINE, did a really impressive job at getting that Win32 API layer implemented, and rather than maintaining two completely independent versions of it, piggybacking off the WINE work should make ReactOS usable relatively soon, and able to run a large number of existing Win32 applications.</p><p>Whether you think ReactOS is a sensible project or not, clearly some people think a complete, Open Source, Windows-compatible OS has some real value, and kudos to them for figuring out how to make that happen, or at least getting very close.</p></htmltext>
<tokenext>If you read the actual post , what this guy is doing makes a lot of sense .
He 's not re-writing ReactOS from scratch , he 's just taking the parts of ReactOS that have worked out reasonably well ( the kernel , bootloader , etc .
) and tossing the stuff that has n't worked out so well ( the Win32 API subsystem ) .
It just so happens that another project , WINE , did a really impressive job at getting that Win32 API layer implemented , and rather than maintaining two completely independent versions of it , piggybacking off the WINE work should make ReactOS usable relatively soon , and able to run a large number of existing Win32 applications.Whether you think ReactOS is a sensible project or not , clearly some people think a complete , Open Source , Windows-compatible OS has some real value , and kudos to them for figuring out how to make that happen , or at least getting very close .</tokentext>
<sentencetext>If you read the actual post, what this guy is doing makes a lot of sense.
He's not re-writing ReactOS from scratch, he's just taking the parts of ReactOS that have worked out reasonably well (the kernel, bootloader, etc.
) and tossing the stuff that hasn't worked out so well (the Win32 API subsystem).
It just so happens that another project, WINE, did a really impressive job at getting that Win32 API layer implemented, and rather than maintaining two completely independent versions of it, piggybacking off the WINE work should make ReactOS usable relatively soon, and able to run a large number of existing Win32 applications.Whether you think ReactOS is a sensible project or not, clearly some people think a complete, Open Source, Windows-compatible OS has some real value, and kudos to them for figuring out how to make that happen, or at least getting very close.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30818016</id>
	<title>Re:A reason not to rewrite React....</title>
	<author>Civil\_Disobedient</author>
	<datestamp>1263906720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>Many things in Unix were designed correctly to begin with, Windows was not</i></p><p>Except that 'ol pesky User Interface.  You know, the part of the operating system you have to actually LOOK AT.</p></htmltext>
<tokenext>Many things in Unix were designed correctly to begin with , Windows was notExcept that 'ol pesky User Interface .
You know , the part of the operating system you have to actually LOOK AT .</tokentext>
<sentencetext>Many things in Unix were designed correctly to begin with, Windows was notExcept that 'ol pesky User Interface.
You know, the part of the operating system you have to actually LOOK AT.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813366</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30815022</id>
	<title>The curse of the perfectionist</title>
	<author>Bertie</author>
	<datestamp>1263823800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'm probably going to get modded to hell for this, but I don't mean it in a disparaging way at all.</p><p>I can't be the only one who's noticed a tendency for open source projects to get close to completion only for the mastermind behind it to decide it's no good, scrap it and start again.  To my mind, this is a natural tendency for geeky types - they want things to be perfect and aren't usually willing to compromise on this.  When it becomes apparent that what they're working on has gone up some perceived blind alley, their natural reaction is to destroy it and try again, only this time they'll get it right.  Until some other snag appears...</p><p>And this is why sometimes, loath as most of Slashdot's readership may be to admit it, it helps to have good management keeping an eye on things.  Somebody with a sense of perspective who's able to put a little bit of distance between themselves and the project, and recognise when things are Good Enough, and then get it out the door.</p><p>The problem is that many open-source projects don't work to deadlines and are self-determined - nobody's standing over hobbyist programmers cracking the whip, things are done when they're done.  And if it's not quite how it should be, well, we'll just take a bit longer.  Until the developers get bored and move onto some new problem instead.  Just look at all the stalled projects on Sourceforge for ample proof of this.  And so with infinite dicking-around time at their disposal, our OSS developers choose to dick around - after all, the journey is in some ways more important for them than the destination, they're coding for their own amusement, not necessarily to provide the world with a service.</p><p>There's nothing wrong with this - they can spend their time how they like.  But I just wonder how often promising things have been scrapped and restarted because there was nobody around able to take a detached look at it and say "Y'know, maybe we should just get this out, and we can do the rewrite in version 2".</p></htmltext>
<tokenext>I 'm probably going to get modded to hell for this , but I do n't mean it in a disparaging way at all.I ca n't be the only one who 's noticed a tendency for open source projects to get close to completion only for the mastermind behind it to decide it 's no good , scrap it and start again .
To my mind , this is a natural tendency for geeky types - they want things to be perfect and are n't usually willing to compromise on this .
When it becomes apparent that what they 're working on has gone up some perceived blind alley , their natural reaction is to destroy it and try again , only this time they 'll get it right .
Until some other snag appears...And this is why sometimes , loath as most of Slashdot 's readership may be to admit it , it helps to have good management keeping an eye on things .
Somebody with a sense of perspective who 's able to put a little bit of distance between themselves and the project , and recognise when things are Good Enough , and then get it out the door.The problem is that many open-source projects do n't work to deadlines and are self-determined - nobody 's standing over hobbyist programmers cracking the whip , things are done when they 're done .
And if it 's not quite how it should be , well , we 'll just take a bit longer .
Until the developers get bored and move onto some new problem instead .
Just look at all the stalled projects on Sourceforge for ample proof of this .
And so with infinite dicking-around time at their disposal , our OSS developers choose to dick around - after all , the journey is in some ways more important for them than the destination , they 're coding for their own amusement , not necessarily to provide the world with a service.There 's nothing wrong with this - they can spend their time how they like .
But I just wonder how often promising things have been scrapped and restarted because there was nobody around able to take a detached look at it and say " Y'know , maybe we should just get this out , and we can do the rewrite in version 2 " .</tokentext>
<sentencetext>I'm probably going to get modded to hell for this, but I don't mean it in a disparaging way at all.I can't be the only one who's noticed a tendency for open source projects to get close to completion only for the mastermind behind it to decide it's no good, scrap it and start again.
To my mind, this is a natural tendency for geeky types - they want things to be perfect and aren't usually willing to compromise on this.
When it becomes apparent that what they're working on has gone up some perceived blind alley, their natural reaction is to destroy it and try again, only this time they'll get it right.
Until some other snag appears...And this is why sometimes, loath as most of Slashdot's readership may be to admit it, it helps to have good management keeping an eye on things.
Somebody with a sense of perspective who's able to put a little bit of distance between themselves and the project, and recognise when things are Good Enough, and then get it out the door.The problem is that many open-source projects don't work to deadlines and are self-determined - nobody's standing over hobbyist programmers cracking the whip, things are done when they're done.
And if it's not quite how it should be, well, we'll just take a bit longer.
Until the developers get bored and move onto some new problem instead.
Just look at all the stalled projects on Sourceforge for ample proof of this.
And so with infinite dicking-around time at their disposal, our OSS developers choose to dick around - after all, the journey is in some ways more important for them than the destination, they're coding for their own amusement, not necessarily to provide the world with a service.There's nothing wrong with this - they can spend their time how they like.
But I just wonder how often promising things have been scrapped and restarted because there was nobody around able to take a detached look at it and say "Y'know, maybe we should just get this out, and we can do the rewrite in version 2".</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812338</id>
	<title>ha</title>
	<author>Anonymous</author>
	<datestamp>1263807960000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><i>But after 11 years in development it never reached a satisfactory level of usability.</i>
<br>
<br>
Wait, ReactOS or Wine?</htmltext>
<tokenext>But after 11 years in development it never reached a satisfactory level of usability .
Wait , ReactOS or Wine ?</tokentext>
<sentencetext>But after 11 years in development it never reached a satisfactory level of usability.
Wait, ReactOS or Wine?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30816790</id>
	<title>Why?</title>
	<author>Anonymous</author>
	<datestamp>1263932520000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>If you like Linux, but needs access to win apps, why not just run ubuntu and wine?<br>Or Windows and and cygwin</p><p>Why spend all that time trying to make Linux binary compatible with win32<nobr> <wbr></nobr>... don't get it.</p></htmltext>
<tokenext>If you like Linux , but needs access to win apps , why not just run ubuntu and wine ? Or Windows and and cygwinWhy spend all that time trying to make Linux binary compatible with win32 ... do n't get it .</tokentext>
<sentencetext>If you like Linux, but needs access to win apps, why not just run ubuntu and wine?Or Windows and and cygwinWhy spend all that time trying to make Linux binary compatible with win32 ... don't get it.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30818758</id>
	<title>What ReactOS aims to do, Vs what it needs to be</title>
	<author>Anonymous</author>
	<datestamp>1263914160000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>ReactOS's killer feature isn't application compatibility, it is generic driver compatibility.</p><p>MS is in the inarguably comfortable position of having the people who actually engineer PC computer hardware have to pay them for the privilege of then going and writing their own drivers for their newly-developed hardware... so that the new hardware works in windows.... Then they have to pay even more (and disclose their source code to MS) to get their driver rubber stamped by MS. Then if they want windows to "Just work" with their hardware they have to pay more again to persuade MS to ship their driver with windows...</p><p>If you want an example of this "just works" phenomena, just plug a professional range Canon camera into a Windows workstation. Most manufacturer's don't bother, which interestingly the average user never blames on MS, but on the hardware manufacturer.</p><p>Contrast this with what happens when someone complains that linux "sucks" because it doesn't work with that new hardware: Some brave soul has to step to reverse engineer the hardware to the point that they can write their own driver support into linux. Asking the hardware manufacturer for details to help do this is often met with indifference or hostility.</p><p>I guess the hardware manufacturers' look at the cost of windows driver development as just another part of general development costs. Often there's no budget left for a linux driver on top of that.</p><p>The true value of ReactOS is that it could allow all of these expensively developed Windows drivers to be used. In one fell swoop, the open source world suddenly gets the hardware support that the average Windows user is long accustomed to. (And not just for network cards, which is all ndiswrapper is good for. )</p><p>In order to really gain traction, ReactOS needs to be able to fill the enthusiastic gamer niche - and why not?<br>A super lightweight operating system is exactly what is most wanted to scrape the last iota of performance out of a PC gaming rig. To do this it needs to be able to either be compatible enough for Microsoft's DirectX to be loaded, or to provide its own alternative DirectX module.  It also needs to work with ATi and nvidia drivers. With those features, it wouldn't need to have a pretty desktop.</p><p>Ideally, after installing the video card driver, a contemporary game installer with its own bundled DirectX installer should just work.</p><p>Given the way that the enthusiast gaming niche seems to drive hardware performance, it's a no-brainer. Video game software developers and video game hardware manufacturers looking for an edge will be falling over themselves to take advantage of ReactOS. This will provide the corporate backing (full-time paid programmers) that this OSS project is missing.</p><p>If this happens and Microsoft wants to maintain any relevance in this niche, it had better "play nice" and help ReactOS work with its proprietary DirectX. If they are adversarial it is ever more likely that an open source DirectX replacement will come along, and this could potentially cut MS completely out of the loop.</p><p>It is worth pointing out that at the moment, ReactOS has no plans to implement a DirectX module of its own.</p><p>Of course, it is unlikely that this will happen until ReactOS reaches the point of basic usability. It needs to deliver on both application compatibility, as well as driver compatibility.  Working in virtual machines as the developers are is counter-productive to the goal of driver compatibility, although likely necessary for the moment in order to implement what is currently missing.</p><p>Moving forward, ReactOS represents an excellent development opportunity for fine tuning the performance of demanding applications. Consider the possibility of a real-time kernel alongside customised proprietary video card drivers to enable guaranteed minimum frame rates, or perhaps production quality low latency audio performance. The possibilities for improving the reliability of mission-critical applications is endless.</p><p>The fundamental increase in security enabled by agile open source development is not to be sniffed at either. Critical vulnerability fixes in hours rather than months is known to be possible. "Many eyes" and not "broken by design" trumps "security through obscurity".</p></htmltext>
<tokenext>ReactOS 's killer feature is n't application compatibility , it is generic driver compatibility.MS is in the inarguably comfortable position of having the people who actually engineer PC computer hardware have to pay them for the privilege of then going and writing their own drivers for their newly-developed hardware... so that the new hardware works in windows.... Then they have to pay even more ( and disclose their source code to MS ) to get their driver rubber stamped by MS. Then if they want windows to " Just work " with their hardware they have to pay more again to persuade MS to ship their driver with windows...If you want an example of this " just works " phenomena , just plug a professional range Canon camera into a Windows workstation .
Most manufacturer 's do n't bother , which interestingly the average user never blames on MS , but on the hardware manufacturer.Contrast this with what happens when someone complains that linux " sucks " because it does n't work with that new hardware : Some brave soul has to step to reverse engineer the hardware to the point that they can write their own driver support into linux .
Asking the hardware manufacturer for details to help do this is often met with indifference or hostility.I guess the hardware manufacturers ' look at the cost of windows driver development as just another part of general development costs .
Often there 's no budget left for a linux driver on top of that.The true value of ReactOS is that it could allow all of these expensively developed Windows drivers to be used .
In one fell swoop , the open source world suddenly gets the hardware support that the average Windows user is long accustomed to .
( And not just for network cards , which is all ndiswrapper is good for .
) In order to really gain traction , ReactOS needs to be able to fill the enthusiastic gamer niche - and why not ? A super lightweight operating system is exactly what is most wanted to scrape the last iota of performance out of a PC gaming rig .
To do this it needs to be able to either be compatible enough for Microsoft 's DirectX to be loaded , or to provide its own alternative DirectX module .
It also needs to work with ATi and nvidia drivers .
With those features , it would n't need to have a pretty desktop.Ideally , after installing the video card driver , a contemporary game installer with its own bundled DirectX installer should just work.Given the way that the enthusiast gaming niche seems to drive hardware performance , it 's a no-brainer .
Video game software developers and video game hardware manufacturers looking for an edge will be falling over themselves to take advantage of ReactOS .
This will provide the corporate backing ( full-time paid programmers ) that this OSS project is missing.If this happens and Microsoft wants to maintain any relevance in this niche , it had better " play nice " and help ReactOS work with its proprietary DirectX .
If they are adversarial it is ever more likely that an open source DirectX replacement will come along , and this could potentially cut MS completely out of the loop.It is worth pointing out that at the moment , ReactOS has no plans to implement a DirectX module of its own.Of course , it is unlikely that this will happen until ReactOS reaches the point of basic usability .
It needs to deliver on both application compatibility , as well as driver compatibility .
Working in virtual machines as the developers are is counter-productive to the goal of driver compatibility , although likely necessary for the moment in order to implement what is currently missing.Moving forward , ReactOS represents an excellent development opportunity for fine tuning the performance of demanding applications .
Consider the possibility of a real-time kernel alongside customised proprietary video card drivers to enable guaranteed minimum frame rates , or perhaps production quality low latency audio performance .
The possibilities for improving the reliability of mission-critical applications is endless.The fundamental increase in security enabled by agile open source development is not to be sniffed at either .
Critical vulnerability fixes in hours rather than months is known to be possible .
" Many eyes " and not " broken by design " trumps " security through obscurity " .</tokentext>
<sentencetext>ReactOS's killer feature isn't application compatibility, it is generic driver compatibility.MS is in the inarguably comfortable position of having the people who actually engineer PC computer hardware have to pay them for the privilege of then going and writing their own drivers for their newly-developed hardware... so that the new hardware works in windows.... Then they have to pay even more (and disclose their source code to MS) to get their driver rubber stamped by MS. Then if they want windows to "Just work" with their hardware they have to pay more again to persuade MS to ship their driver with windows...If you want an example of this "just works" phenomena, just plug a professional range Canon camera into a Windows workstation.
Most manufacturer's don't bother, which interestingly the average user never blames on MS, but on the hardware manufacturer.Contrast this with what happens when someone complains that linux "sucks" because it doesn't work with that new hardware: Some brave soul has to step to reverse engineer the hardware to the point that they can write their own driver support into linux.
Asking the hardware manufacturer for details to help do this is often met with indifference or hostility.I guess the hardware manufacturers' look at the cost of windows driver development as just another part of general development costs.
Often there's no budget left for a linux driver on top of that.The true value of ReactOS is that it could allow all of these expensively developed Windows drivers to be used.
In one fell swoop, the open source world suddenly gets the hardware support that the average Windows user is long accustomed to.
(And not just for network cards, which is all ndiswrapper is good for.
)In order to really gain traction, ReactOS needs to be able to fill the enthusiastic gamer niche - and why not?A super lightweight operating system is exactly what is most wanted to scrape the last iota of performance out of a PC gaming rig.
To do this it needs to be able to either be compatible enough for Microsoft's DirectX to be loaded, or to provide its own alternative DirectX module.
It also needs to work with ATi and nvidia drivers.
With those features, it wouldn't need to have a pretty desktop.Ideally, after installing the video card driver, a contemporary game installer with its own bundled DirectX installer should just work.Given the way that the enthusiast gaming niche seems to drive hardware performance, it's a no-brainer.
Video game software developers and video game hardware manufacturers looking for an edge will be falling over themselves to take advantage of ReactOS.
This will provide the corporate backing (full-time paid programmers) that this OSS project is missing.If this happens and Microsoft wants to maintain any relevance in this niche, it had better "play nice" and help ReactOS work with its proprietary DirectX.
If they are adversarial it is ever more likely that an open source DirectX replacement will come along, and this could potentially cut MS completely out of the loop.It is worth pointing out that at the moment, ReactOS has no plans to implement a DirectX module of its own.Of course, it is unlikely that this will happen until ReactOS reaches the point of basic usability.
It needs to deliver on both application compatibility, as well as driver compatibility.
Working in virtual machines as the developers are is counter-productive to the goal of driver compatibility, although likely necessary for the moment in order to implement what is currently missing.Moving forward, ReactOS represents an excellent development opportunity for fine tuning the performance of demanding applications.
Consider the possibility of a real-time kernel alongside customised proprietary video card drivers to enable guaranteed minimum frame rates, or perhaps production quality low latency audio performance.
The possibilities for improving the reliability of mission-critical applications is endless.The fundamental increase in security enabled by agile open source development is not to be sniffed at either.
Critical vulnerability fixes in hours rather than months is known to be possible.
"Many eyes" and not "broken by design" trumps "security through obscurity".</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813546</id>
	<title>Re:ha</title>
	<author>Anonymous</author>
	<datestamp>1263814020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Yes.</p></htmltext>
<tokenext>Yes .</tokentext>
<sentencetext>Yes.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812338</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812884</id>
	<title>if you value your time</title>
	<author>chentiangemalc</author>
	<datestamp>1263810780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>buy windows 7 and save all the pain of using WINE or ReactOS, or ReactOS on WINE. the amount of time you save in trying to get things work (wow! my apps just work without any hacks!)  will very quickly pay for the cost of the windows license. (of course time itself doesn't buy a windows license, assuming you have an income<nobr> <wbr></nobr>;)

For me using Wine and ReactOS there is no saving *yet* - just a whole lot of wasted time. If it eventualls gets high level of compatibility/stability then great, but for now it's a great toy in my experience can waste a lot of time.</htmltext>
<tokenext>buy windows 7 and save all the pain of using WINE or ReactOS , or ReactOS on WINE .
the amount of time you save in trying to get things work ( wow !
my apps just work without any hacks !
) will very quickly pay for the cost of the windows license .
( of course time itself does n't buy a windows license , assuming you have an income ; ) For me using Wine and ReactOS there is no saving * yet * - just a whole lot of wasted time .
If it eventualls gets high level of compatibility/stability then great , but for now it 's a great toy in my experience can waste a lot of time .</tokentext>
<sentencetext>buy windows 7 and save all the pain of using WINE or ReactOS, or ReactOS on WINE.
the amount of time you save in trying to get things work (wow!
my apps just work without any hacks!
)  will very quickly pay for the cost of the windows license.
(of course time itself doesn't buy a windows license, assuming you have an income ;)

For me using Wine and ReactOS there is no saving *yet* - just a whole lot of wasted time.
If it eventualls gets high level of compatibility/stability then great, but for now it's a great toy in my experience can waste a lot of time.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30816198</id>
	<title>flogging a dead horse</title>
	<author>icepick72</author>
	<datestamp>1263837240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>People who want to run Windows will pay for it; they aren't going to opt for a free implementation that even has one difference. The days of the Window software clone is over because Linux is here to stay. There is no need for a binary compatible Windows anymore because there are good, alternative free choices.</htmltext>
<tokenext>People who want to run Windows will pay for it ; they are n't going to opt for a free implementation that even has one difference .
The days of the Window software clone is over because Linux is here to stay .
There is no need for a binary compatible Windows anymore because there are good , alternative free choices .</tokentext>
<sentencetext>People who want to run Windows will pay for it; they aren't going to opt for a free implementation that even has one difference.
The days of the Window software clone is over because Linux is here to stay.
There is no need for a binary compatible Windows anymore because there are good, alternative free choices.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813128</id>
	<title>Re:Re-reactOS?</title>
	<author>fran6gagne</author>
	<datestamp>1263811980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>ReactOS 7</htmltext>
<tokenext>ReactOS 7</tokentext>
<sentencetext>ReactOS 7</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812056</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813068</id>
	<title>Re:ha</title>
	<author>fred fleenblat</author>
	<datestamp>1263811740000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>windows</p></htmltext>
<tokenext>windows</tokentext>
<sentencetext>windows</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812338</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30816364</id>
	<title>Re:Misleading summary</title>
	<author>fm6</author>
	<datestamp>1263840240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Sure, such an OS is desirable. But is it <i> possible</i>?  The amount of effort needed boggles the mind.  You can't do something like this with a few volunteers. You need serious resources. Where are they going to come from?  Who has really, really deep pockets and a vested in making this happen?</p></htmltext>
<tokenext>Sure , such an OS is desirable .
But is it possible ?
The amount of effort needed boggles the mind .
You ca n't do something like this with a few volunteers .
You need serious resources .
Where are they going to come from ?
Who has really , really deep pockets and a vested in making this happen ?</tokentext>
<sentencetext>Sure, such an OS is desirable.
But is it  possible?
The amount of effort needed boggles the mind.
You can't do something like this with a few volunteers.
You need serious resources.
Where are they going to come from?
Who has really, really deep pockets and a vested in making this happen?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812032</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812282</id>
	<title>Re:Just use Windows</title>
	<author>h4rr4r</author>
	<datestamp>1263807720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You should get modded down, for being an idiot.</p><p>Solaris and BSD have linux binary compatibility layers, they work fine. Wine is coming along nicely and the pay for version supported LFD2 the night that game shipped. Bloat can come from many things but merely implementing another API ain't gonna be it.</p></htmltext>
<tokenext>You should get modded down , for being an idiot.Solaris and BSD have linux binary compatibility layers , they work fine .
Wine is coming along nicely and the pay for version supported LFD2 the night that game shipped .
Bloat can come from many things but merely implementing another API ai n't gon na be it .</tokentext>
<sentencetext>You should get modded down, for being an idiot.Solaris and BSD have linux binary compatibility layers, they work fine.
Wine is coming along nicely and the pay for version supported LFD2 the night that game shipped.
Bloat can come from many things but merely implementing another API ain't gonna be it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812554</id>
	<title>Re:Misleading summary</title>
	<author>Anonymous</author>
	<datestamp>1263809280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The last time I looked at the project, it was already using some user-mode libraries from Wine. I guess this was really the logical next step. Perhaps in the future the two projects could work together to create a common codebase, that only contains #ifdef ReactOS in places where differences are inevitable. I for one really hope that they can at least get ReactOS to mostly work before Microsoft drops XP support.</p></htmltext>
<tokenext>The last time I looked at the project , it was already using some user-mode libraries from Wine .
I guess this was really the logical next step .
Perhaps in the future the two projects could work together to create a common codebase , that only contains # ifdef ReactOS in places where differences are inevitable .
I for one really hope that they can at least get ReactOS to mostly work before Microsoft drops XP support .</tokentext>
<sentencetext>The last time I looked at the project, it was already using some user-mode libraries from Wine.
I guess this was really the logical next step.
Perhaps in the future the two projects could work together to create a common codebase, that only contains #ifdef ReactOS in places where differences are inevitable.
I for one really hope that they can at least get ReactOS to mostly work before Microsoft drops XP support.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812032</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102</id>
	<title>Just use Windows</title>
	<author>Anonymous</author>
	<datestamp>1263806940000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>-1</modscore>
	<htmltext><p>I'll probably get modded down for this, but if you want to run Win32 binaries, run Windows. I don't ask Microsoft to let me run Linux or OS X Apps on my Windows 7 OS. If I want to run a Linux App (Which I do occasionally) I either do it on my Linux Server or a Linux VM within my Windows OS. Trying to build Cross OS support in to an OS seems like something that would cause extensive bloating.</p></htmltext>
<tokenext>I 'll probably get modded down for this , but if you want to run Win32 binaries , run Windows .
I do n't ask Microsoft to let me run Linux or OS X Apps on my Windows 7 OS .
If I want to run a Linux App ( Which I do occasionally ) I either do it on my Linux Server or a Linux VM within my Windows OS .
Trying to build Cross OS support in to an OS seems like something that would cause extensive bloating .</tokentext>
<sentencetext>I'll probably get modded down for this, but if you want to run Win32 binaries, run Windows.
I don't ask Microsoft to let me run Linux or OS X Apps on my Windows 7 OS.
If I want to run a Linux App (Which I do occasionally) I either do it on my Linux Server or a Linux VM within my Windows OS.
Trying to build Cross OS support in to an OS seems like something that would cause extensive bloating.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30819166</id>
	<title>Re:ha</title>
	<author>bill\_mcgonigle</author>
	<datestamp>1263916440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>Wait, ReactOS or Wine?</i></p><p>Don't be silly, WINE has been unsatisfactory for <i>sixteen</i> years.</p></htmltext>
<tokenext>Wait , ReactOS or Wine ? Do n't be silly , WINE has been unsatisfactory for sixteen years .</tokentext>
<sentencetext>Wait, ReactOS or Wine?Don't be silly, WINE has been unsatisfactory for sixteen years.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812338</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30814086</id>
	<title>Re:ha</title>
	<author>markmay</author>
	<datestamp>1263817020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p> <i>But after 11 years in development it never reached a satisfactory level of usability.</i>




Wait, ReactOS or Wine?</p></div><p>Wait, wait, ReactOS, Wine, or Windows?</p></div>
	</htmltext>
<tokenext>But after 11 years in development it never reached a satisfactory level of usability .
Wait , ReactOS or Wine ? Wait , wait , ReactOS , Wine , or Windows ?</tokentext>
<sentencetext> But after 11 years in development it never reached a satisfactory level of usability.
Wait, ReactOS or Wine?Wait, wait, ReactOS, Wine, or Windows?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812338</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813566</id>
	<title>Sigh. I can only hope that</title>
	<author>Anonymous</author>
	<datestamp>1263814080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>one if these days, i'll get wine infusion, too.</p></htmltext>
<tokenext>one if these days , i 'll get wine infusion , too .</tokentext>
<sentencetext>one if these days, i'll get wine infusion, too.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30816540</id>
	<title>11 years? Minimum wage.</title>
	<author>Anonymous</author>
	<datestamp>1263842700000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>Wouldn't it have been quicker for him to just work a few hours at McDonalds and buy a damn academic version of Windows 98SE?</p></htmltext>
<tokenext>Would n't it have been quicker for him to just work a few hours at McDonalds and buy a damn academic version of Windows 98SE ?</tokentext>
<sentencetext>Wouldn't it have been quicker for him to just work a few hours at McDonalds and buy a damn academic version of Windows 98SE?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812402</id>
	<title>Unfornate name: ArwinSS</title>
	<author>Yuioup</author>
	<datestamp>1263808320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Sorry, but the first thing I read is ArwinSchutzStaffel.</p><p>Yes, I have a sick mind.</p></htmltext>
<tokenext>Sorry , but the first thing I read is ArwinSchutzStaffel.Yes , I have a sick mind .</tokentext>
<sentencetext>Sorry, but the first thing I read is ArwinSchutzStaffel.Yes, I have a sick mind.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813366</id>
	<title>A reason not to rewrite React....</title>
	<author>Anonymous</author>
	<datestamp>1263813240000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>Many things in Unix were designed correctly to begin with, Windows was not. Linux was never intended to be a binary replacement for any Unix based OS, but rather it was itself a Unix based OS. Trying to achieve binary compatibility with Windows (chasing a moving target) is not only unlikely to succeed, but if it does you still have Windows.

It's like trying to create an open source Yugo.  Maybe it can be done... maybe it can't... but even if you succeed, you've only reimplimented a bad idea. Even if you win, you still fail.</htmltext>
<tokenext>Many things in Unix were designed correctly to begin with , Windows was not .
Linux was never intended to be a binary replacement for any Unix based OS , but rather it was itself a Unix based OS .
Trying to achieve binary compatibility with Windows ( chasing a moving target ) is not only unlikely to succeed , but if it does you still have Windows .
It 's like trying to create an open source Yugo .
Maybe it can be done... maybe it ca n't... but even if you succeed , you 've only reimplimented a bad idea .
Even if you win , you still fail .</tokentext>
<sentencetext>Many things in Unix were designed correctly to begin with, Windows was not.
Linux was never intended to be a binary replacement for any Unix based OS, but rather it was itself a Unix based OS.
Trying to achieve binary compatibility with Windows (chasing a moving target) is not only unlikely to succeed, but if it does you still have Windows.
It's like trying to create an open source Yugo.
Maybe it can be done... maybe it can't... but even if you succeed, you've only reimplimented a bad idea.
Even if you win, you still fail.</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813068
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812338
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30814086
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812338
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812300
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30819166
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812338
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813546
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812338
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30817472
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812884
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812778
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812032
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30814886
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813366
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812698
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812304
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30818016
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813366
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812680
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812032
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812286
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30815934
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812868
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812056
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812724
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812056
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812554
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812032
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812954
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812056
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30814492
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812056
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812242
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30815818
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812252
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813374
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812056
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813128
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812056
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812282
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_18_1924201_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30816364
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812032
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_1924201.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30811916
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_1924201.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812102
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812698
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812282
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812304
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812300
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812242
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812286
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812252
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30815818
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_1924201.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813366
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30818016
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30814886
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_1924201.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812032
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812778
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812680
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812554
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30816364
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_1924201.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812338
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30814086
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813546
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813068
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30819166
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_1924201.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812056
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30814492
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812954
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813374
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812724
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30813128
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812868
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30815934
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_1924201.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30815022
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_1924201.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30814080
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_18_1924201.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30812884
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_18_1924201.30817472
</commentlist>
</conversation>
