Slashdot Mirror


Windows Loses Ground With Developers

An anonymous reader notes that InfoWorld is covering a survey of North American developers that claims that Linux is gaining share as the number of developers targeting Windows fell 11 percent over the last year. Evans Data has been conducting these surveys of client, server, and Web developers since 1998. Evans Data says that the arrival of Windows Vista likely only kept the numbers from being even worse. The big gainer wasn't developing for a Web platform, but rather for Linux and "nontraditional client devices." Windows is still dominant, with 65% of developers writing code for this platform. Linux stands at almost 12%, up from 8% a year earlier. The article says that Evans Data collected information on Mac and Unix development but did not include them in this year's report.

77 of 431 comments (clear)

  1. Ob.. by grub · · Score: 5, Funny


    ObSweatTardLink: Developer Music Video

    Awesome.

    --
    Trolling is a art,
    1. Re:Ob.. by Captain+Splendid · · Score: 3, Funny

      Beat me to it. I was going to say the headline should say:

      Windows Loses Ground With Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers, Developers,Developers...developers...developers...

      DEVELOPERS!

      --
      Linux, you magnificent bastard, I read the fucking manual!
    2. Re:Ob.. by misleb · · Score: 2, Funny

      Actually, it was only an 11% drop, so it would just be the "Developers developers developers developers" that they lost ground with. Don't exaggerate the data!

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    3. Re:Ob.. by PopeRatzo · · Score: 4, Interesting

      The migration of developers away from personal computers toward "nontraditional client devices" worries me a bit. The best thing about the rise of the PC was that it gave people access to a machine that could be configured to do a lot of different things, including "learn about making your own applications". I wonder whether all the "embedded devices" will also provide a coming generation with a platform from which to recreate their world the way PCs did for us.

      I love the Mac interface, but the thing I always loved about Windows was that it forced me to look more closely at what was going on than I may have wanted to. And that exploration of the nuts and bolts of an overcomplicated desktop OS gave me insights that I may never have gained had I stuck with the more opaque Mac OS. Of course, for those who want that experience today, Linux has it in spades. But as much as I loathe Vista and the company that has trumpeted this abomination on us, I'm glad that I had to learn about a "registry" and I'm glad I had to learn about shared libraries and memory management.

      As much as I'm sure that the devices that will contain embedded processors will provide us with utility and convenience, pleasure and all varieties of entertainment, I hope that the idea of an all-purpose, configurable, expandable box with a keyboard and operating system doesn't go away any time soon. And I hope that developers continue to create tools for us to use on those boxes.

      --
      You are welcome on my lawn.
    4. Re:Ob.. by jgrahn · · Score: 3, Insightful

      The migration of developers away from personal computers toward "nontraditional client devices" worries me a bit. The best thing about the rise of the PC was that it gave people access to a machine that could be configured to do a lot of different things, including "learn about making your own applications". I wonder whether all the "embedded devices" will also provide a coming generation with a platform from which to recreate their world the way PCs did for us.

      I see what you mean, and I agree. A computer should be programmable by its users.

      One correction though: it wasn't the PC that turned kids into programmers. It was (a) Unix systems at universities and (b) the cheap home computers of the 1980s, with a BASIC interpreter and a demo scene, like the Commodore 64.

    5. Re:Ob.. by BasilBrush · · Score: 2, Interesting

      I love the Mac interface, but the thing I always loved about Windows was that it forced me to look more closely at what was going on than I may have wanted to. And that exploration of the nuts and bolts of an overcomplicated desktop OS gave me insights that I may never have gained had I stuck with the more opaque Mac OS. Of course, for those who want that experience today, Linux has it in spades. But as much as I loathe Vista and the company that has trumpeted this abomination on us, I'm glad that I had to learn about a "registry" and I'm glad I had to learn about shared libraries and memory management.

      You're glad you have a lemon for a car because it's forced you to learn car mechanics?

    6. Re:Ob.. by Air-conditioned+cowh · · Score: 2, Funny

      Developers, Developers, Developers, Developers, .... Developer.... Where's everyone gone????

    7. Re:Ob.. by gig · · Score: 2, Interesting

      > And that exploration of the nuts and bolts of an overcomplicated [Windows] desktop OS gave me insights that I may never have gained had I stuck with the more opaque Mac OS

      The overcomplicated state of Windows has done more to turn people off computers than it has to help them. There are only a paltry 500 million personal computers in the world, that is abject failure on the part of the 30 year old personal computer industry. There are 4x as many phones right now and everyone will tell you phones suck. Microsoft is to blame for a lot of the PC's unpopularity. People fucking HATE them. Just stop making excuses for Microsoft. The PC is fucked right now and the Web moving to phones can't happen fast enough.

      Also your remark is bigoted: 1) coding is just one way to use a computer, and it is only a solution to a minority of tasks, and 2) you obviously know nothing about Mac OS.

      > The best thing about the rise of the PC was that it gave people access to a machine that could be configured to do a lot of different things,
      > including "learn about making your own applications".

      Here is how you make your own application on the Mac:

      - launch Script Editor (the Mac shell since System 7 in like 1992)
      - write AppleScript code
      - click "Compile" (it is instant)
      - choose File > Save As
      - specify "Application"
      - give your new application a name
      - click OK
      - in Finder, locate your new application and launch it
      - enjoy

      I'm a graphic artist, I went to art school not CS, didn't even use a computer until I was 21, and yet I make 50+ Mac apps per year that do the work of an entire other graphic artist, using nothing but the built-in tools in Mac OS. Sometimes an app only takes a half hour to develop and it saves me days and days of laborious, repetitive work. Some apps take as much as a week to develop, but they do a week of work in one hour the first time you use them, then every other time it is just gravy.

      With AppleScript development, the applications on your system become libraries for your own apps. So even though you only wrote 20 lines of code and it only took a half hour, the app you create write JPEG's with Photoshop, writes MPEG-4 movies with QuickTime, creates folders and moves files around using Finder, converts EPS to SVG using Illustrator, runs Unix shell scripts using the command line, and so on, all in the same little rapidly-developed AppleScript app, so you get out very high quality products with very little work.

      Maybe that is just the Mac being opaque to you, but I can tell you I go to Photoshop conferences and I sincerely want to know what Photoshop-Windows users are using to automate Photoshop since they don't have AppleScript. For example, converting 500 camera photos into 500 Web photos 1/8th of the size with 1/8th inch border and logo watermark is really time-consuming and error-prone if you try to do it manually, you want to write some code that describes the above task and have Photoshop do the task once on the first photo, then once on the second photo, etc. What I have found is that Photoshop-Windows users, when faced with a task like that, go out and buy yet another photo editing app that specializes in converting batches of photos and they take whatever options are in there and make the best of it. They don't get the exact watermark they wanted, necessarily, and the files they create are not as high-quality as Photoshop creates, and they also spend hundreds of dollars on these useless apps.

      It is Windows that is opaque, in my opinion. Especially if you're not an MSDN member C software developer. Windows users are not supposed to develop their own custom software, they're supposed to buy software from Microsoft's developers developers developers.

      I mean, Tim Berners-Lee is a physicist who had an idea for a software app and wrote it himself on a NeXT machine and it became Microsoft's worst nightmare. Those same tools have been on the Mac since 1999, how opaque is that?

      > access to a machine that

    8. Re:Ob.. by bdjacobson · · Score: 2, Interesting

      The migration of developers away from personal computers toward "nontraditional client devices" worries me a bit. The best thing about the rise of the PC was that it gave people access to a machine that could be configured to do a lot of different things, including "learn about making your own applications". I wonder whether all the "embedded devices" will also provide a coming generation with a platform from which to recreate their world the way PCs did for us.

      I see what you mean, and I agree.
      A computer should be programmable by its users.


      One correction though: it wasn't the PC that turned kids into programmers.
      It was (a) Unix systems at universities and
      (b) the cheap home computers of the 1980s,
      with a BASIC interpreter and a demo scene, like the Commodore 64.

      I believe the idea is that by centralizing your computer, grandma doesn't have to worry about antivirus or installing updates. I know that sure would be a help for mine; she doesn't understand why she has to install updates monthly; and I'm certainly not going to be her [Linux] support speed-dial.
    9. Re:Ob.. by Fred_A · · Score: 2, Informative

      It is Windows that is opaque, in my opinion. Especially if you're not an MSDN member C software developer. Windows users are not supposed to develop their own custom software, they're supposed to buy software from Microsoft's developers developers developers.
      Quite so. Back when I *was* a developer (on Tandem minis, semi-big iron, definitely not user friendly systems), I quit Windows because the first Linux distro had become available and I couldn't really understand how Windows worked anyway since it didn't make any kind of sense. And now that I could run a decent and affordable Unix clone I certainly wasn't going to stick with that pile of crap that kept messing around with my data (and I was very close to the MS people at the time who admitted that most of their stuff mostly didn't work).

      Anyone who believes he learned anything worthwhile about computing by poking at Windows is severely misinformed ("memory management" ?? In *Windows* ?? huh ? hello ?)
      --

      May contain traces of nut.
      Made from the freshest electrons.
  2. Client vs. Server Applications by chris098 · · Score: 5, Interesting

    I'm guessing the majority of the applications written to target Linux are server applications. It would be interesting to see if this can be explained by a result only in the server application space, or if more client applications are also being targeted at Linux. Of course, in order to find that out, one would probably have to pay to view the full report.

    1. Re:Client vs. Server Applications by fyngyrz · · Score: 5, Interesting

      We don't do server apps, and we considered linux quite seriously.

      We have abandoned windows as a development platform, but it wasn't linux that replaced it, it was OSX. Linux's lack of a standard GUI layer in the OS - modern menus, buttons, lists, even windows - is the primary issue for us. There are lots of things that are very attractive about linux, not the least of which is a large user base that we think would have an interest in some of the things we can offer, and so we do keep an eye on what is going on. But there is a long history of independent widget development projects with quite a range of capabilities, licenses and corresponding legal issues, and in some cases, prices for commercial use; there's no certainty there will ever be a standard graphics layer. In my opinion, which is only one fellow's outlook (though I do control my company's direction) this is a key factor.

      Both Microsoft and Apple have some pretty nice interface builders; that'd be a factor too, presuming that the embedded graphics eventually gets past xwindows and user-land layers on top of it. And by the way, I'm not advocating any of that be dropped; just that a standard be added to the OS that anyone can use in any way without any issues, just as one can use the fopen() call and know it'll be there and neither legal nor accounting will have to be called because the call was used.

      --
      I've fallen off your lawn, and I can't get up.
    2. Re:Client vs. Server Applications by ushering05401 · · Score: 2, Insightful

      The increase in web development probably has a lot to do with this. Many Windows coders had nothing to do with the web because their apps were traditional desktop apps. Now the possibilities of the web are not only more fleshed out, but large companies are showing the way toward the web as a partial replacement for traditional desktop programs.

      That being said, TFA data goes against my personal experience.

      Almost everyone I know is now experimenting with Linux, with slow adopters and doubters being prodded by Vista to finally look over the fence, but I don't know of any Windows developers who have abandoned Windows development altogether.

      Your comment, chris098, falls directly in line with my experience. The first step most developers I know are taking is evaluating Linux as a server platform... tweaking/playing with/learning about the O.S. in that capacity.

      Regards.

    3. Re:Client vs. Server Applications by jimstapleton · · Score: 4, Interesting

      I typically use QT as it works in just about anything.

      You can use GTK instead if you like. Or if you want something that works in anything, but looks different every version, you can always use WX.

      Add in a platform independant language like Python if your application is not extremely intensive (and sometimes, even then), and you have an extremely nice setup for anyone to use.

      And QT has a very modern (and more importantly, customisable) look. It comes with a little app, and you [the user], can set GUI appearances that the developer left as default, to look like Windows, MacOS 9, MacOS X, and QTs native, amongst others. It also pulls the system default colors for various field types, which is extremely nice.

      --
      34486853790
      Connection too slow for X forwarding? Try "ssh -CX user@host"
    4. Re:Client vs. Server Applications by LWATCDR · · Score: 4, Insightful

      "Linux's lack of a standard GUI layer in the OS - modern menus, buttons, lists, even windows - is the primary issue for us."
      It shouldn't be. The solution is really simple
      Qt if you are going to GPL your code and want to code in C++
      Qt if you don't want to GPL your code and code in C++ just pay Trolltech for the none free version.
      GTK if you want to code in C or C# GPL or not since you can use it under LGPL.
      GNUStep if you really want to use Objective C and don't mind being different.

      I mix Qt and GTK apps at will on my Linux desktop. For many applications your choice between GTK and QT really doesn't matter. Okay I hate GTKs file dialog Qts is a lot better IMHO but even that isn't a really big issue. I use Eclipse CDT which uses SWT-GTK for it's interface on Suse 10.1 running KDE. No big problem.

      The lack of a standard windowing tool kit just isn't a big deal. Frankly I suggest just going with QT and then you can make your code run on Windows, Mac and Linux with very little effort at least as far as the UI goes.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    5. Re:Client vs. Server Applications by Cyberax · · Score: 2, Informative

      QT costs A LOT of money (about $3000 per developer, AFAIR). _AND_ you can't legally use KDE's functions, because KDE is GPLed.

      So, GTK is the only viable alternative (and guess what, most commercial Linux apps use GTK).

    6. Re:Client vs. Server Applications by jimstapleton · · Score: 2, Informative

      Additionally, it's not $3000 per developer, but $3000 for the first developer, for each dev thereafter, the price decreases sharply. Also, if you do your program right, you shouldn't need a lot of UI developers.

      And, depending on what you are doing and how you are releasing it, you may still be able to use the Free version.

      --
      34486853790
      Connection too slow for X forwarding? Try "ssh -CX user@host"
    7. Re:Client vs. Server Applications by jimstapleton · · Score: 2, Interesting

      No, I don't statically link to QT, I use it as a library, and the specifically allow that useage.

      The people at PC-BSD thought the same thing. So PC-BSD specific software was GPLed since they used QT.

      It's now BSD also, for the same reason that you are incorrect. Namely - you can use QT without having to GPL your stuff.

      --
      34486853790
      Connection too slow for X forwarding? Try "ssh -CX user@host"
    8. Re:Client vs. Server Applications by Nevyn · · Score: 3, Informative

      Linux's lack of a standard GUI layer in the OS - modern menus, buttons, lists, even windows - is the primary issue for us.

      I'm sorry, what? This isn't 1995 anymore where Motif and libXaw were the main GUI toolkits. gtk+, pygtk, gtk#, SWT, etc. are shipped in every distribution containing all the common widgets and are free to use. Maybe you mean your visual-studio developers can't use anything else? Well have fun in hell with that snowball waiting for MS to port the apps. you've locked yourself into.

      --
      ustr: Managed string API with ave. 44% overhead over strdup(), for 0-20B
    9. Re:Client vs. Server Applications by Srin+Tuar · · Score: 4, Insightful

      Wow, that is an amazingly uninformed post.

      X-windows together with any of the popular graphical toolkits is every bit as fast as windows GDI primitives, and very similar to what apple's DPS does to draw widgets. The old fashioned integration of graphical primitives directly into the operating system is exactly what everyone is trying to get away from, as it tends to make everything suck. Take one look at beryl and youll see the future of eye candy is going to be coming from the free software camp.

      Now, in addition to that, you are taking the licensing issue 100% backwards. With any OSS toolkit, the terms and source are 100% disclosed, and many times simpler than proprietary licenses. The toolkit you choose will be around forever as surely as if you own it yourself. I don't suppose you have ever read one of MS or Apple's EULA's, but to sum them up you are essentially placing yourself and your company at their mercy when you develop for their platforms.

      If your reason for choosing proprietary products is because you plan to make proprietary products, that at least would make sense. But keep in mind that the product model for software is receding into history, and you may need a change of business model in the forseeable future.

    10. Re:Client vs. Server Applications by Cyberax · · Score: 5, Interesting

      No, you can't (effectively).

      You can have your code under BSD license, because it's less restricting than GPL. But if anyone tries to use your application as a part of a commercial closed-source project, then they will be violating _GPL_ license of QT. Which, sort of, defeats the whole purpose of BSD license...

      You can have QT in BSDs without GPLing the whole thing because of the 'aggregation' clause in GPL.

    11. Re:Client vs. Server Applications by Altus · · Score: 2, Informative


      thats all well and good but when you want to use QStrings everywhere in your application (because they work well, support translation nicely and are compatible with your UI) all of a sudden everyone needs a license or you have to have some kind of compatibility layer so that your back end doesn't need QStrings.

      Its doable, but its not trivial.

      --

      "In America, first you get the sugar, then you get the power, then you get the women..." -H. Simpson

    12. Re:Client vs. Server Applications by Cyberax · · Score: 2, Informative

      Nope. EACH developer who needs to compile sources which use QT should have a developer license (that's what our legal department said after talking with Trolltech). In practice, it's easier to buy license for every developer.

      BTW, I was wrong with the price. It's $6600 per developer for three-platform desktop edition - http://trolltech.com/products/qt/licenses/pricing

    13. Re:Client vs. Server Applications by LWATCDR · · Score: 2, Informative

      No QT is free if your software is free.
      It only costs if you charge for your software.
      Frankly the price starts out at 6600 for Mac, Windows, and Linux for the first developer I think. Not all that expensive for a such a great tool.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    14. Re:Client vs. Server Applications by Just+Some+Guy · · Score: 2, Interesting

      I don't know of any Windows developers who have abandoned Windows development altogether.

      We did.

      At least, in the sense that we're now targetting Python + wxWidgets (and soon QT4) for pretty much all new development. Most of our programmers still use Windows as their desktop OS, but all of our new software is testing to work at least on Windows and Linux (and FreeBSD for server stuff, and OS X if we're bored).

      Honestly, we've had enough of vendor lock-in. Sure, our programs still need to be able to run on Windows but that's only part of the requirements now. Given that we've already rolled out Firefox, Psi (for Jabber messaging) and OpenOffice.org on every desktop, we're only one major release of our in-house core application away from not needing Windows anymore. We'll almost certainly still use it, at least until we can't get security updates for XP/SP2 anymore, but it's now at our convenience rather than by mandate.

      --
      Dewey, what part of this looks like authorities should be involved?
    15. Re:Client vs. Server Applications by pherthyl · · Score: 2, Informative

      For example, you couldn't create something as simple as a statusbar item with QT, AFAIK.

      I think this is what you want: http://doc.trolltech.com/4.2/desktop-systray.html/

    16. Re:Client vs. Server Applications by PitaBred · · Score: 2, Interesting

      So... how portable are your apps? They're not, you say?

      You could have at least picked GTK and had Windows and Linux compatibility. Seems like you guys threw out the baby with the bathwater. Your OSX widget library cost $0, but how much does each development-grade Mac cost? Or are you doing all your work on Mac mini's?

    17. Re:Client vs. Server Applications by CompMD · · Score: 2, Interesting

      Our company writes software in Delphi, and we seriously considered using Kylix to release our software to Linux users in addition to Windows users. We ran into too many issues since the program had too many Windows specific things added in that it wasn't worth it to go that route.

      Then there's the other side. We use a lot of scientific and engineering software that will only run on proprietary Unix systems. Recently, the developers of one of those programs decided to try and port their 64-bit Unix version of a CAD/CAM/CAE package to Linux to compete with their lighter and less stable Windows version. It didn't go over so well. They retained ye olde Motif UI on this brand spanking new program in 2006. After a lot of people were upset by this, the next release of the program saw a somewhat nicer UI. This same company is also planning on cutting development for HP-UX, Solaris, and AIX, and instead focusing on Windows XP, Windows XP x64, and Linux (64-bit), while porting their software to OS X (10.5 64-bit) with their next release.

      Just thought I'd throw that in the mix.

    18. Re:Client vs. Server Applications by fyngyrz · · Score: 2, Informative
      The solution is really simple

      No, it really isn't. LGPL is the only general solution right now for a typical commercial application, and it presents problems with IP; specifically, section 4d, which boils down to providing code for the user to recompile that links to the LGPL'd libraries (not likely with most commercial IP models), or depending on the fact that the user has the library on their system already, which you can't do, because if they don't, your app, and therefore your whole commercial premise, is down the drain. A commercial application has to be install and run. Anything more than that and complications and problems ensue. Either way, because there is a license involved, legal has to sign off on it and that takes time, money, and can in some cases bring the entire process to a halt when legal won't sign off on something the license requires (such as source code distribution.)

      Here is 4D for reference, emphasis mine:

      4. Combined Works.

      ...

      d) Do one of the following:

      0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.

      1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.
      --
      I've fallen off your lawn, and I can't get up.
    19. Re:Client vs. Server Applications by TheRaven64 · · Score: 2, Informative
      You're getting a lot of Qt and GTK fanboys replying to you, but I wonder if you've considered GNUstep. If your app just uses Foundation and AppKit, it should just work (GNUstep can read OS X .nib files now). If it uses more, then you might need some extra works (although things like AddressBook are supported).

      I don't know anything about your app, but you might be able to get a *NIX port almost for free. GNUstep runs on Windows too, but the Win32 back end is still a bit... interesting.

      --
      I am TheRaven on Soylent News
    20. Re:Client vs. Server Applications by LWATCDR · · Score: 2, Interesting

      Well for the Windows tool kit I think you get what you pay for. QT is much nicer than MFC.

      We feel that the time QT saves more than pays for the software.
      As to "the little guy" I would say it all depends on what you consider little. My company isn't Microsoft but it isn't two guys in a basement.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    21. Re:Client vs. Server Applications by Nevyn · · Score: 2, Insightful

      I assumed "etc." included Qt. Don't want to forget about the KDE crowd!

      So a series that only included bindings to a single widget set should have in the implicit expansion a completely different widget set? The "etc." stood for the perl elisp etc. (hope you can see where this is going now) bindings that I didn't list.

      So which is the standard? GTK or Qt?

      Let's see, GTK is the default in Fedora and Ubuntu. Mono/C# and Java basically only have GTK bindings. For a commercial entity (which you said you were) you have to pay for Qt and don't have to pay for GTK ... I'm kind of assuming, again, but this doesn't seem that hard of a question to me.

      --
      ustr: Managed string API with ave. 44% overhead over strdup(), for 0-20B
    22. Re:Client vs. Server Applications by eivindthrondsen · · Score: 2, Informative

      Pricing development software for a global is inherently very hard, because as you point out the context varies so widely. We've priced Qt according to the value we believe it provides, but recognize our pricing won't work for everyone. FYI, if you are a small business or a startup, our Small Business Program will provides licenses at a comfortable discount (http://trolltech.com/products/qt/licenses/pricing /licensing/smallbusiness).

      --
      Eivind Throndsen, Trolltech AS
  3. Perhaps Its just gotten easier.. by cybrthng · · Score: 4, Interesting

    I know more "indy" developers that code irrespective of the platform. Programming is just different these days - what took an entire staff can now be done efficiently with just a few. Is the market downsizing or has growth in the field shrank or is it more platform agnostic? How do you determine a windows coder vs a universal or only a linux/unix coder?

    Windows has some of the best tools out there - software as a whole has matured to a level that there hasn't been anything "new" and its been mostly upgrades. No wonder the market has shifted. Just because there are more developers in other environments, doesn't mean the market has dried up, just that it has matured.

    1. Re:Perhaps Its just gotten easier.. by BadERA · · Score: 2, Informative

      "what took an entire staff can now be done efficiently with just a few."

      Really? Where? Sign me up! Unless by a "few," you mean "a few US salaries," while you outsource the project to a hundred-strong team of offshore developers?

      I work in an environment with both a legacy mainframe and more current x86 applications -- both .NET and Java. Our team is growing, and we're still hungry for people with skills. Work is work is work -- it takes no less effort today to code a functional, reliable software system -- and maintain it in a mission critical environment -- than it did 10 or 20 years ago. The resulting output is simply richer.

      --
      I am, therefore you think.
  4. Linux is not another Windows by mcrbids · · Score: 4, Insightful

    What we're seeing here folks is a diversifying technological ecosystem. Windows does not "fit all", and neither does Linux. (Though arguably, Linux does fit lots more than Windows does)

    Linux will never replace Windows, because nothing else ever will. Windows is an artifact of a time when having a single platform was more important for development than having the best platform. Now that the industry is maturing, the needs are rapidly becoming commodities behind standards-based interfaces (TCP, XML, etc) while the platform itself is becoming less and less relevant. The Internet met a need that Microsoft simply couldn't provide, and now the cat is out of the bag. Vista is Microsoft's attempt to lock users in before erosion gets too bad, and it's pretty evident how well that's going.

    Windows' market share will slowly erode, slowly being beaten by an increasing number of products, services, and wares on an increasing number of platforms.

    Go standards!

    --
    I have no problem with your religion until you decide it's reason to deprive others of the truth.
    1. Re:Linux is not another Windows by quanticle · · Score: 5, Insightful

      We are far more productive just sticking to one set of code for one platform, because there are no good languages out there that work for any platform.

      Excuse me for being naive, but why not Java? Its not like Java carries any performance penalty as compared to C# - both are JIT compiled languages that are run by a VM. Java has excellent developer tools as well: both Eclipse and Netbeans have matured as IDEs.

      --
      We all know what to do, but we don't know how to get re-elected once we have done it
    2. Re:Linux is not another Windows by Stamen · · Score: 2, Informative

      People write this sometimes and it baffles me. I use Visual Studio 2005 all the time, and it's a fine IDE, but it has some major issues and I don't find it any better than Eclipse, IDEA, or NetBeans for Java (all of which run on Windows, OS X, and Linux). I'm not saying Visual Studio is bad, it isn't, but it's hardly awesome like some people describe it. My assumption is that people who say that haven't really spent any time with those other IDEs.

      When writing Java in IDEA 5 years ago, it had all the fancy editor stuff like re-factoring that Visual Studio just got. Later when I would switch over to c# from Java I always missed IDEA, Visual Studio was lagging in many ways.

      For stuff like MFC work in c++, OS X has a very nice development environment with their X-Code.

      Take a look at NetBeans 6 or Eclipse, I think you may be surprised. If you are doing web development, give up your IDE, which is just a crutch for such work, buy a Mac, buy TextMate, then learn Ruby and Ruby on Rails. Get your work done faster, smile more, and release your code on any platform you like; just my humble opinion, of course.

    3. Re:Linux is not another Windows by bladesjester · · Score: 3, Insightful

      How many people use 3 year old PC's

      Are you kidding? I've seen businesses that were still running pentium 1 systems in 2000 and 2001.

      Not everyone replaces all of their equipment every couple of years. For instance, the laptop I'm writing this on was bought in 2003. With a 2.4ghz processor and a decent amount of ram, it still performs quite well even when I'm doing development.

      As for the people who just use a computer for email and surfing, most of them don't have to get a new machine until the one they're using dies.

      It's a budget thing, and most people simply have better things to spend their money on than a new computer every other year.

      --
      Everything I need to know I learned by killing smart people and eating their brains.
    4. Re:Linux is not another Windows by Threni · · Score: 2, Informative

      > How many people use 3 year old PC's

      I'd have thought the average age of a PC is around 3 years. How many people use a new PC? Not everyone even gets a new PC - they get handed down one. Certainly that's the way it works in every company I've worked for. Developers/managers get the new ones, and they trickle down to the rest of the business. After 5 years the OS (lets face it, we're talking Windows here) stops being supported , so you'll have (right now) W2K boxes being replaced with XP (yeah, I've yet to hear of any company rolling out Vista).

      > the more the price falls the more people will replace them.

      The price of the PC isn't too important. Companies don't upgrade just because a replacement is cheap, and when a computer needs replacing it'll be replaced regardless of the cost. Most PCs belong to companies, not individuals. Individuals probably hang onto kit even longer than businesses do. It may surprise the average Slashdot reader but most people don't replace something unless it breaks.

    5. Re:Linux is not another Windows by MightyMartian · · Score: 2, Interesting

      I won't lock myself in with Mono either. It's like Wine or Samba, it will always be playing catch-up, and Microsoft is quite capable of doing screwy things. Mono is even worse than .Net, it will always be the almost-compatible .Net lookalike that will only further Microsoft's tacit assertion that it is the development platform.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    6. Re:Linux is not another Windows by poopdeville · · Score: 2, Interesting

      IMHO, Windows will only lose its dominance when cross platform development tools become as easy to use and feature rich as Visual Studio. The software that I write is all Windows-only because it is written in Visual C# from within Visual Studio (using .Net).

      This is a part of the issue, but keep in mind that most commercial software houses are going to target the biggest userbase they can. Even if they have to use Notepad to write the software.

      I would love to write software that would work on Windows, Linux, and OS X; but I work at a small development company. We are far more productive just sticking to one set of code for one platform, because there are no good languages out there that work for any platform.

      There are good languages that work for any platform. Ruby is the current favorite among fanboys. (I'll admit, it's my favorite too, for now. Though it has its warts). Java is certainly cross-platform, but it's almost as painful to code in as C.

      Writing software that works with Linux, OS X, and the other Unix-like operating systems is trivial, if you plan it right from the start. Apple has done a lot to make targetting Unix-like operating systems as easy as possible, and they keep adding tools to make porting Unix applications to OS X easy.

      For instance, OS X comes with Perl, PHP, Python, Ruby, and Java, by default. Getting GCC installed is a matter of installing the Xcode Tools. Leopard is going to include Cocoa bindings for Ruby (I'm excited about that).

      Outside of Java, Windows doesn't include any cross-platform programming language, which complicates deploying to that platform. Targetting .NET wouldn't be so bad, but Mono isn't quite ready. There are, however, Ruby bindings for .NET available.

      --
      After all, I am strangely colored.
    7. Re:Linux is not another Windows by XueLang · · Score: 2, Insightful

      Ummm, you buy a new computer.....

      Wow, they finally got money to grow on trees, huh?

      --
      Knowledge is power. Power corrupts. Study hard. Be evil.
    8. Re:Linux is not another Windows by flukus · · Score: 2, Informative

      Wow. Your wrong. Java can do most stuff on it's own and has a bajillion libraries for anything else, no cpan equivalent, but neither does .net. If you think .net libraries are excessive and javas are non existent then you've clearly never looked at the java documentation. But then again, you don't sound like a professional developer. You obviously can't read documentation and can only program with an IDE holding your hand.

    9. Re:Linux is not another Windows by Chrix++E · · Score: 2, Informative

      > it doesn't have a native look-and-feel on any platform, and it lacks integration with the OS.
      Could SWT change - partially - your mind about Java GUI? It's as native as it can get. It powers apps like Eclipse.

      http://www.eclipse.org/swt/

    10. Re:Linux is not another Windows by bladesjester · · Score: 2, Insightful

      But then again, you don't sound like a professional developer. You obviously can't read documentation and can only program with an IDE holding your hand.

      Oh boy. An "I'm geekier than you" boast. I am so sick and tired of the "real men don't use IDE" fools.

      Hate to break it to you, but the reason we use IDEs is because they make us more productive. A good IDE can help you write better code faster than using a text editor.

      Those of us who do it for a living tend to be rather fond of our IDEs. I am perfectly capable of coding just using notepad or pico and a compiler (after all, if you have that much of a hatred of people who use IDEs, anything but the most basic text editor must be evil) if I wanted, but that would, on the whole, be a waste of my time.

      Give the guy a break. Java's a big language (face it, the core o'reilly books on the subject span three volumes) and it can be a pain in the rear to work with at times, especially if you don't have a lot of experience in it and don't have someone to ask questions of.

      --
      Everything I need to know I learned by killing smart people and eating their brains.
    11. Re:Linux is not another Windows by Billly+Gates · · Score: 2, Informative

      Javadoc is your friend

      http://java.sun.com/javase/6/docs/api/

      Netbeans has a free gui designer just like vs.net where it will autogenerate your java code.

      Java is a very strict language and you need strong object oriented knowledge of inheritence to get anything done like write a hello world program.

    12. Re:Linux is not another Windows by julesh · · Score: 2, Interesting

      Java has been around a bit longer, so it actually has a bit more 3rd party support industry wide, certainly more stable support. It has a lot of open source libraries which are commonly shared across the industry, so new tools/products are generally very quick to learn and if you need to work around something a library doesn't handle well, it's a bit easier to do it in a maintainable way.

      This is something I was going to mention too. Java development has a culture of free tools that seems to be lacking in the .net world. Stuff like Apache Jakarta, Spring, Hibernate, HSQL, POI, and so on are all particularly useful tools that (it seems from my brief experience of .net programming) I would spend a while looking for and then spend some cash to get hold of if I wanted something similar for a .net application.

  5. Hardly Surprising... by Shuntros · · Score: 2, Interesting

    Embedded Linux is growing like chuff, and has been for some time. Around 3/4 of Linux jobs on my preferred job site are now for embedded, and for damn good money aswell!

    Surely that's the [regularly stated on /.] point, let people hack around with source and they'll do amazing things. Keep it all locked up in a nice blue box and what do you get? A bunch of crap smartphones which aren't clever. Meh.

  6. Nice but worthless data by grapeape · · Score: 2, Insightful

    Was it the same 400 developers surveyed? A 12% increase in Linux could mean more Linux developers or it could just mean less Windows developers. If I carefully pick my 400 to survey I could post a completely legit survey showing that OS2 is making a comeback. I hate survey's like this, unless the sampling pool is static is means absolutely nothing.

    Javascript? Thats just one step up from HTML as far as "development" goes, of course it has 3 times the users, unlike Perl, Ruby and Python all you need is 24 hours and a dummies book.

    1. Re:Nice but worthless data by swillden · · Score: 5, Insightful

      If I carefully pick my 400 to survey I could post a completely legit survey

      If you carefully pick your 400, your survey isn't legit.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    2. Re:Nice but worthless data by mhall119 · · Score: 3, Insightful

      If I carefully pick my 400 to survey I could post a completely legit survey showing that OS2 is making a comeback. I hate survey's like this, unless the sampling pool is static is means absolutely nothing. The whole foundation of surveys like this is that the sample is representative of the population as a whole. They probably chose developers in different pay grades, industries, etc. based on the total demographic percentage of developers in those pay grades, industries, etc. They "carefully pick" their 400 specifically to NOT bias their conclusion.
      --
      http://www.mhall119.com
  7. Linux is a better target for new developers. by jellomizer · · Score: 4, Insightful

    Windows is satrated with third party apps. Anything you do for windows will most likely compete with someone elses program and you will have an uphill battle to get adoption. Linux there is a huge gap of programs that it needs allowing programmers a better chance to get a good foothold as a key app. Or the more ambition the next killer app. Making software for windows will either be medocre at best (In terms of sales) or if it is a really good app Microsoft will make a clone of it and imbed it into windows so you don't have a chance of competing, or discredited for some other application. Linux apps have a better chance of getting some staying power and your new app may get some ground.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    1. Re:Linux is a better target for new developers. by misleb · · Score: 2, Insightful

      But at the same time, you have less chance of making money off Linux software if only because Linux users are spoiled with so much free software. It isn't like WIndows where users are accustomed to paying ~$20 for a fscking screansaver or a tool that takes screenshots.. or something trivial like that. The killer apps that Linux users might pay for are pretty complex (a personal finance app such as Quicken or MS Money, for example). Just being able to code often isn't enough. You have to know the target audience really well (and in the case of finance: tax law, accounting, etc). Not to mention that the development tools like Visual Studio just aren't there for Linux.

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
  8. Not suprising... by SoapBox17 · · Score: 2, Insightful

    I assume that by "nontraditional client devices" they mean embedded platforms. If so, then this really isn't surprising, or even really all that noteworthy at all.

    There continues to be a vast increase in the number of embedded chips capable of running a full-fledged OS (like Linux) and as the chips get smaller, the of course get put into more things. Not only does Windows CE not support a lot of these chips, but even if it did no one in their right mind would use windows for something that didn't need a GUI. The only time to even consider using WinCE is in a PDA like-device, and thats a very small percentage of the embedded market.

  9. .net anyone? by hxnwix · · Score: 4, Interesting

    By day, I code in WTL, Win32API and (regrettably) MFC. Like a great many, I wonder whether .net is pushing developers away from Windows.

    This mess is drawing Microsoft's attention away from the C/C++ layer, where it's sorely needed, and into what, as far as I'm concerned, is comparable to Visual Basic. Put simply, neither my employer nor I are interested in writing in a proprietary, bytecode-interpreted language. If we have to abandon our C/C++ investment, it certainly wont be for a proprietary java knockoff. It will be for the real thing, allowing us to slowly drift away from Windows.

  10. Metrics by jshriverWVU · · Score: 2, Insightful
    Curious how they count these people. Is a windows developer someone who writes strictly for .Net/Win32 API if so that makes sense. But I wouldn't call a person who uses Zend to write php scripts in Windows a windows programmer if the software will be run on a linux box with apache and php.

    It's the target platform that matters in my view, if they took this into account I'm sure that linux would be a lot higher, because it would count all of the Web 2.0 people who are hosting on Linux but write in windows.

  11. Blowing off VB6 burned some bridges by Maxo-Texas · · Score: 4, Interesting

    The way Microsoft ended Vb6 with no easy upgrade path to .net both irritated developers here and stranded some of them in vb6 with no path to .net. Some of them trained to java (tho they would have preferred .net).

    --
    She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    1. Re:Blowing off VB6 burned some bridges by dedazo · · Score: 5, Interesting
      Partly true. In my personal experience the vast majority of VB6 developers are using... VB6, actually. Which is why the VB6 IDE is supported under Vista, but Visual Studio 2003 is not.

      The lack of a clear upgrade path from VB6 has forced companies to hold off on porting, upgrading or even replacing "legacy" VB apps for a lot longer than they otherwise would. The standard average lifecycle for a LOB app in most corporate environments is about 3 years. We're going on 5 now, and unless Microsoft pulls a rabbit out of the hat somehow, these people are probably not going to go to .NET. They'll go to Java or some other technology, at least those that have the option, because some don't. Microsoft has made it really hard for a lot of folks and they're going to end up paying for that in the long run.

      Microsoft squandered the mine gold that was the enormously huge VB developer base. They should have released a follow up to the COM-based VB6 platform with improvements and provided a clear timeline for the jump to the .NET CLR. Instead one day they just announced VB6 was dead, being replaced by something that is arguably better but completely incompatible, at least from a practical standpoint.

      --
      Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
    2. Re:Blowing off VB6 burned some bridges by syntaxeater · · Score: 2, Interesting

      The way Microsoft ended Vb6 with no easy upgrade path to .net both irritated developers here and stranded some of them in vb6 with no path to .net

      So... Free live webcast classes (and also an archive for ones you missed) on msdn, free licenses for Visual Studio Express and also a VB6 Upgrade Wizard built into the IDE left you feeling "stranded?"

      You're entitled to your opinion if you don't like .Net or whatever, but saying Microsoft didn't prepare you or offer you the tools needed to evolve with them is a blatent lie. I was a VB6 developer "back-in-the-day" and I couldn't imagine sitting back and ignoring everything that was happening (this wasn't a surprise to anyone). Everytime I hear a sour VB6er, I always wonder what kind of developer they actually are. 1) It was their first language and they've never had to evolve before 2) They actually are the stereotype lazy VB developer who is just too apathetic to move on or 3) They simply refused becase of misinformation and FUD they read in random articles/blogs written by people who regurgitated it from other articles/blogs in hopes to give their site tech cred (9/10 of the articles you see provide no technical information at all - but since it's MS bashing, people just assume).

      Some developers might not like .Net, but Microsoft needed it. If you do some research, you can see exactly how much .Net has opened doors for Microsoft. Sure - every door has a group picketers infront, most of which just happened to be walking by and picked up a sign... But if you take a minute, walk by them and go inside; you're going to pick up on this very quickly and be exceptionally happy you did...

      The tools and resources are still out there (all free).

  12. Java is... by teknopurge · · Score: 2, Funny

    ubiquitous, even on mobile[linux] devices. As a Java Application Architect I care very little about what my infrastructure is, so long as it's not WebSphere. Mobile linux and Netbeans work _very_ nicely together. I can even whisper sweet nothings to Active Directory with my LDAP powers.

    Give me the Toaster-based BSD and a jre higher than 1.4.2 and get out of my way!

  13. Different niches by athloi · · Score: 4, Interesting

    For mainstream and corporate software, Windows may continue to rule, but the biggest leaps I've seen in development have been in the niches where Linux has prominence. Audio, networking, manufacturing and server-side work is booming for Linux.

    In a perfect world, this article would distinguish between development "for pay" and all development.

  14. New Ballmer Chant by Junior+J.+Junior+III · · Score: 5, Funny

    Developers! Developers! Developers! De-- hey where'd everybody go?

    --
    You see? You see? Your stupid minds! Stupid! Stupid!
    1. Re:New Ballmer Chant by feedmetrolls · · Score: 3, Funny

      Now what am I going to do with all these chairs?

      --
      You are reading a sig. Cancel or allow?
  15. Embedded Linux by hatchet · · Score: 3, Insightful

    Really not that surprising, since every other device runs on embedded linux. Everything from handheld GPS devices, electronic locks, routers, switches to satellite receivers/decoders runs on embedded linux now. It's cheapest embedded platform.

  16. Developing for Linux is just easier. by Dr.+Manhattan · · Score: 5, Interesting
    One of the reasons that Windows has the kind of IDE and debugger support that it 'enjoys' is because it needs it. Developing for Windows is nearly unmanageable without that kind of support. The Windows API is huge, complex, only occasionally and accidentally orthogonal, and in my experience mostly very poorly documented. I'm not the only one who thinks so:

    "Today we are ready for the official release of the .NET Framework 2.0. Tabulating only MSCORLIB.DLL and those assemblies that begin with word System, we have over 5,000 public classes that include over 45,000 public methods and 15,000 public properties, not counting those methods and properties that are inherited and not overridden. A book that simply listed the names, return values, and arguments of these methods and properties, one per line, would be about a thousand pages long.

    If you wrote each of those 60,000 properties and methods on a 3-by-5 index card with a little description of what it did, you'd have a stack that totaled 40 feet."

    Meanwhile, the entire POSIX spec, suitable for fully implementing a POSIX system including the utility apps, with commentary and rationales for design decisions, fits in about two and a half feet of binders.

    Intellisense is practically mandated if you want to work with an interface as baroque as Win32. And it's nice even when you're working with your own defined classes and structures. But it has its own drawbacks, as Petzold notes:

    "For example, suppose you're typing some code and you decide you need a variable named id, and instead of defining it first, you start typing a statement that begins with id and a space. I always type a space between my variable and the equals sign. Because id is not defined anywhere, IntelliSense will find something that begins with those two letters that is syntactically correct in accordance with the references, namespaces, and context of your code. In my particular case, IntelliSense decided that I really wanted to define a variable of interface type IDataGridColumnStyleEditingNotificationService, an interface I've never had occasion to use."

    I develop for many platforms at work. It's a core part of my job. I mostly enjoy writing code for Unixish platforms, and tolerate the Windows stuff. The APIs on Unix are small, well-thought-out, have few if any side effects, and tend to be thoroughly documented. I find very few interfaces on Windows have even a majority of these traits, let alone all of them.

    I've rarely felt the need for more debugging support than Linux comes with. The problems tend to be simpler and more easily uncovered. Eclipse is nice, and appears to take many of the good things about Visual Studio and leave much of the bad behind. For some projects, it's very useful. For others, it's overkill.

    Another item worth reading - the whole book, really - is The Art Of Unix Programming. For a Windows developer's perspective on the book, see here. Needless to say, I don't agree with everything he writes there, but you might find it interesting.

    --
    PHEM - party like it's 1997-2003!
  17. Re:Basic Math by lilomar · · Score: 2, Informative

    11.8 - 8.8 = 3.0
    percentage of developers on Linux now - percentage of developers on Linux a year ago = percentage of developers who switched to Linux

    3.0 / 8.8 = .34
    percentage of developers who switched to Linux / percentage of developers on Linux a year ago = percentage of Linux developers who switched in the last year

    So, the number of Linux developers increased by 34% in the last year.

    --
    The creator of this post (Jacob Smith) hereby releases it, and all of his other posts, into the public domain.
  18. Number != percent by semifamous · · Score: 3, Insightful

    TFA seems to be saying that there is a smaller *percentage* of people working on Windows as compared to other things:

    "Just 64.8 percent targeted the platform as opposed to 74 percent in 2006."

    That does *not* automatically mean that the number has declined. There may still be the same number of or more Windows developers, but their percentage is smaller because the other categories have increased.

    I hate misleading article titles. The numbers should be thought of as multiple line graphs, not a pie chart.

  19. Market Potential by lantastik · · Score: 2, Insightful

    If I am going to spend the time and effort to write a piece of commercial software, then I am probably going to want to make money off of it. Linux users in general don't like to pay for applications so there would be no way I would write a client application for Linux. Windows Administrators are leery of server applications without an installed user base, so I would tend to avoid writing server applications for the Windows platform (as a start-up mind you).

    That being said, why limit myself to one platform? It would only be a smart business decision to code for both. Hey, what do you know...I work for a company that currently does that. It's like Windows users that refuse to use Linux "because it's too complicated", or *nix users who refuse to use Windows "because of (monopoly/commercialism/shady business practices/insert random slashdot whine here)".

    If you limit your target, you only limit your market and earnings potential. That's just stupid from a business perspective. ...because guess what, neither of them are going away in the near future so you might as well be proficient at both.

  20. Re:Why target? by ThosLives · · Score: 2, Insightful

    I still like how people think that C is a platform-dependent language.

    I write stuff in C/C++ using OpenGL and it compiles and runs consistently on Windows, OSX, and Linux. I don't need any interpreters (Python) or fancy toolkits or anything.

    Platform independence is not a language issue, it's a library / API issue. If you use Win32 or .Net, you're stuck Windows (excepting Mono). If you use Cocoa, MacOSX. I suppose the equivalent on Linux would be glibc or one of the GUI toolkits. You could probably even classify Python as an API if you looked at it in a certain way.

    The standard C library is probably about as standard an API as you'll get, along with Python, Java, etc. Now, yes, I realize that some implementations are a bit goofy (or just plain wrong), but if you stick with the functions that have been around for 30 years, it's hard to be bitten.

    (Note: Also, stop using undefined features of languages, like "i = i++;"!)

    --
    "There are a dozen opinions on a matter until you know the truth. Then there is only one." - CS Lewis (paraprhase)
  21. Vista hurt the numbers, not helped by caywen · · Score: 4, Interesting

    FTA: "The arrival of Windows Vista likely only kept the numbers from being even worse." I think that Vista actually hurt the numbers. Not so much Vista itself, but in Microsoft's post-launch execution. Microsoft's big developer hotness is supposed to be all these great .NET technologies. But the lack of Vista adoption might be putting the brakes on developer enthusiasm because Microsoft is failing to lead the way in showing the end result benefits of it. COM didn't really catch on until Microsoft started demonstrating how hot it was through dogfooding and releasing applications architected on it. With it came a greater degree of modularity and flexibility that they demonstrated compellingly well with IE, Office, Visual Studio, etc. To this day, Microsoft hasn't delivered any real WPF+WCF applications - at least none that a significant number of people care about. They should be pumping out amazing applications that can be showcased on Vista, causing developers to envy and copy them, and causing customers to actually want Vista because of the hotness the developers *and* Microsoft are offering.

  22. Too bad no Mac numbers... by micromuncher · · Score: 2, Insightful

    Because most of the Windows defectors I know have gone to OSX.

    --
    /\/\icro/\/\uncher
  23. I'm actually sad about this by dinther · · Score: 3, Interesting

    But not surprised. In the last few years Microsoft has increasingly taken a "My way" or the "High way" approach to software development. Like many others I work as a full-time software developer for many years now and these day's building a working solution is the easy part. The hard part is to make sure it runs at a customers site. The very thing Operating systems are supposed to enable.

    The hack and slash security patches Microsoft brings out these days often unexpectedly denies features in the API on which solutions are based thus rendering large chunks of our code useless and a workaround must be found.

    Security is important in a connected world and indeed not recognised enough my many programmers but the hap hazard ducks and dives in Windows makes it hard to tackle this issue in a structured way. Often I find myself hacking my way around "Security patches" in order to restore functionality in our software.

    Add to that this crazy program (I refuse to call it an operating system) called Vista which is is so secure you hardly can run anything on it. I imagine the next version of Windows is 100% secure as it will only run "Notepad" and "Calculator"

    So, bottom line. If the Operating System no longer allows us to use the hardware to drive our programs then the OS get's in the way. For me the problem is that I have a huge skill base in Windows and my programming tools that I don't like to give up. But for some of my projects I seriously consider to try my hand at Linux so I can provide a turnkey solution (Include the OS with the software).

    MS Windows has become like a government. It is supposed to serve but instead it now insists to rule the IT world.

  24. North American developers? by mutterc · · Score: 3, Insightful

    What's the point of polling North American developers?

    The 11% decrease in Windows targeting could be because one of the 9 still working here switched to Linux.

  25. If only it were true. by John+Sokol · · Score: 2, Insightful

    It might be but with a sample of "400 developers and IT managers in North America"
    there is just far to small of a sample that the margin of error is probably well over 20%

    Also where and how where these "developers and IT managers" sampled.

    At a Microsoft Developers conference?

    Most Linux developers I know are broke and living on almost nothing but air. Many are student, very green (save the environment) or have some other oddness like being idealistic or so focused on Cool stuff they forget that they need to have an income.

    Odds are that these guys did not get surveyed.

    With only such a small sample, I don't give much weight to the results.
    Also it take about 10 Windows developers to get the same work accomplished as one Linux developer.
    Most windows development is dealing with Bugs, Features, bad documentation and changes from Microsoft rather then with real forward progress.

    I'd love to know what they think developers are moving over too? Cross platform stuff like Ajax, TCL, PHP and Java? Cross platform C++ and C? Much of the application layer stuff I work on tends to be platform Agnostic like that. The rest is Kernel and Drivers that are every OS specific, although I even did 2 drivers that were windows and Linux cross platform. It even worked to my own amazement.

    John

    --
    I am always doing that which I can not do, in order that I may learn how to do it. - Pablo Picasso
    1. Re:If only it were true. by boybaha · · Score: 2, Informative
      A sample size of 400 is actually a pretty good sample. Assuming a global developer population of 10,000,000, a sample size of 400 would give you a margin of error of 5%.

      With a population of the same size, in order to get a margin of error of 20%, you'd need a sample size of 25. If the North American developer population is even a third of this, you'd get around 5% margin of error as well, so I'd say that statistically speaking that 400 is a pretty good sample size.

      These calculations were taken from http://americanresearchgroup.com/moe.htmlAmerican Research Group's Margin of Error Calculator

  26. Useless by matthewcraig · · Score: 2, Interesting

    A whole article on statistics, yet no where does it say what is the confidence level. Is the percent error +/- 10% ? If so, then this is a bogus story. Since it doesn't bother to even say, then this reporting is rubbish. Where's your love for mathematics, Slashdot editors?