Slashdot Mirror


No Respect for Windows Open Source

man_of_mr_e writes "Shaun Walker, one of the founding developers of the DotNetNuke Portal/CMS has written an interesting piece about Open Source software on the Windows platform. "It's hard being an open source project on the Microsoft platform. Because no matter how hard you try to exemplify true open source ideals, you will not get any respect from the non-Microsoft community." He also says "There are Open Source zealots who believe that unless an application is part of a stack which includes 100% Open Source services and components, that it can not claim to be Open Source. [...] But does this "stack" argument actually make any sense?""

91 of 551 comments (clear)

  1. A lot like Star Trek... by FyRE666 · · Score: 2, Insightful

    his reminds me of that Star Trek Voyager episode a friend of mine watched and told me about because I'd never watch that. The Voyager was chasing down some other Starfleet ship that had modded there ship by using direct port alien injection. They were squishing Martians or something to make warp 1000 to get back to Earth. So this story is exactly like that; the DNN team are essesntially doing a good thing (like the alien mashers getting their people home), but in a bad way (helping the evil company by providing it with free apps that promote their product).

    Personally, I don't trust them. In this case, I'd encourage them to go closed source. Nobody should be promoting the use of VBScript or whatever that crappy Basic derivitive is that people use to write ASP (I've converted a lot of this garbage to PHP/Perl, and everything I've seen written using ASP has been absolutely horrific - the worst, least optimised crap I've ever seen - hell I could do better way back when I used to sit in my high-chair bashing away on my toy learning computer - last week it was. Now I think of it, maybe this is why IIS seems slow and wobbly; it's burdened with coping with the worst "Programmers" on Earth.

    1. Re:A lot like Star Trek... by fyrie · · Score: 2, Informative
      Nobody should be promoting the use of VBScript or whatever that crappy Basic derivitive is that people use to write ASP

      It's written in VB.NET, hence the name DotNetNuke.

    2. Re:A lot like Star Trek... by rwven · · Score: 3, Funny

      oh come on... If i wrote some open source app for windows it's not like i have some secret mission to promote Microsoft. Keeping it open source just means that you can take my source-code and port it to LINUX, thus furthering your "secret mission" of linux domination. :-P

    3. Re:A lot like Star Trek... by temojen · · Score: 2, Insightful

      I've seen some pretty crappy PHP. Actually, the one I'm trying to fix right now is so bad as to lead me to believe that it was origionally written as a demonstration of insecure coding practices.

    4. Re:A lot like Star Trek... by Bogtha · · Score: 5, Informative

      Nobody should be promoting the use of VBScript or whatever that crappy Basic derivitive is that people use to write ASP

      ASP is a language-independent framework. While VBScript is popular, there are two languages shipped by default, JScript being the other. You can also install other components to allow you to use other languages, such as ActiveState's PerlScript. In this particular case, it's VB.NET, which (I believe) is substantially better than traditional ASP VBScript.

      I've converted a lot of this garbage to PHP/Perl, and everything I've seen written using ASP has been absolutely horrific - the worst, least optimised crap I've ever seen

      With all due respect, that particular complaint doesn't mean much when you are converting it to Perl and PHP, seeing as that's the way a good portion of the rest of the world feels about those languages too.

      --
      Bogtha Bogtha Bogtha
    5. Re:A lot like Star Trek... by ChatHuant · · Score: 4, Funny

      Could you explain how IIS is more secure than Apache?

      I could: Apache 2.0.x had 28 security advisories since release (2 still unpatched at the time of writing), while IIS 6.0 had only 2 until now, and they were both patched.

    6. Re:A lot like Star Trek... by jacksonj04 · · Score: 2, Insightful

      The trouble is, as you develop your skills you look over your old stuff and go "What the hell was I thinking of?" or "Damn that's a long way around..."

      --
      How many people can read hex if only you and dead people can read hex?
    7. Re:A lot like Star Trek... by Danger+Stevens · · Score: 2, Interesting

      I recognize that ASP has some advantages in the way it handles components - especially third-party components, but VBScript is a nasty language. It compromises much of it's flexibility in the name of user friendliness, but then fails to be all that friendly.

      Ruby is an example of what VBScript should have been but completely failed at. PHP is, at it's heard, a procedural language but very robust and powerful applications have been built with it that would have taken many times more lines of code were they to have been written in VBScript for ASP. WordPress, for example, is highly modular and OO. I've looked at a few of it's core functions and converted them in my head to VBScript - it usually takes about 4 times as many lines of code and an awful lot of intermediate steps to do the exact same thing.

      VBScript is okay if it's all you've got, but I wouldn't recommend anybody choose it over Ruby, PHP, or maybe even Perl.

      --
      World Changing - News for Humans, Stuff about our planet
    8. Re:A lot like Star Trek... by robertjw · · Score: 4, Funny

      That would explain the mass exodus of Apache users moving to IIS 6.

    9. Re:A lot like Star Trek... by flithm · · Score: 3, Interesting

      It's good that this is modded as funny.

      People often quote the number of security advisories against a product as evidence of how secure it is. In some cases this is warranted, but this is not one of them... a general rule: comparing closed source and open source products in this fashion is not valid.

      Most security flaws in open source programs are discovered by people looking through the code, and noticing things like unchecked buffers, etc. In closed source programs, these types of flaws are found generally through more sinister means. What this means is usually closed source vulnerabilities are less frequently reported, but when they are they are generally more serious -- not because the potential exploit is more serious, but because it's almost always guaranteed that at the time of discovery a working exploit is already loose in the wild.

      And there are many other factors involved as well. Apache does WAY more things than IIS does (when you include all of the add on modules and so forth), and this is fair to say since the security advisories include problems that relate only to modules.

      The Apache 2.0.x stream is almost 6 years old now. IIS 6.0 has only been around for about a year or so.

      It seems silly to count the number of security vulnerabilities in a new closed source product against a much older, more widely used, more complex, open source one.

      Having said all of that, I feel the need to point out that secunia.org is really not a very trustworthy source of information. There are many known IIS 6.0 exploits that don't appear on that list.

      For example:

      IIS Information Disclosure

      I just wanted to say that you really can't do such a comparison.

    10. Re:A lot like Star Trek... by MrBlack · · Score: 2, Informative

      IIS has plenty of modules and add-ins (like Apache) via ISAPI - lots of vulnerabilities in IIS5 were vulnerabilities in crappier extensions that were loaded by default. IIS6 ships with far fewer things "ON" and thus is more secure. IIS6 has been out for over 2 years now, and there are plenty of people (both black hats and white hats) trying to break IIS 6 (e-eye for example, which virtuall specialize in IIS - http://www.eeye.com/html/research/index.html).

  2. Open source is... by Sinryc · · Score: 5, Insightful

    Open source is open source, no matter what platform. Just because you use Windows does not mean that you beleive that everything should be DRMed or closed. If you write something open souce, you know what, thats good enough for me.

    --
    Yay, I have a sig.
    1. Re:Open source is... by Anonymous Coward · · Score: 5, Insightful

      Open source is open source, no matter what platform. Just because you use Windows does not mean that you beleive that everything should be DRMed or closed. If you write something open souce, you know what, thats good enough for me.

      The problem arises when a particular free, open source app relies on a proprietary library. Then in order to modify/compile the source, you need the proprietary lib (which costs money and is usually not modifiable), thus negating the "free and open" part of the situation.

    2. Re:Open source is... by Short+Circuit · · Score: 4, Insightful

      That's why we have different Open Source licenses. There's the GPL, LGPL, BSD, etc.

      Each is tailored to a different situation. And let's not get into a debate about Open Source vs. Free Software. Not again. Please. For the curious, read this and this, instead. Or just do a search for open source vs free software.

    3. Re:Open source is... by happymellon · · Score: 3, Informative

      To resolve this issue make sure you can run on http://www.reactos.org/

    4. Re:Open source is... by Short+Circuit · · Score: 3, Funny

      Yeah, well, according to those guys, Microsoft beats sex. I'd be a little leary of them...

    5. Re:Open source is... by NutscrapeSucks · · Score: 2, Insightful

      Why is this a problem? There's tons of Open Source which exists solely to interact with propertary libraries. (See VirtualDub and most Windows video open source software.)

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    6. Re:Open source is... by Anonymous Coward · · Score: 2, Insightful

      The problem arises when a particular free, open source app relies on a proprietary library.

      You mean like KDE?

      For the uninitiated, KDE is not "free" on the Windows platform, nor is it even LGPL on any platform. This is because of the proprietary Qt library on which it is based. Here's a price list.

      This means it is easier and cheaper to write and deploy software for Microsoft Windows than KDE. I really do not understand how anybody can badmouth Windows and then turn around and praise KDE when in some respects it's even worse. FYI, Qt / KDE is also the main reason that Gnome (a desktop environment that isn't crippled by it's licence) even exists.

    7. Re:Open source is... by zsau · · Score: 5, Insightful

      The thing is, Free Software vs Open Source is precisely what this is about. DotNetNuke is clearely properly open source, and another open source developer couldn't criticise him because of that, unless they misunderstand what open source is.

      A free software developer, tho, could; he's almost as bad as a proprietery software developer--possibly worse--because, even though there's an adequate (perhaps not perfect) environment for which Shaun Walker could've written his tool using solely free software, he's encouraging people to stick with the proprietry base. His software is one of the temptations that we need to avoid if we're to obtain a fully free-software world.

      So yes: As an open-source developer, Walker has a legitimate complaint. As a free-software developer, he doesn't.

      (In case you're wondering, no, I have no idea how to spell "propriet[|a|e]ry".)

      --
      Look out!
    8. Re:Open source is... by TrancePhreak · · Score: 2, Funny

      But according to these "guys", Microsoft beats Open Source. I'd be a little leary of them.

      --

      -]Phreak Out[-
    9. Re:Open source is... by hikerhat · · Score: 4, Insightful

      Huh. I run all my software, even my linux box, on a non free, non modifiable CPU. Why do you draw the line at the software/hardware boundry? Don't forget that functionality that is provided by free open source software on some systems is provided by proprietary hardware on other systems. Consider RISC vs CISC processors, or graphics accelerators. If software is distributed under an open source license, even if it requires non-free (as in beer or freedom) components then I consider it free (as in freedom, not beer) and open. Sure, not everyone can afford the platform it runs on, but that's true of any software out there (unless your computer 'fell off the back of a truck' or was otherwise aquired for free).

    10. Re:Open source is... by Keith+Russell · · Score: 3, Informative

      Well, that's not quite true anymore. KDE 3.x is based on Qt 3. Version 3 was never released under an OSI-compliant license, so there was no legal way to port it, short of porting the Linux/GPL version of Qt 3. That was in progress for a while.

      Trolltech has since released Qt 4 for Windows under the GPL. That means that there are no longer any licensing issues preventing anyone from developing a Windows port of KDE 4. The core KDE libraries would have to be ported, but the underlying Qt libraries are already available and Free.

      --
      This sig intentionally left blank.
    11. Re:Open source is... by RoLi · · Score: 2, Insightful
      I run all my software, even my linux box, on a non free, non modifiable CPU. Why do you draw the line at the software/hardware boundry?

      By using this weasely phrase, you should already know.

      The point is that the IA32 commands (like those of most other CPUs as well) are all very well documented and open. In the case of IA32, there are even multiple vendors available. Also anybody can look up what exactly each command does.

      This makes it possible to compile most OSS software on many different CPUs.

      Windows on the other hand is completely closed. It is almost impossible to port an OSS project on the Windows-platform to anything else. (See Virtualdub as an example. It is Windows-only and will stay that way)

    12. Re:Open source is... by jc42 · · Score: 2, Insightful

      Open source is open source, no matter what platform. ... If you write something open souce, you know what, thats good enough for me.

      Well, yes and no. One important issue that seems obscured by this way of framing the issue is the practical reason for wanting "open source": If you want reliable software, you need access to the source for all the software. Not just the app you're running, but all its libraries. And the system calls that it makes. And, ultimately, the hardware diagrams for the processor.

      If you reframe it as a "software quality" issue, it becomes clearer. As a programmer, I often point out that, on a closed platform like Windows, I can't guarantee the behavior of any of my code. The reason is simple: My code needs to call lower-level libraries to do its job. If I can't access the code to those lower levels, I can't really know exactly what they do. Since my understanding of the lower levels is incomplete, there could be surprises in special cases that will make my code misbehave.

      We saw an extreme case of this some years back, with the Pentium floating-point bug. In this case, the bug went all the way down to the hardware, where incorrect values were returned for a small number of inputs. Without access to code and circuit diagrams, you can't discover such things by any method short of exhaustive testing, which could take centuries.

      Of course, making everything "open" is of somewhat theoretical value to most users. But it is of value. The "many eyes" argument explains why: By making the details visible, it is at least theoretically possible to do an exhaustive analysis; with a lot of people looking at the stuff, you greatly increase the chances that someone will spot problems or devise tests that expose problems.

      But if anything under your code is closed, you don't even have the theoretical possibility of discovering problems until they bite you. Since your code is dependent on those lower levels, you can't make any guarantees about your code's behavior.

      Security people have been saying something similar for years. If you want real security, you don't run anything unless you have the source. And you compiled it yourself, so you know that the binary corresponds to the source. And you compiled the compiler yourself (using a compiler from a different source), so you have confidence that the compiler doesn't contain backdoor code like Brian Kernigan described in his famous paper. And your hardware guys studied the processor's diagrams to look for possible gotchas (or designed-in bugs) in the machine language.

      Unless all this stuff is open and available, you are utterly at the mercy of the lower-level stuff that you're calling.

      In particular, since MS Windows isn't open for inspection, no software running on it can be reliable or secure. We have no way of knowing what tricks may be lurking down there in the OS or system libraries.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    13. Re:Open source is... by fitten · · Score: 2, Interesting

      His software is one of the temptations that we need to avoid if we're to obtain a fully free-software world.

      Assuming that is your goal. I, for one, do not have that as a goal. I'm happy with having both open and closed source and see no reason why I should *desire* to eliminate one or the other type of software. In fact, the idea is somewhat hypocritical.... "I want people to be free to develop software, but only under the type of license that I like."

  3. Not true by gregbains · · Score: 5, Insightful

    Considering still 90% of people, inc me, use a Windows environment, having your software work on it is not a bad idea, unless you want to cut 90% of your market off without even trying. Get people onto free open source software and they may try your OS. I wouldn't have tried Linux if I hadn't tried OSS such as Firefox/OO, yes it's silly but I didn't know about it before them.

    1. Re:Not true by rtb61 · · Score: 3, Insightful
      It would seem that this is what this article is really about, playing the word association game, windows and open source, asp.net and firefox/open office. Of course those bits of code are open source but it requires proprietary closed source code to write and run (you can only use it if you keep paying to do so).

      Microsoft is uncool and trying to associate it with that which is cool linux,open office,firefox and thunderbird etc. is pointless excersize in marketing. Getting the community to write code for it for free to promote it's products is history (microsoft loves the BSD licence, you do the work so it can sell it back to you)

      --
      Chaos - everything, everywhere, everywhen
    2. Re:Not true by Rei · · Score: 2, Insightful

      Exactly - cross platform is the way to go whenever possible. That means choosing cross platform libraries from the start, instead of ones that tie you to a particular platform. As a developer of Vulture's Eye/Claw, I can attest to the fact that we have many players who are Windows users, even though the project started out as unix-only. When our windows builder disappeared on us, we had more than a couple complaints about lagging windows builds of Vultures' :)

      --
      "99 dead duelists of Dios on the wall. 99 dead duelists of Dios! Take one's ring, pass it around..."
    3. Re:Not true by xstonedogx · · Score: 2, Insightful

      In my case I started using Linux because the only free apps I could find for Windows (years ago) were 100% crap pieces of shareware. Most of the free open source stuff was for Linux. I'm sure there were a lot of people who shared my experience and probably think that free software was a selling point for Linux until it become so readily available on Windows.

      I personally think your experience will be more common. Give people a little taste of geekdom and free stuff, and they might not be so afraid of trying something "weird and scary" like Linux.

    4. Re:Not true by peawee03 · · Score: 3, Funny

      In VI America, you use text editor. In Stallman Russia, text editor uses you!

      --
      I wish I could write clever and witty sigs.
    5. Re:Not true by RAMMS+EIN · · Score: 2, Interesting

      ``Considering still 90% of people, inc me, use a Windows environment, having your software work on it is not a bad idea, unless you want to cut 90% of your market off without even trying. Get people onto free open source software and they may try your OS. I wouldn't have tried Linux if I hadn't tried OSS such as Firefox/OO, yes it's silly but I didn't know about it before them.''

      I disagree with you on every count. Windows may have 90% of the desktop market, but the figures are different in other segments. Which operating system is prevalent depends on your audience.

      Secondly, your suggestion that it would be a bad idea to cut off 90% of your market. Most open source projects are primarily written to suit the authors' needs, and shared with the world on the off-chance that anyone else finds the software useful. Market share isn't even close to a primary goal.

      From the above, it's clear that I don't accept your conclusion that running on Windows is good. However, there's another reason why supporting Windows is a bad idea: Windows works differently from all other operating systems out there. You can support most Unix-like systems with little effort, but supporting Windows typically requires a lot of extra work. I would rather spend that work improving my software instead of supporting a deviant operating system.

      Finally, you try to convince me I should get people to use open source software so they will try my OS. You know what? I don't care if people try my OS. If my OS happens to be better and have all this great open source software, it's your loss if you don't use it. However, if you want to keep using your proprietary OS with proprietary software, that's fine with me. Just don't bug me with your problems and your worms. You bring those upon yourself.

      --
      Please correct me if I got my facts wrong.
  4. On the contrary by rwven · · Score: 4, Insightful

    I hold more respect for people willing to produce open source products for windows. Mainly because of the people this article is written about. I think there's some sort of irony to giving away something so open on top of a platform that stands very much for closed. Maybe that's just me though. I don't see a lot of people griping when their Closed-Source ATI linux driver keeps their video card running on their "open source" OS...

    1. Re:On the contrary by slavemowgli · · Score: 4, Insightful

      I don't see a lot of people griping when their Closed-Source ATI linux driver keeps their video card running on their "open source" OS...

      That's because in reality, there aren't actually many people like that. Sure, you'll find the occasional flameboy on Slashdot (although Slashdot's population in general is better than its reputation), and of course you'll also have zealots like Theo de Raadt (who, while probably a genius as far as the technical side of things is concerned, unfortunately still can be quite the flameboy), but for the most part, most developers *and* most users are pretty reasonable and will respect your choices and opinions even if they don't share them.

      Maybe it has to do with the fact that the more reasonable developers are busy coding instead of making a fuss all the time, but I also think that people generally aren't given as much credit as they deserve. Every village has village idiots, even the global village, but you shouldn't judge the entire population based on them, and neither should you assume that the majority of the village's inhabitants are village idiots - because they aren't.

      --
      quidquid latine dictum sit altum videtur.
    2. Re:On the contrary by The_Dougster · · Score: 4, Interesting
      I personally use almost 100% open source stuff on my windows machines, but thats because of the following:

      • I'm already a long time Linux user
      • For me, its a productivity boost to use familiar apps
      • I'm not trying to convince somebody else to use it.
      • I'd rather spend my extra money on other things.

      I routinely install Cygwin, OpenOffice, Dia, Python, Ghostscript, GIMP, and several other lesser apps on my own personal windows machines. Aside from games and CAD, I can get a pretty complete system using free software.

      It is true though that for some unknown reason, corporate IT people won't even consider an open source app most of the time. Why businesses continue to hire these wastrels is beyond me though. Companies will throw millions of dollars into crappy proprietary software, then cut jobs when the red ink starts appearing.

      --
      Clickety Click ...
    3. Re:On the contrary by radish · · Score: 3, Insightful

      It is true though that for some unknown reason, corporate IT people won't even consider an open source app most of the time. Why businesses continue to hire these wastrels is beyond me though. Companies will throw millions of dollars into crappy proprietary software, then cut jobs when the red ink starts appearing.
      I work for a major investment bank, building front and back office systems. Most of what I (and my team) do day to day is in Java - I use Eclipse as my IDE, build the code in Ant/Maven, and never go anywhere without my Apache Commons libraries. We have code generation tools which are built on Velocity, and everything's tested with JUnit. The finished stuff runs on Linux blades, often under JBoss or Tomcat - http duty is obviously also handled by Apache. When it comes to debugging web apps nothing beats Firefox & the HTTPHeaders extension.

      But apart from that you're right - we're terrified of Open Source :)

      --

      ---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"

    4. Re:On the contrary by paulkchen · · Score: 2, Interesting

      heck even the Mac can't hold its own against Visio (plus OSX requires the much more expensive Illustrator just to match CorelDraw...)

      Actually, have you looked at OmniGraffle? Some swear it's better than Visio. (I haven't used enough of either to any comparison.)

  5. Same for the opposite. by Anonymous Coward · · Score: 2, Insightful

    Why is this a surprise? Devlopers of closed-source software on Linux get a similar lack of respect (oracle excepted)

  6. Let me rephrase it a bit... by Memophage · · Score: 5, Insightful

    Unless an application is running on a system in which the processor design, motherboard schematics and BIOS firmware are 100% Open Source, it can not claim to be Open Source.

    Sound reasonable?

    1. Re:Let me rephrase it a bit... by scooviduvoctagon · · Score: 2, Insightful
      Unless an application is running on a system in which the processor design, motherboard schematics and BIOS firmware are 100% Open Source, it can not claim to be Open Source. Sound reasonable?

      It's called "argument of the beard"...

      Everyone has a different point at which they split the hairs.

    2. Re:Let me rephrase it a bit... by Sycraft-fu · · Score: 4, Insightful

      But since the source is open, can't you simply rewrite it to use another platform? I mean you are "locked in" to whatever platform you write complex code for. If you have a graphic app that relies on X and QT you are locked in to using a platform that has and supports those things. Windows, for example, won't work without adding components. However the idea is that since you have the source, you can rewrite the X/QT calls into Windows API calls and thus move it to another platform.

      Basically to me all this whining over openess of the whole thing sounds like just silly zealotry and isn't helpful.

    3. Re:Let me rephrase it a bit... by The_Dougster · · Score: 2, Interesting
      Unless an application is running on a system in which the processor design, motherboard schematics and BIOS firmware are 100% Open Source, it can not claim to be Open Source.

      I don't personally agree with this statement. This is one of those logical fallacies, maybe a Straw Man. Running on proprietary hardware has little or nothing to do with the fact that the software itself is Open Source.

      I always kind of felt that Stallman and his crew basically made the GNU userland so that when their expensive UNIX licenses expired on their proprietary mainframes, they could just replace the OS with their own and spend the money on more worthy projects, like buying better hardware.

      If you look at some of the checks that autoconf does, especially on really old versions of GNU software, its interesting to note that its checking for AT&T UNIX, DEC Ultrix, and all kinds of proprietary host systems. That software was made to install on "hostile" hosts at least until the Linux's became the platform of choice.

      --
      Clickety Click ...
    4. Re:Let me rephrase it a bit... by Rei · · Score: 2, Insightful

      The idea being presented is to use OpenGL instead of DirectX, PHP instead of ASP, etc - to use things that *don't* lock you in.

      --
      "99 dead duelists of Dios on the wall. 99 dead duelists of Dios! Take one's ring, pass it around..."
    5. Re:Let me rephrase it a bit... by Haeleth · · Score: 2, Informative

      Is it even legal to redistribute (L)GPL software that's linked against the stuff like MFC or DirectX?

      Probably.

      I would think that anyone porting a Linux app to Windows using closed Win32-specific libraries and distributing executables could (technically) be sued by the original author of the GPL software. No?

      Probably not.

      See section 3 of the GPL: "as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs."

    6. Re:Let me rephrase it a bit... by cortana · · Score: 2, Informative
      If the software is under the LGPL then you can link it to whatever you want. You only have to distribute any changes you make to the LGPL'd work.

      If it's under the GPL then things get interesting. From section 3 of the GPL:
      However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
      So you can link against a proprietary operating system's C library... most of the time: one of the ways that Microsoft makes Windows hostile to programmers of Free Software is by releasing newer versions of operating system components, like DirectX or the C library, only as separate downloads. Such components are not distributed as a part of the operating system and so do not fall under the section 3 exception cited above--someone distributing a Windows port of a work that used such components could be sued by the copyright holder of the work.

      I guess porters would be best to stick to whatever versions of MSVCRT and DirectX ship with the latest Windows version.
    7. Re:Let me rephrase it a bit... by killjoe · · Score: 4, Insightful

      "Basically to me all this whining over openess of the whole thing sounds like just silly zealotry and isn't helpful."

      Yes, it's widely understood that people you disagree with are by definition zealots. After all there can be no rational or reasonable reason not to accept your viewpoint, people must be disagreeing with you out of sheer zealotry and blind hatred of you and those things you love.

      --
      evil is as evil does
  7. Does it make sense? by grasshoppa · · Score: 4, Insightful

    No, of course not. These are zealots we're talking about. Logic rarely has anything to do with it.

    As to the argument: What are the overall goals of OSS? I suspect you'd get 10 different answers from 5 different people. But even if you define the goal as free and open software, you'd still want OSS projects on windows to create a transition medium. So the zealots would still be wrong.

    In short, ignore them and keep up the good work.

    --
    Mod me down with all of your hatred and your journey towards the dark side will be complete!
    1. Re:Does it make sense? by Krach42 · · Score: 2, Insightful

      It's not about it running only on Windows, it's about it running on ASP.NET, which is only available for Windows. They're distributing something that is free (as in speech) that can only be used on a proprietary non-free toolkit. (for the time, Mono is trying to fix this.)

      If there were Open Source alternatives for ASP.NET that were source level compatible, then there wouldn't be a problem. But forcing someone to purchase a license for windows, and ASP.NET is generally unacceptable from a free standpoint.

      It's like saying "You can say whatever you want, but in order to say it, you have to first write it down on this handy Gov-o-matic Scratchpad!"

      --

      I am unamerican, and proud of it!
  8. vocal minority by Enahs · · Score: 4, Insightful

    It's just a vocal minority. Chill. Most people aren't that particular.

    Seriously, I love the fact that people are passionate enough about something that they're willing to write Open/Free Software for Windows. After all, it's a VERY popular platform, and unlikely to go away any time soon. Firefox? Sure! OpenOffice.org? Yes, please! These two projects are helping keep things at the office I work at both safe and legal. ClamWin? Why not? I could go on, but I won't.

    A good analogy would be the days when kuro5hin.org was worth reading. You'd have material that was getting voted to sections and the front page all the time, but you'd only see comments like "stop posting this crap, we don't want to read it!"

    Who's "we"?

    --
    Stating on Slashdot that I like cheese since 1997.
  9. Idiotic by dshaw858 · · Score: 5, Insightful

    I'm usually very understanding of people defending linux, unix, bsd... and in fact, I'm an avid NetBSD user myself. However, people who don't support open source software on Microsoft platforms are really just hurting themselves. For example, how can one argue against the "low quality of open sourced software" to a Windows user, who cannot try any open source software themselves? Mozilla Firefox has helped immensely in this regard, showing how open source software can truly trump proprietary software.

    I'm all for open source operating systems, but let's be realistic here: zealots who don't respect open source efforts on Windows are not only being stubborn, but are hurting their treasured cause.

    - dshaw

    1. Re:Idiotic by bcrowell · · Score: 2, Insightful
      However, people who don't support open source software on Microsoft platforms are really just hurting themselves.
      I don't follow your logic. I use Linux. I've written some open-source apps that run on Linux. Most of them don't run on Windows. My life is fine. How am I hurting myself?

      For example, how can one argue against the "low quality of open sourced software" to a Windows user, who cannot try any open source software themselves
      There are a whole bunch of hidden assumptions here:

      1. You assume that the Windows user has a choice about whether to switch to OSS. Actually very few of them do, except in a few cases like web browsers. They may have lots of data tied up in proprietary file formats that can't be used in OSS. They may want to do things that you just can't do in OSS (like certain kinds of tax and financial stuff). They may use a particular closed-source app at work, and not have any choice about it.
      2. You assume they can't try OSS on a Knoppix disk.
      3. You assume that OSS apps are, in fact, high quality compared to closed-source ones. In reality, there are high-quality and low-quality OSS apps, and high-quality and low-quality closed-source apps. Maybe we shouldn't worry about the most effective way to convince people of something that isn't even true.
  10. The Definition of Open Source by ThinkComp · · Score: 3, Insightful

    Here's what I think of open source, at least from a technical perspective.

    From a legal perspective, there are 58 OSI-approved "open source" licenses last I checked, which together constitute at least 58 different definitions. There's no consensus on what it really means. Personally, I feel that if I can read the code, the code is open source. All the other factors are extraneous.

    However, one would think that in the spirit of openness, the open source community would welcome whatever contributions it gets, no matter how they're licensed. Sadly, that's rarely the case. I actually had someone threaten me with trademark infringement on the term "open source," when we released the Lampshade PHP framework under a dual license of our own. Of course, that person didn't own the trademark, becaues there is no trademark on the generic term, but whoever it was felt justified in threatening me anyway.

    If the open source community wants respect, it should be willing to treat people who contribute with respect, too. Scaring off contributors is not the way to go.

  11. why is this a problem? by p2sam · · Score: 2, Insightful

    Why is this a problem? and why should OSS developers on the Windows platform care about opinions of zealots?

  12. OSS should be everywhere!!! Hooray!!! by dslauson · · Score: 2, Interesting

    I know a lot of people are going to say that if you want to use a content management tool like Dot Net Nuke, why not just go Linux instead.

    That's sometimes easier said than done. I worked for a company that had a huge existing codebase in ASP and C#, and they had already bought the licenses for Windows server. The actual Microsoft Content Management Server was so insanely prohibitively expensive that it wasn't even an option. Dot Net Nuke saved the day.

    For the open source model to become what people want it to become, it needs to be not only embraced by the slashdot community of Linux nerds, but by everbody else, as well. Stuff like this is a good start.

  13. There are Open Source zealots by Darius+Jedburgh · · Score: 2, Insightful

    Is there a story here? Even if these people were a majority it doesn't do anything to stop anyone who wants to write open source for whatever platform they feel like. Even if these people want to declare that freely distributed Windows source is no longer to be called Open Source it still wouldn't stop Windows users distributing software and calling it something else. So try as I might, I can't find even the tiniest shadow of a story here.

  14. Cross Platform by KrackHouse · · Score: 4, Insightful

    If it's Windows only I could see how the anti-MS types would lose respect but if it's cross platform then intentionally preventing it from running on Windows would seem to be missing the point of openness.

    --
    What if Digg added local news and a Slashdot inspired comment karma system? ---
    http://houndwire.com
    1. Re:Cross Platform by nxtw · · Score: 3, Informative
      While it may be insufficent to run every ASP.NET application, Mono's ASP.NET implementation does exist and is functional. They claim to support all of ASP.NET 1.1 and have implemented many of the new features in ASP.NET 2.0. Of course, I haven't used every feature of ASP.NET 1.1, but overall Mono works fine with everything I have needed to do.

      The article is incorrect in saying "at this point in time DotNetNuke runs on ASP.NET, a services layer which is only available for the Windows platform - a situation which the Mono project is trying to address." ASP.NET is indeed available on other operating systems using Mono's implementation. In other words, the Mono project has already addressed this issue. While running ASP.NET applications with Apache and mod_mono isn't as easy to configure as, say, mod_php or any old CGI application, it's possible and not very difficult for anyone with experience configuring Apache and compiling Apache modules -- comparable to setting up FastCGI.

      Mono's XSP, a small, simple web server, works great for serving up ASP.NET applications.

      While .NET programs can be portable between Microsoft's .NET Runtime and Mono, just as software written in many languages can be portable between Windows and Linux, it's also possible to write software that only functions properly in one operating system or the other.

  15. A mute point by Penguinoflight · · Score: 3, Insightful

    The kernel that is being run doesn't really matter to a user when they consider one specific program. Usually what matters is the librarys being used. While supporting Windows is a honorable goal, using Win32 exclusive libraries creates problems. The windows implementations of Gaim, and wget work well because the foundational libraries project authors used to write the software have been ported to platforms that did not already support them. When you choose to write an open source program using proprietary libraries, porting to a more useful platform is hard, and the lack of forsight observed is just frusturating.

    I think the quoted in this post was trying to get false sympathy. By using someone elses foundation you are gaining advantages that allow your job to be done more easily, However when that foundation is closed source you do no favours to people who would improve or port your project. So unless you want to do ALL the non-foundational work yourself, find a good open source foundation, or write your own OS foundation.

    This is more of a practical argument than a philosphical one. I'm sure the /. crowd will not assess many pity points for whining.

    --
    "And we have seen and do testify that the Father sent the Son to be the Savior of the World"
    1 John 4:14
    1. Re:A mute point by istartedi · · Score: 4, Insightful

      gAIM works "OK". It's useable. Same deal with Ethereal. These apps would be a lot better if they used the native Windows APIs, or if they used a wrapper that was abstract enough to give them more the feel of a "real" Windows application. Not getting the Windows common dialog savebox when I want to save something is annoying. I understand why they did that--it was probably a lot easier to port. If I were looking to write GUI apps cross-platform though, I'd make sure the wrapper I was using came as close as possible to the look and feel of the native GUI on all the platforms I was trying to support. GTK ports are just crappy on Windows in too many ways to ever be the method I'd chose. It's been a while but I've heard wxWindows is pretty good in this regard. If so, more people should probably use it.

      --
      For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
  16. More sour grapes than truth here, I suspect by andyross · · Score: 4, Insightful
    The one thing missing from this article is the actual evidence of abuse from the broader Open Source community.

    I mean, sure, there are undeniably people who insist on running a 100% pure free software stack (I'm close to this end of the spectrum myself). And there are undeniably trolls out there who see the use of non-free software (more commonly MS software specifically) as evidence of moral corruption, idiocy, or malice. And these populations have some overlap.

    But so what? The reaction from the sane folks in the OSS community is going to be just, well, ignorance. As a full-time linux user, I will admit that I've never heard of "DotNetNuke" and have no plans on using it. It just doesn't enter my field of view, sorry.

    Ignoring projects isn't the same thing as "disrespect", and I suspect the author has confused the two.

  17. Port Up or Shut Up by gbulmash · · Score: 4, Insightful
    Personally, I'm a big fan of platform-independent open source. I run XP at home and built myself a WAMPP development platform, using Windows XP, Apache 2, PHP, Perl, and MySQL. It makes my life easier, because I can use all my comfort-zone editors (text, bitmap, vector) and integrate the results into the dev site on the fly.

    Would I care if a project that was really useful to me on Windows wasn't viable on Linux? Yes and no. I think that platform independence is a HUGE plus in the FOSS world. It definitely earns you bonus points. It increases the level of freedom the users of that project have. BUT, users of that project are also free to port it to other platforms. I wouldn't be able to run my WAMPP environment if people hadn't ported the AMPP portion to Windows.

    Using more proprietary foundations like .NET do limit the usefulness of an OSS project, but only until people get interested in developing ports. If nothing else, you can build a forked project that uses the best logic and functions that aren't platform dependent and merges them with a more platform independent underpinning.

    If you're developing OSS for .NET, kudos on being open source, but you do miss the bonus points for being platform independent and don't whine about not getting the cred platform-independent projects of the same nature do. If you're an OSS user who sees this great project built on a proprietary stack and are pissed because it's not available for your platform, "port up or shut up".

    - Greg

  18. Talk to the folk at Wine by Anonymous Coward · · Score: 2, Insightful
    The Wine get the same sort of flack, as do those working on ReactOS, which is actually a complete replacement for Windows.

    It's just platform chauvinism, plain and simple. It stems from a very simplistic world view, a sort of If you aren't 100% against them, you must be against us.

    The irony is, it's often those who whine and complain the loudest about Micro$oft that do the least to support actual Open Source development.

    Ooops, that was almost well thought out and reasoned... I should have just said: "You're new here, aren't you?"

  19. Re:OpenFirmware? by TheRaven64 · · Score: 2, Insightful

    The question is not does it run on an open platform, but can it. Linux and NetBSD, for example, will boot happily on a MIPS system running on an FPGA - and the core can be downloaded from Open Cores under a Free license. That's probably a bit more Free than I feel the need to be, but I like the option being there. Software written using Windows APIs, however, will not run on anything other than Windows unless care has been made to port it to winelib or similar.

    --
    I am TheRaven on Soylent News
  20. Predefined Notions by caperry · · Score: 2, Informative

    From my experience, there are a lot of people who make "free" software in windows and it's frowned upon becuase "it's a plot to install a virus on my system". Then there is the folks who feel that writing software for windows should earn them money no matter what. On the flip side, you can get a lot of flack for making non-free software on Linux or you can been seen as evil for charging for services that "should be free". Long and short of it: you can't please everyone. If it makes you happy and people are using it, just keep doing what you are doing. There is a vocal minority on either side of the fence to flame you :)

    --
    -Carl "No, we already thought of that one. 'Why?' '42' - It doesn't fit." -Hitchhiker'
  21. Lets be serious here... by danielk1982 · · Score: 3, Funny

    ...reminds me of that Star Trek Voyager episode a friend of mine watched and told me about because I'd never watch that. The Voyager was chasing down...

    We're all geeks here, no need to deny it.

  22. Re:I use a lot of OSS on doze by kuzb · · Score: 4, Insightful

    1) There is no operating system called "doze" - You might benefit from the link in my tagline.
    2) You can't defeat something unless you have something better to replace it with. Linux is not better from an end-user standpoint.
    3) People who port their software are NOT part of the problem. They are part of the solution. Exposure to what F/OSS is capable of will make it more likely that someone will use it in the future.
    4) People like you are part of the problem. You would limit choice based on platform.

    --
    BeauHD. Worst editor since kdawson.
  23. How open is C#? by Foofoobar · · Score: 2, Informative

    This is one reason why I don't use C#. People who use C# develop for Windows and Windows only (MONO be damned). C# is owned by Microsoft; true there is an open implementation but Microsoft has refused to support it, refused to allow them to their .NET conferences or anything else... which says they will NEVER support an open implementation of C#.

    It's like building an 'open source' house with wood that's owned by Bill Gates. What is going to happen to your house when Bill decides to start breeding termites on location? Bye bye house. And bye bye open source C# implementation.

    --
    This is my sig. There are many like it but this one is mine.
    1. Re:How open is C#? by Foofoobar · · Score: 2, Interesting

      Since when have standards stood in Microsoft's way. Name one standard that they comply with that they don't own? Go ahead... name one. I know they haven't complied with any of the W3C standards forever and instead attempt to implement their own standards.

      Standards? They don't need no steenking standards!

      --
      This is my sig. There are many like it but this one is mine.
  24. Why, no, it doesn't. by istartedi · · Score: 2, Insightful

    The stack argument never made any sense. Over the years I've seen too many projects that claim to have Windows versions, and then when you download the source they don't include any kind of Windows build files (NMAKEs, project files, etc) or they say it has source for Windows when it really just has source for Cygwin, which isn't native Windows. Worse than that, I have even seen projects that just give you headers and libs with the Windows "developer" distribution. Or, if you offer to provide better Windows development files, they say they don't want them. This will often happen with project files for MSVC. Yes, I know they are subject to the format whims of MS's next release, but for cryin' out loud the format doesn't change that often, and there is nothing that says you can't provide NMAKEs and other, more stable build scripts too. Regardles, those MS files are part of the preferred method for modifying the program and I have even seen projects where the developers obviously used MSVC but wouldn't tar up those files. That's just cruel, because then I have to go through the hassle of re-creating them.

    Anyway, the stack argument is being invalidated every day by apps like Firefox and Open Office. It might not have taken so long if so many people hadn't been snobbish. People are more likely to replace their kernel when they can keep familiar apps then they are to replace familiar apps for the sake of a kernel.

    --
    For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
    1. Re:Why, no, it doesn't. by spitzak · · Score: 2, Informative

      I cannot accept MSVC project files for the simple reason that I want to be able to add, delete, and rename the source files in my software. If I distributed a MSVC file I have to remember to update that file. Better to not distribute anything and force the MSVC users to copy & paste the correct list from the Makefile each time.

  25. I was a windows open source developer by Cannedbread · · Score: 2, Interesting
    I have been doing open source programming in VB6 for 4 years.

    I had the utmost respect for OSS but no knowledge of linux or any of its programming languages, so i felt like opening up my Vb6 apps would be my small contribution to the world. i got no respect from any other programmers and i couldnt figure out why. they told me that as long as my projects were on a microsoft platform, in a proprietary language, that they could not fundimentally be open. i would forever be microsofts bitch.

    Then microsoft killed Vb6, and i understood what they meant.

    I am now writing this from a laptop i built especially for ubuntu and i need to stop looking at slashdot because my C homework is due in 3 hours.

  26. Beyond the FUD by Draconix · · Score: 5, Informative

    (Meh, sorry to those I modded up, but I need to say this.) The article is (possibly intentionally) vague on what they mean by 'Windows OSS projects.' If you read into what DotNetNuke actually is, you'll discover that it is a Windows-only OSS project built on the .NET framework, and that they appear to be partly sponsored by Microsoft itself. The article is referring to Windows-only OSS projects, not OSS projects with Windows versions.

    Though I imagine projects like VLC, Freeciv, and Gaim occasionally have someone whining about their supporting windows, that's not what this is talking about, and frankly, where DotNetNuke is concerned, I'm with the 'zealots', despite having nothing against proprietary software. OSS has built up a strong reputation for being cross-platform, so an OSS project that's for Windows-only and is dependant on Microsoft technology is understandably going be frowned upon by OSS purists. Windows-only OSS developers are, arguably, not helping the OSS communities much, and they are especially detrimental to the spread of Open-Source and Open-Source-based operating systems. It's not showing Windows users that they have something nifty that they could still have if they decided to try linux or get a Mac, it's just further miring people in the Windows platform.

    Now, are these people against DotNetNuke still looking so much like zealots, or are they perhaps starting to look more like people against Microsoft who see this as yet another boost to Microsoft's power?

    --
    By reading this you acknowledge that you have read it.
    1. Re:Beyond the FUD by Anonymous Coward · · Score: 2, Insightful

      Open source Windows software that is cross platform has a tendency to be really shitty from a Windows user's point of view.

      Stuff like Ethereal and Gimp can get a job done, but leave you wanting to avoid open source if possible. GNU software tends to be the worst offender, words cannot describe getting GPG to work on Windows.

      Windows users expect a Windows interface, software that places emphasis on a good UI and that can do everything that 'normal' Windows software can do (for example the file open dialog being able to see the network).

      I understand your points about cross platform OSS being both more useful to the community, and not alienating it, but due to the way it looks, Windows OSS that was not designed with Windows in mind makes people from the commercial software world think free software is free because it's too unprofessional to charge for, rather than free as in speech. That last line is not a troll - going to a university that did not explain the OSS philosophy in their courses, the feeling was that the university ran free software because it was too cheap to purchase proper software.

    2. Re:Beyond the FUD by DraconPern · · Score: 2, Informative

      Not only do those people look like zealots, I believe you are one of them too. Either you are new here or you are a zealot. Because...

      You can't run .NET on linux
      You can't run ASP.NET on linux
      There's not an Integrated Development Environment (IDE) for .NET on linux
      There's no commercial support for .NET on linux

      So I am betting you want to bash Novell too because they support .NET?

  27. There are Good F/OSS Windows Applications! by Noksagt · · Score: 2, Insightful

    I am a strong believer in F/OSS. Not only do I run it, but I contribute code and money (I also submit bug reports, patches, contribute answers to forums, and am an advocate of F/OSS to my peers). In short, I drink the Kool-Aid. I use only Linux and FreeBSD on machines I own (and I bought the machine on my desk at work, so I can use it there). I am a zealot. I think that an all (or mostly) F/OSS stack is something to strive for & that a lot of F/OSS software does work better on a free OS (usually because that is what the developers write it for & where it gets the most complete and knowledgable testing).

    That being said, I do still sometimes have to use Windows & I am happy to have F/OSS on that platform. I patch my own code to work around bugs that only impact Windows users & I have financially supported projects on that platform. I have even given money to good F/OSS software which is only on that platform. I am certainly not alone. Just look at the top projects on sourceforge. Most run on Windows. Some run only on Windows.

    So...some of the best Windows-only/Windows-mostly F/OSS:
    Filezilla--great (S)FTP client/server. Hopefully a *nix port soon.
    7-zip--excellent compression software. p7zip is there for the rest of us, but updates take a while to reach us.
    PuTTYFor your ssh/scp/sftp needs.

    I've given money to these projects & carry them around on a USB key (along with Thunderbird, Firefox, and vim). Cygwin is another handy thing to have if you have to be on win32 for very long.

  28. Re:Let me rephrase it a bit... more... by pedantic+bore · · Score: 2, Funny
    I can buy an FPGA

    Good heavens, don't do that!

    There are only a few vendors who make FPGAs with enough gates to run a full MIPS core (you'll need more than the mimimum to boot an interesting operating system). And then you're locked in!

    Unless the FPGA design is open source, you're a complete hypocrite, worse than any Windows user, because you preach open source and are living in sin.

    --
    Am I part of the core demographic for Swedish Fish?
  29. Re:I use a lot of OSS on doze by kuzb · · Score: 4, Insightful

    1) It wasn't right then, it's not right now. If you really love Linux/Unix/Etc, then at least try to support it in a way that encourages new users. This brand of advocacy that you endorse just makes it so people think you're a raving lunatic with no objective opinion. You know, a zealot.

    2) Sure it can. Right now, OS X is better than Linux is, and it appears to have coexisted just fine in a Windows dominated world.

    3) Most people don't know anything about OSS, and are unlikely to move to Linux just to experience it. Face it, Linux users in general are the minority, and if you want to see that userbase increase, we need to slowly get these people used to the idea that OSS is not something to fear.

    [..]we shouldn't be supporting windows by making it more usable.

    4) Actually, as per your original post (see above line), you flat out said we shouldn't port OSS to Windows. That's limiting choice based on platform. Isn't part of the whole FOSS argument that you're giving the user choice and freedom?

    5) You take things way too seriously. Relax.

    --
    BeauHD. Worst editor since kdawson.
  30. I'm Guessing You Don't Get It. by Bob9113 · · Score: 3, Insightful

    From your site:

    In order to download DotNetNuke® Projects, you must register on the site.

    I'm thinking you're getting no respect in the Open Source community because you don't get it. The community is not about how you license your software (you don't even have to be a developer to be a member of the OS community). It's about the spirit of community and openness from which springs the compulsion to use a particular license for your software.

    The above statement from your site and your publication of an MS-only piece of software makes me assume that you accept Open Source because that's the way the world is and it is how one develops a resume these days, not because you like it. Is that necessarily true of you? I can't say for sure, but first impressions mean a lot, even your post somehow hits me as a little off - something about the whining or faulting others because you are not being accepted, like you need someone to bless your OS-ness, instead of just knowing you have it. I can't say exactly what all it is, but I'm guessing it's the same thing that has made others uneasy (perhaps some other poster will be more insightful in identifying the real causes).

    Moreover, changing that one line on your site isn't going to do it. Faking it won't work - if you don't understand, people will see it in a million ways. OS developers will see it and continue to give you no cred. If I'm wrong, or if you're willing to learn more and understand why Open Source is a good thing, more power to you. But until you do, you're probably in for a fair amount of continued disenfranchisement.

  31. The elephant in the room - Portability by toby · · Score: 3, Informative
    None of the high rated comments mention the issue of portability (and they use the word zealot all too freely...reminiscent of certain other abuses of language lately, but nm!) Non-portable software is arguably a dead-end too, if it can't be ported to a free system when the time comes. A closed O/S, we have seen repeatedly, means obsolescence; it means the plug can be pulled at whim of the vendor.

    Since XP, technological measures have been in place (DeActivation) that can separate you from your applications (not to mention your data) at any time, through wilful act of the vendor, or fault in the system, and this is regularly experienced by customers of M$ and Adobe.

    It seems obvious that portability is part of the spirit of freedom as expressed in free and open source software. If your code can't migrate from Windows - then it's going to be taken from you and your users sooner or later.

    --
    you had me at #!
  32. You don't need respect to develop on windows by TheNarrator · · Score: 4, Insightful

    Just go look at the stats on sourceforge, software that runs on windows gets 10x the downloads that linux software does. A great example is Postgresql which was ignored by many until it got a windows port. Who needs respect when you've got popularity?

  33. Quality of products on Windows is good by The+OPTiCIAN · · Score: 2, Interesting

    I've found a couple of situations where free software has a better quality implementation on Windows than linux. I came to mozilla for Windows from a linux background. Yet there are several niggly ways in which mozilla/windows is better than mozilla/linux. One of them is the fact that you can't use ctrl+arrow in the address bar to select by word in linux.

    Eclipse is far more responsive and cleaner-looking on Windows than linux.

    I've used postgresql on linux for years and years. The other day I installed postgresql for Windows and was quite impressed by the implementation. It works like a Windows app but doesn't compromise performance or power.

    --


    Believe with me, my saplings.
  34. Open source driver? by cdrguru · · Score: 2, Interesting

    The problem is that a significant cost in producing a hardware product - any hardware product - is the software engineering. If a Chinese company could "borrow" the driver for an ATI product, they would be one step closer to producing an ATI replacement product. I am sure they already either are licensing or "borrowing" the hardware bits.

    So, ATI knows this. All opening up the driver would do is (a) give people more of an opportunity to screw things up and (b) give a helping hand to people that want to drive them from the marketplace.

    Most video drivers these days are pretty large - larger than your average open source project - and unlikley to respond well to being tweaked by people unfamiliar with the architecture. Surely you don't think ATI's drivers are better self-documenting and structured than most open source projects, do you?

  35. My perspective by einhverfr · · Score: 2, Interesting

    I use and recommend a lot of Free/Open Source software on Windows. I just don't use Windows for my own purposes, so most of these solutions tend to be cross-platform.

    I don't use Windows because I don't like the terms of the EULA. But I don't make that decision for my customers. In these cases, complimenting Windows with Free/Open Source software (like SpamBayes, Cygwin, and the like) makes a lot of sense. So while I make my own software use decisions around the stack argument, I want my customers to have access to Free Software regardless of what operating system they currently use.

    For the most part, I don't recommend a lot of Windows-only FOSS. Most of the projects I recommend are somewhat cross-platform. So a Free/Open Source Windows-only apps aren't going to get much of my notice. However, there are exceptions and I think it is important to cultivate a Windows-based open source community (if nothing else it will warm people up to other open source projects).

    --

    LedgerSMB: Open source Accounting/ERP
  36. Re:The open source crowd won't matter next year by smash · · Score: 2, Interesting
    M*soft will be rolling out Vista next year and 64 bit, yada yada. I'll buy it, you'll buy it, your company will buy it. Almost every new pc sold will have it installed. If you want to help the open source movement, you must develop for windows. Linux is not not a consumer os (yet). Right now it's for people who like spending 34 hours downloading, burning, compiling, coding, burning, downloading again (new distro this week),

    Still living in the 90s?

    That is simply no longer the case.

    Install ubuntu from CD, download nvidia driver (as you would need to with windows anyway), boom.

    Installed.

    Been using it for 6 months without even having a compiler installed.

    I will *not* buy Vista 64 bit (and not because I"m cheap/broke/live in mum's basement/whatever - I'm 28, living OUT of home and earning a decent wage with 90% disposable income).

    There's simply no need for it.

    Sure, there's a limited games selection, but there hasn't been a single game in the last 12 months thats really grabbed my attention in any case (and yes, I've been keeping an eye out/playing them from time to time on Windows) - except for GT4, which i play on PS2.

    I love how many people consider themselves an authority on the whole Windows v Linux debate, when they clearly have no experience with Linux since the mid-late 1990s...

    smash.

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  37. Kernel and Shell by Spit · · Score: 2, Insightful

    The kernel and shell are the easiest parts of a system to swap, considering the obvious similarities between modern GUI shells.

    The applications are the hardest part to replace. Change apps until they are all free, then it's trivial to move them to a free kernel and shell.

    The true beauty of free software is its cross platform and hardware independant nature.

    --
    POKE 36879,8
  38. He misses the real issue by jdhutchins · · Score: 2, Insightful

    I think that the author of the article misses the real point. Most people writing OSS run Linux. That's a fact. People writing OSS are much more likely to write for a platform they use frequently, Linux. If you are writing an OSS app for Windows, most of the rest of the OSS community, running Linux, sees little point because they can't use your software.

    Few care about the nit-picky definition of "not being open because the whole platform isn't open" The author of the article misrepresents that for the general lack of interest most of us have in Windows-only software- we simply can't use it, and are therefore unable to see why we should care. That being said, many larger OSS projects maintain windows ports (firefox, gaim, etc), but they were Linux programs first for the most part.

  39. Windows for Linux users by DavidNWelton · · Score: 4, Informative

    I suppose this would be as good a place as any to mention the wiki I started, Windows for Linux Users, which attempts to gather up some software that is useful for long-time Linux users who are for some reason constrained to use Windows. I know I had a terrible time getting the environment to a point where I didn't want to smash the computer because focus wasn't following mouse and a bunch of other little annoyances.

  40. nobody minds if it *also* runs on windows by ammoQ · · Score: 2, Insightful

    but open source software that runs only on Windows encourages the use of Windows
    and discourages the use of free operating systems. On the way to a fully free
    software stack, it's basically a dead end. You can't expect the members
    of the FOSS community to endorse that.

  41. Which part of 'Open Source' don't you understand? by Otis_INF · · Score: 2, Interesting

    Open Source, two words. One means 'Open', e.g. the opposite of 'Closed' and the other one means sourcecode, together they mean: a non-closed form of sourcecode.

    Gee, since WHEN is that tied to CROSS PLATFORM crap? Because in this particular situation, it's very handy to use that cross-platform nonsense to hit back at this DNN OSS developer?

    It's precisely the whining YOU put forward in your posting what made him write the article.

    --
    Never underestimate the relief of true separation of Religion and State.
  42. Supporting Windows is a waste of effort by RAMMS+EIN · · Score: 2, Insightful

    I won't deny anyone the right to spend their time the way they want to, but I can see why people writing OSS for Windows don't earn as much respect as those writing for a free *nix.

    The reason is that Windows is incompatible with existing OS API standards. This makes it difficult to port apps to or from Windows, whereas getting an app that uses mostly POSIX APIs to work on any other operating system requires a lot less effort.

    Thus, if you want to support multiple platforms, your choices are essentially to spend the extra effort and support Windows, or to support only the other operating systems and spend the effort actually developing your app. As I said in the beginning, you're free to chose as you wish, but I'd choose the latter option any day.

    --
    Please correct me if I got my facts wrong.
  43. It's because of Windows culture by ajs318 · · Score: 2, Interesting

    Windows, by its very way of being, has instilled in people a certain culture that is at odds with the Open Source movement.

    Windows brings the idea that the act of writing software is a service that must be paid for, by charging money for the privilege of installing said software. The Open Source movement believes that the act of writing software should not chargeable. After all, the programmer who wrote it was going to write it anyway irrespective whether or not you paid for it; so refusing to hand it over without payment is just playing dog-in-the-manger -- and contravening Freedom Two in the process. But Windows goes on further and directly contravenes Freedoms One and Three {both of which are contingent upon the user having access to the source code, which is not supplied with the software} and even goes some way towards infringing upon Freedom Zero by means of the -- mercifully unenforcible -- End User Licence Agreement.

    If something costs money, goes the thinking, then it can be stolen. And so there has appeared a group of people who have obtained Windows and other software without paying for it. Microsoft calls these people "pirates" and "thieves"; in reality they have stolen nothing but are merely attempting unilaterally to assert Freedoms Zero and Two. This fuels an attitude amongst these people that they are "sticking it to The Man" somehow, when in fact they are just as dependent upon The Man as any paying customer. In fact, by far the vast majority of software used in the world consists of unpaid-for copies of Microsoft Windows and applications running upon it.

    Back in The Days, when computer users had no choice but to be knowledgeable in the field, the Four Freedoms could to a large extent be taken for granted. Computer users were effectively a society who looked after their own. Everyone benefitted from everyone else's work, and collaboration was the only way to advance. The community shared the bond that comes from a survival situation. The incompatibilities between different kinds of computer meant that the only feasible way to share software was in the form of source code {and often, different implementations of the "same" programming language meant that even this needed significant alteration}.

    Today, it is possible even for a person who knows nothing about the inner workings of a computer to use one. This situation has led to a large number of people who are ignorant of the existence of this thing called "source code", believing it to be of importance only to boffins in laboratories somewhere. This attitude is deplorable: it is like someone who lives in a city not caring about which plants are edible, or how to build a bivouac, dismissing such knowledge as of importance only to "survival nutters" and the Military. Even if you do not know these things yourself, it is important at least to have friends who know these things -- it might save your life one day.

    Ignorance of the benefits of the Four Freedoms is exactly what fuels the acceptance of the way Windows, and other closed-source software, trample on them. Windows users typically have been taught not to care about Open Source software. Either they expect to have to pay for software and not get the source code, or they expect to be able to get it without paying {like they are doing something big and clever} and do not care about the source code. Windows users who go on to become developers typically perpetuate the Cycle of Abuse by releasing their software closed-source. {cf. children brought up in violent families who go on to inflict violence upon their own children}. In some cases, the abuse of users' Four Freedoms is malicious but in many cases, it may be attributed to ignorance caused by developers having no better example.

    The kind of computer user who is savvy enough to understand the importance of the Four Freedoms in general, and source code in particular, typ

    --
    Je fume. Tu fumes. Nous fûmes!
  44. Re:Free or not... by inaequitas · · Score: 3, Interesting

    Well there's been some interchanging of "free" and "open" throughout the comment sections which I'm not sure is warranted since there's two different philosophies at work here in terms of software. But for all points and purposes I suppose I'll try and tackle both.

    Yes, GNU isn't interested in developing things which are not [or rather, cannot be] free from the ground up. That's why they don't endorse OpenOffice 2.0 or the Sun JDK [the former due to great use of the latter]. Sure, there was compromise at the beginning, what with having to develop GCC on some other compiler that wasn't free [if memory serves me right from "Revolution OS"], but the groundwork has been laid out and so there's nothing stopping the 'proper' development of free software now.

    But the perceived issue here is in regards to the politics of open source and the lack of understanding of those mentalities when it comes to Windows users. Indeed, it's hard to change that mindset overnight; as a University student [and a CS major to add to that] I'm faced with enough "pay me for my work" peers that cannot even begin to understand the point of doing something for free [they believe no one will donate a penny given the choice]. There's also the ones that use Linux due to financial constraints but have no other affinity to the OS or the mentality.

    I consider that neither of these groups can truly understand the nature of free and/or open source. While the world is happy enough with just one Richard Stallman, it cannot be denied that Linux is a movement that has more than just technological implications. Sure, it isn't communist [as it has been sometimes thrown around] but maybe some "technological marxism" [economically speaking] can be traced to it, and surely it bothers a lot of people.

    Okay, kinda went off-topic there, apologies.

    Windows OSS isn't a movement per-se. It's sprung as a by-product of the Linux/BSD OSS movements and lacks the drive or 'notoriety' characteristic to these. There's rarely any understanding of the core mentalities in most [read: average] Windows users and they'll look at anything free with incredulity at best and suspicion at worst.

    The non-Windows community doesn't disregard WinOSS based solely on the non-free stack upon which it tries to function: yes, I think it is generally a matter of portability rather than anything else. Most OSS devs work in free environments because it feels more 'at home' to do so; and non-portable code does not interest them since they cannot benefit it.

    The stack principle is valid in terms of free software; the mentioning of it here, when it comes to Open software, seems an indication of the lack of depth given to clearly understanding the difference between the two issues... wonder why you'd get shot down sometimes :)

    Cheers!