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.

431 comments

  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 Anonymous Coward · · Score: 0

      Even after all these years, that performance is just as... visceral.. as the first time I ever saw it. Sort of like catching a chair with your gut.

      Getting back to the present day, it seems to me that the migration of developers from MS to Linux, etc, is inevitable. Because as a guy gets older, it becomes harder and harder to do the Monkey Dance with the correct amount of vigor.

    3. Re:Ob.. by nschubach · · Score: 1

      I just can't get enough of that video, especially the hobbling around and screaming at the top of his lungs :P

      --
      Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
    4. Re:Ob.. by RaNdOm+OuTpUt · · Score: 0

      Actually, it should be "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 have stopped loving Microsoft YEAARRGH!" Lameness filter avoidance needed to here, which needs to be long to fully counteract the actual content here.

      --
      13. Any legal action is absolutly excluded. (Pi World Ranking List rules)
    5. 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
    6. Re:Ob.. by xENoLocO · · Score: 1

      Isn't 11% "only" the share of the preferred browsers that firefox enjoys? It's a big deal then... I would say this is a decent size deal.

      --
      "The need to build the internet comes from something inside us, something programmed... something we can't resist."
    7. Re:Ob.. by sw1tchd0ct0r · · Score: 1

      I never knew steveb had such good rhythm...

    8. 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.
    9. 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.

    10. 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?

    11. Re:Ob.. by VagaStorm · · Score: 1

      Your reason for loving windows just made Steve trow a chair out the window....

    12. Re:Ob.. by Anonymous Coward · · Score: 0

      What an embarrassment to existence.

    13. Re:Ob.. by Anonymous Coward · · Score: 0

      That video needs the caption "Would you buy an used car from this guy?"

    14. Re:Ob.. by aichpvee · · Score: 1

      You're glad you had to learn about a "registry?" WTF!??! The registry is one of the stupidest things ever put into windows. Copying it for gnome very well might be the stupidest thing EVER put on Linux, but I won't say that for sure because miguel de icaza does a LOT of dumb stuff on Linux.

      --
      The Farewell Tour II
    15. Re:Ob.. by smittyoneeach · · Score: 1

      "nontraditional client devices"
      Which gadgets run a lot of linux, as well.
      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    16. Re:Ob.. by Brotherred · · Score: 1

      You're glad you had to learn about a "registry?" WTF!??! The registry is one of the stupidest things ever put into windows. Copying it for gnome very well might be the stupidest thing EVER put on Linux, but I won't say that for sure because miguel de icaza does a LOT of dumb stuff on Linux. Quite right just like Moonlight which may just be the key for Microsoft's Silverlight to dominate its new space.
      --
      Those that do not know, pay for it.
    17. Re:Ob.. by Air-conditioned+cowh · · Score: 2, Funny

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

    18. 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

    19. Re:Ob.. by master5o1 · · Score: 0

      I suppose that this is the reason why they are not siding with MS so much: Ballmer was yelling at them :P

      --
      signature is pants
    20. Re:Ob.. by pato101 · · Score: 1

      (c) The magnificent HP-48

    21. 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.
    22. Re:Ob.. by Anonymous Coward · · Score: 1, Insightful

      Enough with the fucking car analogies already! They're all horribly broken and unimaginative. For one thing, the guy is a developer not a car mechanic.

    23. Re:Ob.. by jbolden · · Score: 1

      You are too young. HP teaching a generation to program (and better yet the virtues of a stack / functional programming language). Look at the 25C to the 28S. They was doing it 2 decades before the 48 came out.

    24. 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.
    25. Re:Ob.. by pato101 · · Score: 1

      :) I began programming with a 48K spectrum. But when I studied 2nd course of my career I purchased a brand new HP48SX (they become available to the public just that year, 1 year older mates had an HP28s). The solver feature was crucial to pass thermodynamics exams. Then I began programming gases formulas, which I nested comfortably in the equations to solve. Finally I learnt how to program the thing, and I spent a lot of time with that machine. Too bad the ON key has stopped working. I miss my HP, (nevertheless x48 is a good substitute)

    26. Re:Ob.. by vuffi_raa · · Score: 1

      commodore 64 yes, I used at home- but when I was in elementary they taught us to program on an apple IIe

    27. Re:Ob.. by UnknownSoldier · · Score: 1

      More like glad how NOT to do things, you mean.

      I don't understand how Microsoft can consistently take a simple idea, and obsfucate it.

    28. Re:Ob.. by PopeRatzo · · Score: 1

      I believe the idea is that by centralizing your computer, grandma doesn't have to worry about antivirus or installing updates.
      You're right, but grandma and I have different computing needs.
      --
      You are welcome on my lawn.
    29. Re:Ob.. by Anonymous Coward · · Score: 0

      I trow he did :)

    30. Re:Ob.. by Xabraxas · · Score: 1

      You're glad you had to learn about a "registry?" WTF!??! The registry is one of the stupidest things ever put into windows. Copying it for gnome very well might be the stupidest thing EVER put on Linux, but I won't say that for sure because miguel de icaza does a LOT of dumb stuff on Linux.

      You have absolutely no experience with GConf other than glancing at gconf-editor if you think GConf is anything like Windows' registry. GConf is text based, not binary so corruption can be fixed. GConf isn't required to start the computer so a corrupt GConf won't cause your OS to fail to start like the famous C:\Windows\System32\Config errors. GConf also has different interfaces including a CLI tool. So the only remaining similarity is the fact that they both offer centralized configuration storage. So what you're saying is that centralized configuration is bad. I guess my question is why?

      --
      Time makes more converts than reason
    31. Re:Ob.. by aichpvee · · Score: 1

      Because I don't run gnome and it's annoying when I have to deal with that shit just to run a program that's written in gtk because the author is so fucking stupid as to use it?

      --
      The Farewell Tour II
    32. Re:Ob.. by Anonymous Coward · · Score: 0

      Scripting in PhotoShop?
      http://www.adobe.com/support/downloads/detail.jsp? ftpID=1536

      Scripting in PaintShop Pro?
      Python!

      Application on windows?
      http://msdn2.microsoft.com/en-us/library/ms950396. aspx
      Python
      Perl
      many more

      To make "application":
      1. Open notepad
      2. Write code
      3. Save file
      4. Double click
      5. ???
      6. Profit

      It wasn't difficult, was it?

    33. Re:Ob.. by Xabraxas · · Score: 1

      Because I don't run gnome and it's annoying when I have to deal with that shit just to run a program that's written in gtk because the author is so fucking stupid as to use it?

      Ok so your real issue is having to deal with GNOME's centralized management system when you don't use GNOME. Why didn't you say that in the first place? What does that have to do with Windows' registry? Why is an author stupid to use GConf if he intends his application to be a GNOME application? Because you don't like it? At this point you're just whining about your preferences.

      --
      Time makes more converts than reason
    34. Re:Ob.. by ToasterMonkey · · Score: 1

      I think I understand your point, but learning memory management, shared libraries, and... system databases through the problems present in Windows (or anything you have to use frequently) is hardly an efficient way to learn anything.

      The ability to learn those things wont go away anytime soon, you just don't have to deal with them on a daily basis. That's a good thing.

      I've heard the same sorts of arguments as yours in regards to modern cars. Thank god you don't HAVE to get under the hood often, but if you really WANT to learn about small engines, what's keeping you from buying an old motorcycle, tractor, lawnmower, etc.

      P.S.

      I'll trade you all my old winmodem, active desktop, fun with early 3D cards, rebooting two-three times a day, viral infection experiences for all your old Mac ones. I'll throw in windows laptop hibernation issues to boot. I wouldn't care to remember ANY of those.

    35. Re:Ob.. by Anthony+Baby · · Score: 1

      Definitely have to agree. I had access to an Apple ][ as a kid, and that gave me an initial interest in computers beyond my Atari VCS. Then I got to use the Amiga and the C-64. I didn't get a PC until I was in college, and by that time I was doing a lot of programming in BASIC. I do credit the PC and specifically Turbo C++ for DOS in giving me an interest in programming languages. Without it, I would be chugging away with FORTRAN and BASIC. However, it was UNIX that exposed me to other languages like Perl and Java, and made me think deeper about computing. As for my Mac... well, back then everyone knew Macs were just for games and nifty art programs, unlike those crappy PCs that could only run word processors. ;-)

  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 Anonymous Coward · · Score: 0

      I don't know, most developers are writing software destined for internal company use only where CLI or curses based GUI's are king. Failing that, it's Java or Microsoft stuff.

    2. 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.
    3. 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.

    4. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      Not having standard GUI on Linux is as annoying for programmers as is fopen() was different depending on the filesystem used by the OS.

    5. Re:Client vs. Server Applications by DraconPern · · Score: 1

      I am guessing close to 33% of the respondents are writing server side apps from the response of "supports virtualization". If the poll question asked, "does your application support virtualization? Yes/No", only the the people who write server stuff will check yes since virtualizing client apps doesn't make sense. We can also infer that more devs are moving toward server based apps from the 42% stats. I think we are seeing the web 2.0 stuff hitting corporate development, and allowing traditional client apps to be ported to the server space. Just look at all the asp.net components that are now ajax ready.

    6. Re:Client vs. Server Applications by __aamnbm3774 · · Score: 0

      The article also failed to mention a lot of developers might be holding off until .Net 3.5 is fully released, which will undoubtedly increase Windows development percentage. And the fact ASP.Net websites 'might' be considered cross-platform leads me to believe this article is FUD.

      BUT, as a current .Net developer, I cant afford not to pay attention to those numbers. I guess I should download 2007.0 when I get home.

      Keep your friends close, but keep your enemies closer.

    7. 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"
    8. 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.
    9. 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).

    10. Re:Client vs. Server Applications by jimstapleton · · Score: 1

      Yes, but you don't need KDE functions to use QT.

      I did not know about the developer cost, I just use the free download.

      Then again, my software is free and BSDed...

      --
      34486853790
      Connection too slow for X forwarding? Try "ssh -CX user@host"
    11. 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"
    12. Re:Client vs. Server Applications by Breakfast+Pants · · Score: 1

      Then you are breaking the qt license, which is GPL.

      --

      --

      WHO ATE MY BREAKFAST PANTS?
    13. Re:Client vs. Server Applications by Anonymous Coward · · Score: 1, Interesting

      Having had to develop using Qt (I believe version 3) and Cocoa, I'd rather program in Cocoa any day. Qt (v 3 in this case) was simply too 'static' for my tastes, it was too difficult to add new functionality or extend the existing functionality without a lot of extra work. It flat out annoyed me.

    14. 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"
    15. 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
    16. 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.

    17. Re:Client vs. Server Applications by jimstapleton · · Score: 1

      I use QT4, it's easily extendable, and unlike Cocoa, it doesn't limit me to one platform. Cocoa would limit me to a platform I find difficult to use (nearsighted + Mac UI = bad).

      --
      34486853790
      Connection too slow for X forwarding? Try "ssh -CX user@host"
    18. Re:Client vs. Server Applications by jeevesbond · · Score: 1

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

      I don't really understand why this would be a problem. You choose either QT, GTK or whatever. If someone wants to run your application then the libraries are only an apt-get/yum/[insert package manager here] away.

      If you distribute your software as deb and rpm packages those pesky dependencies are handled by the package manager. Moreover integration between the widget sets has been getting better: using Firefox under KDE has pretty-much the same look as a native QT application (such as Konqueror) for me. The situation will only improve.

      I could understand if you're developing proprietary software though. That stuff doesn't seem to gain much traction in the FLOSS world. Pixel is a good example: great photo editor, low price, but not many people use it. Why? On Windows/Mac everyone pirates/buys Photoshop and on GNU/Linux people would rather use the GIMP than a proprietary product (sorry I don't have any evidence to back that up, just personal experience from reading forums and such).

      --
      I'm going to transform myself into a mighty hawk. Either that or I'll just go and work at Dixons, haven't decided yet.
    19. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      here you go. It's good for commercial and/or GPL projects, and the commercial version is royalty free (you only pay for the development environment).

    20. 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.

    21. 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

    22. 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

    23. Re:Client vs. Server Applications by Altus · · Score: 1


      Easily extendable? they locked down many of the features that you could modify easily in QT3. Many functions are no longer virtual and they use private implementation classes under the covers which are hard to replace.

      Your concerns about cross platform compatibility are very valid, but I don't find QT to be all that extensible compared to many other UI frameworks and it is no where near as extensible as Cocoa (mostly due to the nature of objective C)

      --

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

    24. Re:Client vs. Server Applications by misleb · · Score: 1

      As a Mac user and hobby developer, I'd much rather stick with native UI components for whatever platform I'm targetting. Sure, QT can LOOK like an OS X app, but as far as I know you miss out on a lot of integration with the OS and advanced Cocoa features. For example, you couldn't create something as simple as a statusbar item with QT, AFAIK. A better approach, IMO, is to design the application using strict MVC approach (which Apple already encourages with Interface Builder) and have a different view layer for each platform. That way there's no question about look and feel.

      Though I can't say I've really seen a non-trivial QT app on OS X. Maybe it is "close enough." But given my experience with Java/SWT, I have my doubts.

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    25. Re:Client vs. Server Applications by macemoneta · · Score: 1
      From this article:

      The survey featured developers at enterprises, VARs and system integrators, and covered both client and server application development. According to the survey, the decline in Windows targeting by developers started in 2005, and has increased year-over-year as Linux matured and gained in popularity as an enterprise level OS.
      The numbers quoted in that article are also a little different:

      ...the number of developers targeting Linux for their server- and client-side applications increased by 34% over the past year. ...the growth in Linux development came at the expense of Microsoft Windows, which decreased 12% from one year ago.
      --

      Can You Say Linux? I Knew That You Could.

    26. 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.
    27. 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?
    28. Re:Client vs. Server Applications by Jugalator · · Score: 1

      wxWidgets is a cross-platform API that is quite unique in that it uses the native UI widgets:
      http://www.wxwidgets.org/

      As a Windows user, I'm also happy that I don't have to use some sort of "platform neutral" UI, that usually only do a compromise for limited UI functionality for all platforms instead. I've seen too much of that happen with Java and GTK apps. :-(

      --
      Beware: In C++, your friends can see your privates!
    29. Re:Client vs. Server Applications by LWATCDR · · Score: 1

      "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 foreseeable future."

      Get back to me when there is a FOSS CAD program that is as good as Solidworks. Heck get back to me when there is one as good as TurboCad.
      Sorry but that product model is live and well for many segments that FOSS just doesn't work for. There isn't on solution for every problem.
      PS I develop under Linux using FOSS tools. There are some that are very good.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    30. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      OpenCASCADE is more of a CAD application builder than a CAD application, but is extremely powerful. VARKON is highly parametric, so may take a bit of getting used to, but is also used for "real" work.

    31. Re:Client vs. Server Applications by pherthyl · · Score: 1

      You don't need the KDE libraries. Qt is an incredibly comprehensive framework. It's not just Widgets, its database access, xml, network, threading, lots of incredibly useful types etc.

      And if you want the extra functionality of the kdelibs, you can legally use them, they are not GPL, they are LGPL, so you can link to them from a proprietary application with no problem (as long as you paid for Qt).

    32. Re:Client vs. Server Applications by Laur · · Score: 1

      AND_ you can't legally use KDE's functions, because KDE is GPLed.
      KDE's library's (kdelibs) are actually LGPLed, so you should be able to use them with the commercial version of QT just fine. Many of the KDE applications are GPLed, but that shouldn't affect you very much.
      --
      When you lose something irreplaceable, you don't mourn for the thing you lost, you mourn for yourself. - Harpo Marx
    33. Re:Client vs. Server Applications by pherthyl · · Score: 1

      What exactly can't you do in Qt? I use it quite extensively, and have written quite a few custom controls, without any problems whatsoever. It would be interesting to hear what you think can't be extended easily.

    34. Re:Client vs. Server Applications by LWATCDR · · Score: 1

      I will take a look at them but I doubt they are equal to an off the self cad system.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    35. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      standard GUI As in one, not more than one.
    36. Re:Client vs. Server Applications by Delkster · · Score: 1

      As a Mac user and hobby developer, I'd much rather stick with native UI components for whatever platform I'm targetting. Sure, QT can LOOK like an OS X app, but as far as I know you miss out on a lot of integration with the OS and advanced Cocoa features.

      I believe that when GP said "I typically use QT as it works in just about anything" he possibly meant that it works on just about any Linux platform. Besides, if getting things to run on different OS platforms without changing the UI toolkit had been GP's point, Cocoa would be one of the last things to settle on. (But yes, having a separate UI implementation for each platform might be even more preferable -- and this is quite possible with many F/OSS applications if someone bothers to write the specific UI for $platform.)

      And yes, Qt does work on just about any Linux platform. Gtk may just be more preferable for developers of proprietary applications because it's licensed under the LGPL and thus allows dynamic linking from software regardless of the license, unlike the GPL that Qt is licensed under (unless you get a commercial license which costs money).

    37. 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/

    38. Re:Client vs. Server Applications by LEgregius · · Score: 1

      IANAL, but that's actually not entirely true. Anyone who wants to use his code in a non-free application can pay for the commercial QT license. Since his code is BSD and Qt can be commercially licensed, its fine :-). Besides, you only have to buy one license. The other developers can use the GPL version for development and the final build can be built with the commercial version for release version. There is another interesting side effect of this. If you release your app without Qt libraries and tell the user that have to get the Qt libraries for themselves, you are not distributing Qt, and therefore are not breaking the GPL. That is, the GPL says you can link it with a conflicting app on your OWN machine as long as you don't distribute them TOGETHER, it specifically says this. The "aggregation" concept refers to distribution, not physically being on the same hard drive. Since Qt CAN be non-GPL and you are distributing them together, a user can simply install the open-source versions of Qt, and run an non-GPL app with it without anyone ever breaking the license terms. I have not read the GPL 3 yet.

    39. Re:Client vs. Server Applications by Bert64 · · Score: 1

      There will always be niche markets, just as there are today, and CAD is very much a niche market...
      Where the product model will disappear, is in the mass market arena, where there is a big push to create applications so that companies and end users aren't locked in to highly expensive proprietary apps.

      That said, eventually free software will descend into the smaller niche markets too, it's just that too many people are concentrating on reverse engineering proprietary protocols and formats nowadays.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    40. Re:Client vs. Server Applications by MMC+Monster · · Score: 1

      Agree with the above. Choose a distribution and pick an interface. If you can, choose a GUI toolkit and use a standard package manager (ie: rpm or deb). Once you can make a standard package, you can probably automate the packaging and create both rpm and deb packages and target the big 2 or 3 distributions that you want to hit (likely Ubuntu and RHEL).

      --
      Help! I'm a slashdot refugee.
    41. Re:Client vs. Server Applications by fyngyrz · · Score: 1
      Not all that expensive for a such a great tool.

      Perhaps not; however, consider the OSX widget library cost to use and develop for: $0. Consider the Windows widget library cost to use and develop for: $0.

      When you put it in that light, and you have a limited development budget, $6000, or worse, $6000 a seat, does tend to at least spawn a meeting or two where something else has to be traded for that capability. That may not be possible, especially for small developers. And isn't that kind of funny? Linux's GUI development environment favors free at the one end, and deep-pocket folk at the other, while locking out the small guys. Seems... I dunno, sort of un-linuxy.

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

      wxWidgets is a cross-platform API that is quite unique in that it uses the native UI widgets:
      http://www.wxwidgets.org/ [wxwidgets.org]


      Are there any examples of non-trivial wx apps that run on OSX? I'd be interesting in seeing how well they integrate. I'd be surprised if they do it well. UI APIs vary pretty widely in how they function and how the programmmers interacts with them.

      As a Windows user, I'm also happy that I don't have to use some sort of "platform neutral" UI, that usually only do a compromise for limited UI functionality for all platforms instead. I've seen too much of that happen with Java and GTK apps. :-(


      I wonder, does Windows really have much tht resembles a "native" UI? I know Java apps stand out like a sore thumb, but then again, so do a lot of supposedly native apps on Windows. There's MFC, but does anyone really use that directly?

      -matthew
      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    43. Re:Client vs. Server Applications by fyngyrz · · Score: 1
      Cocoa would limit me to a platform I find difficult to use (nearsighted + Mac UI = bad).

      Hopefully - and I can't speak authoritatively on this, but hopefully - the release version of OSX/Leopard will be fully scalable and both you and I will get some relief for our eyes.

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

      _AND_ you can't legally use KDE's functions, because KDE is GPLed.

      Get your facts straight. The KDE lib is LGPL, not GPL. You can legally use KDE's functions in a commercial application. I discussed this a while ago on /.

      --
      After 3 days without programming, life becomes meaningless
      - The Tao of Programming
    45. 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?

    46. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      You can doubt all you want, but both varkon and opencascade are used for some high-end stuff, as a cursory glance at screenshots would show.

      Varkon is better than most CAD packages in the way that LaTeX is better than Microsoft Word for professional document layout. Though again, varkon in particular probably doesn't work like other cad packages you're used to, being pervasively parametric. But don't mistake that for being "worse" than other cad packages - it's often much better if you're doing serious stuff.

      Other CAD: BRL-CAD is still somewhat specialised towards military electromagnetic applications, but is a very nice CSG modeller.

    47. Re:Client vs. Server Applications by PitaBred · · Score: 1

      I know I've only had to change 2-5 lines to get a multi-thousand line Qt app that was developed on Linux to compile and run identically under Windows. Qt does work on ANY platform, not just any Linux platform.

    48. 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.

    49. 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.
    50. Re:Client vs. Server Applications by iluvcapra · · Score: 1

      I think, given the length of this thread, the original posters point it proven, QED.

      --
      Don't blame me, I voted for Baltar.
    51. Re:Client vs. Server Applications by Sparks23 · · Score: 1

      I think no 'cross-platform' widget system will ever be a first-class citizen of the target OS beyond what it was developed for. Why?

      Because things just simply work too differently. Look at Thunderbird; it's a great mail/news client... but on OS X, it does not integrate with the OS X system address book, nor does it support the system spellchecker's dictionary. There's a certain 'way' of doing things on any given OS, and if you try to write one single cross-platform UI (and I refer to overall user interaction here, such as the aforementioned spellcheck integration, not just the graphical aspect of the widgets), it will always feel a tiny bit 'wrong.'

      I'm with a previous poster on this; you're better off separating the front-end from the back-end processing, and writing a native, OS-specific UI layer.

      --
      --Rachel
    52. Re:Client vs. Server Applications by Cyberax · · Score: 1

      GTK looks like and behaves like s**t on Windows. We've tried to use it and had a LOT of problem.

      The only other solution is wxWidgets, but it also has big problems with applications behaving differently on different platforms.

    53. Re:Client vs. Server Applications by misleb · · Score: 1

      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


      And which one of those would be the standard? :-P

      I guess it is good that most developers have settled on the Big Two toolkits (GTK and Qt) but I would definitly be nice if there was just one standard.

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    54. Re:Client vs. Server Applications by fyngyrz · · Score: 1
      So... how portable are your apps? They're not, you say?

      They're extremely portable, m. Pitabred. They're compiled and running on windows, (red hat)linux, and OSX. Older versions - no longer developed for - run under Amiga OS, Be, every major version of Windows since WIndows 95 including RISC NT MIPS, Alpha, and PowerPC, all of which present their own problems. Our windows stuff also lives happily and easily under Parallels for OSX, and I would presume that Wine would work as we use a minimal set of OS calls. Do you have any other presumptions^W questions I can shoot down in flames ^W^W^W^W answer?

      Or are you doing all your work on Mac mini's?

      As a matter of fact, we did. A stank old PowerPC mini, in fact. So? The only thing the mini lacks as a development platform is an already installed copy of the development system, but it is on the release DVD, so it's only the work of a minute or two to get it over there, after which you can code your silly head off. We saw no reason to get anything more robust than a mini, and after having seen the port go so smoothly, I'd say that was exactly the right decision.

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

      If you have a real commercial application, you can pay for Qt. It's not the cheapest thing ever, but neither are developers.

      Now, what the LGPL requires you is that your application works with a modified library. You don't need to provide any source of your app for that. If the library is a .so or .DLL, then the application will automatically work with any library that exposes the same interface, you don't need to do anything about it. Part 1 says exactly that.

    56. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      gtk+, pygtk, gtk#, SWT, etc.

      Which of these is the standard toolkit for all Linux GUIs?

    57. 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
    58. Re:Client vs. Server Applications by dvice_null · · Score: 1

      > 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

      Don't do software for Linux, Mac or Linux. Do cross platform software. Use wxWidgets if you want to write normal desktop applications and want to have native look. wxWidgets is basicly a wrapper around native GUI components, which makes the end result look as if you have written it using the native API directly. License shouldn't be a problem either.

      If you write games, use Irrlicht or Crystal Space or some other cross platform library.

      There really isn't any reason to write a software for a single OS nowadays. The cross platform libraries are so advanced that it is easier to write cross platform applications than native ones.

    59. Re:Client vs. Server Applications by dangitman · · Score: 1

      Take one look at beryl and youll see the future of eye candy

      Yeah, because eye candy is exactly what we want more of in interface design.

      Professor Frink's sarcasm detector explodes.

      --
      ... and then they built the supercollider.
    60. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      You forgot WXWindows, which is super-cool.

    61. 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.
    62. Re:Client vs. Server Applications by dangitman · · Score: 1

      Where the product model will disappear, is in the mass market arena, where there is a big push to create applications so that companies and end users aren't locked in to highly expensive proprietary apps.

      That seems pretty counter-intuitive. Firstly, in the mass market arena, most applications are quite cheap, and there's not very strong lock-in. There are often hundreds of alternative products. On the other hand, the niche markets are where software is really expensive (often $5,000 and up. way up.) and the lock-in is much stronger. Often there are only a couple of product choices, sometimes only 1.

      Not only all of the above, but it's the niche users who have more expertise, and would be more open to a FOSS solution. They are able to put up with less polished interfaces and usability if it gets the job done. The mass market doesn't like the lack of polish of FOSSy software, and doesn't really care much about finding "alternatives". They feel much safer with the box from a company bought from the shelves or an online store. And heck, it's only like $50 to $100 - what's the big deal?

      No, it's the niche professional applications where FOSS has the most potential, and it's also an area they aren't doing very well in. Freeing a company from hundreds of thousands of dollars in software investment, license management (which is often a byzantine minefield for niche titles) and proprietary format lock-in - freeing a company from that would make FOSS developers heroes. The companies who do this kind of work would LOVE to escape the proprietary world, far more than any mainstream consumer. The reason they can't is that FOSS is miles behind when it comes to making serious productivity software. If I want to run a server, or want some geeky widget to entertain myself, that's a different story. But linux doesn't really do professional+productivity.

      --
      ... and then they built the supercollider.
    63. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      >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.

      lol...oh wait, you're serious aren't you?

      OSS wouldn't even have a decent office suite if Sun wasn't putting out the developer costs so they can hurt M$. Ditto for Netscape and Firefox.

    64. Re:Client vs. Server Applications by bl8n8r · · Score: 1

      > I'm guessing the majority of the applications written to target Linux are server applications.

      Actually, the linux embedded scene has been growing like crazy. I know very little about embedded but I've been hacking C code, and linux, since about 1993. This has been enough to jump around embedded linux stuff as a consultant for awhile and have a lot of fun with it. Employers see the linux experience and the C coding as 2+2=4 - even after I tell them I don't know an IC from an ethernet chip. They just want C code pounded out on embedded linux. I've been working like a dog for the past year on a few different projects. Makes me wonder what people that really know what they are doing, are doing. As a footnote, I've had good luck with *Armedslack and Debian

      http://cdimage.debian.org/cdimage/release/4.0_r0/a rm/
      http://www.armedslack.org/

      --
      boycott slashdot February 10th - 17th check out: altSlashdot.org
    65. Re:Client vs. Server Applications by Doug+Neal · · Score: 1

      There's easily that many different APIs for doing it in Windows too. Which one of those is "the" standard? If it's look-and-feel consistency that bothers you, that's for the distributions to worry about. And they've got pretty good at it now.

    66. Re:Client vs. Server Applications by jZnat · · Score: 1

      They're all GTK+, but in different programming languages.

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
    67. Re:Client vs. Server Applications by tjstork · · Score: 0

      That sorta makes the OS pointless, me thinks. Besides, there is a lot to be said for having a really thin and light framework for a tiny EXE.

      --
      This is my sig.
    68. Re:Client vs. Server Applications by misleb · · Score: 1

      They're all GTK+, but in different programming languages.


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

      So which is the standard? GTK or Qt?

      -matthew
      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    69. Re:Client vs. Server Applications by ChrisA90278 · · Score: 1

      There most certainly is a standard, uniform graphic interface on Linux. It's called "Xlib". (Hey that's a joke, no flames please.)

      More seriously I've started to use a web browser for my GUIs. If your needs are simple it works well and people actually like the idea. But then, I'm only doing simple DBMS based forms and not writing a game.

    70. Re:Client vs. Server Applications by Draek · · Score: 1

      That seems pretty counter-intuitive. Firstly, in the mass market arena, most applications are quite cheap, and there's not very strong lock-in. There are often hundreds of alternative products.

      two words: Microsoft Office.

      The mass market doesn't like the lack of polish of FOSSy software, and doesn't really care much about finding "alternatives". They feel much safer with the box from a company bought from the shelves or an online store. And heck, it's only like $50 to $100 - what's the big deal?

      the mass market seldom cares about the lack of polish of commercial software, so I doubt they'd complain much about something that's free (as in beer). As for the rest of your point, you're correct except that MS Office and Windows itself cost quite a bit more than $100, though if we consider piracy you may still be right, in a weird variant of "if it costs money, it must be worth it right?".

      No, it's the niche professional applications where FOSS has the most potential, and it's also an area they aren't doing very well in. Freeing a company from hundreds of thousands of dollars in software investment, license management (which is often a byzantine minefield for niche titles) and proprietary format lock-in - freeing a company from that would make FOSS developers heroes. The companies who do this kind of work would LOVE to escape the proprietary world, far more than any mainstream consumer. The reason they can't is that FOSS is miles behind when it comes to making serious productivity software.

      And the reason for that is that the niche professionals aren't doing a good job in the "develop applications and release their source-code Free (as in speech)" department, and they're the only ones who understand the niche enough to be able to design a professional-level application for it. Mass market apps get developed faster because more people want them, and more people understand how they (should?) work, so there are more people willing, and able, to work on them.

      If I want to run a server, or want some geeky widget to entertain myself, that's a different story. But linux doesn't really do professional+productivity.

      depends on how you define "professional+productivity". It's certainly true for some fields (CAD being the prime example), but not so much for others (like photography, software/web development, and some types of multimedia editing). Nit-picking, I know, but I felt it should be mentioned.

      --
      No problem is insoluble in all conceivable circumstances.
    71. Re:Client vs. Server Applications by mrchaotica · · Score: 1

      The only other solution is wxWidgets, but it also has big problems with applications behaving differently on different platforms.

      You are aware that different platforms have different human interface guidelines, right? Having an application work differently based on the platform is a feature, not a bug!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    72. Re:Client vs. Server Applications by danlyke · · Score: 1

      Yeah, well, the Mac is in the same boat. You'd be a fool to go Carbon, but it's been equally pushed over the past few years, and that leaves you with Cocoa and Objective-C glue code.

      So on the Mac you choose between Carbon and Cocoa, on X based systems you choose between Qt or Gtk. And Wx is an option on all of the platforms, so if you're going to count that as yet another standard you have to count it on Windows, Mac and X.

    73. Re:Client vs. Server Applications by aichpvee · · Score: 1

      So you're saying that developers (who I'd assume are generally making their living at it) are just not programming ANYTHING in anticipation of a new version of .net? Please, get the fuck out! That's got to be the dumbest thing I've read all day.

      --
      The Farewell Tour II
    74. Re:Client vs. Server Applications by aichpvee · · Score: 1

      That's funny, all the good commercial apps I've used for Linux use motif or lesstif. I think the reason you see so many apps using gtk has more to do with who is in control of the big corporate Linux distros than with a $3000/seat license. Because if it were just about the money there are many toolkits that are much nicer than gtk (fewer bugs, less buck passing about them) and just as Free.

      --
      The Farewell Tour II
    75. Re:Client vs. Server Applications by aichpvee · · Score: 1
      Actually, that's not true at all. From the Qt licensing page:

      You must purchase a Qt Commercial License from Trolltech or from any of its authorized resellers before you start developing proprietary software. The Commercial license does not allow the incorporation of code developed with the Open Source Edition of Qt into a proprietary product.
      --
      The Farewell Tour II
    76. Re:Client vs. Server Applications by aichpvee · · Score: 1

      Is it per person who does development or is it per developer? Like if your developer leaves the company do you have to buy a new license or as long as only one person is coding with Qt at a time is it ok to just have the one license?

      --
      The Farewell Tour II
    77. 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
    78. Re:Client vs. Server Applications by ThousandStars · · Score: 1
      The GP said: Linux's lack of a standard GUI layer in the OS

      The parent said: gtk+, pygtk, gtk#, SWT, etc.

      Are you trying to refute the GP or prove his point?

    79. Re:Client vs. Server Applications by ozphx · · Score: 1

      Christ. Thats more expensive than a Windows licence and a copy of Visual Studio. You could probably use the free express editions of VS and still be fine.

      I'm having to make some interoperability samples for a WS-Security web service in Java in Eclipse atm. Its taken days to get my build environment sorted out. Literally took a day to completely implement the server side crap in VS, and I still can only just build the java samples (anything I do dies at runtime).

      Seriously theres only so much un-tar.gz, ant, copy, config, hack, paste, patch, hack, un-tar.gz, ant, fix build.xml, ant that I can stand before I would suck gates' cock for a version of VS that lets me dev in java.

      --
      3laws: No freebies, no backsies, GTFO.
    80. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      No, kdelibs is LGPL, but thez build on Qt so you must satisfy both it and Qt's requirements. This means in practice:

      kdelibs (LGPL)+ Qt (GPL) = GPL
      kdelibs (LGPL)+ Qt (Commercial) = Only kdelibs as LGPL, rest proprietary

      NB: Many KDE applications are GPL, if you want to use code from them. Of course, this hasn't been very interesting for cross-platform development since KDE has been *nix-only, but with KDE4 being released for Windows I don't see any reason not to go with KDE, whether you're commercial or not.

    81. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      Just to ring in (along with the pounds of responses you've gotten) from a die-hard Linux zealot: everybody is fretting over what GUI toolkit to use, except Linux users. I have three machines, they all run major distros that include all of the common desktops and even the really weird ones. For what it's worth, I have a screenshot in my gallery of the panels for KDE, Gnome, and Xfce all running in TWM!

      When I go looking for a program, I could honestly care if it runs as KDE, Gnome, Xfce, GNUStep, Tcl/Tk/wish, or any crazy thing. Does it get the job done? Then it's great to have it!

      ...and thank you for thinking about us!

    82. Re:Client vs. Server Applications by drsmithy · · Score: 1

      (nearsighted + Mac UI = bad)

      Uh, why ? Relatively speaking, OS X uses default fonts on the larger side. Added to that, Macs with built-in screens tend to have resolutions that are on the low side for their screen size.

      Plus (and I say this as someone who is also shortsighted), you should be wearing glasses when you use a computer.

    83. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      The run time copy of the library already present on the user's computer system can be provided by the company.

      Think of it this way: how many dlls come with a standard windows application? You do exactly the same thing with linux (except they're .so files). If the libraries are LGPL doing it this way comes with no legal obligations.

    84. Re:Client vs. Server Applications by drsmithy · · Score: 1

      Where the product model will disappear, is in the mass market arena, where there is a big push to create applications so that companies and end users aren't locked in to highly expensive proprietary apps.

      In the "mass market arena", very few (if any) proprietry apps are expensive. It's the niche markets where software costs serious money (tens of thousands of dollars).

      It's also the niche market that, by it's nature, has very high barriers to entry for OSS.

    85. Re:Client vs. Server Applications by misleb · · Score: 1

      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.


      No, I assumed that it included Qt because, well, there's like this HUGE set of applications that use it.... that is, everything for KDE.

      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.


      I'm not the same person you originally replied to, you don't have to pay for Qt on Linux, and again, there's that whole KDE thing which makes any claim that GTK is THE toolkit standard for Linux GUI applications seem pretty ridiculous.

      -matthew
      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    86. Re:Client vs. Server Applications by owlman17 · · Score: 1

      Lazarus is as close to Delphi-for-Linux as you'll get. It uses GTK 1.2 in Linux though. (2.x is still a bit unstable.)

    87. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      I'm surprised. My general understanding was that Mac sucks as a development platform, there are so few good tools available. I have never developed (nor even used) a Mac. I've been mostly *nix developer with a little bit of Windows development experience, but I've talked to a couple of people who developed on Mac and their feeling was that Mac is not really a developers paradise.

    88. Re:Client vs. Server Applications by Cyberax · · Score: 1

      Sure. But very often Mac OS X/Linux behave different from Windows for no good reason. We had numerous problems with focus handling, controls being one pixel off grid, etc.

      It's easier with QT/GTK because they draw widgets themselves, so a lot of problem go away. If only GTK was not an ugly mess on Windows and Mac OS...

    89. Re:Client vs. Server Applications by __aamnbm3774 · · Score: 0

      So you're saying that developers (who I'd assume are generally making their living at it) are just not programming ANYTHING in anticipation of a new version of .net? Please, get the fuck out! That's got to be the dumbest thing I've read all day. calm down spazz. i guess i need to explain this further so you can understand.

      With the advent of .Net 3.5, (LINQ and all the additional features), on top of performance and security bonuses, it will certainly gain ground with new projects and corporations.

      I do not expect anyone to be sitting idly counting the minutes for its release, but some projects are absolutely (for certain) are on hold until the new release. Blow me, k? ;)
    90. Re:Client vs. Server Applications by kripkenstein · · Score: 1

      QT is free if your software is free.
      It only costs if you charge for your software.
      No, that is not accurate. You can either use Qt under the GPL, or you can pay Trolltech.

      So, if your app is GPL, or GPL-compatible, then you can use Qt under the GPL for free (and Free). But if your app is proprietary or uses a non-GPL-compatible FOSS license then you have to pay. The part in bold is what you forgot. As one example, Apache-licensed apps are a problem (although the GPL3 is compatible with Apache, so if Trolltech moves Qt to the GPL3, that particular issue should improve. I have no idea if they will do so, though).
    91. Re:Client vs. Server Applications by kripkenstein · · Score: 1

      [...]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
      Well, not for GTK, at least. If you use GTK, then you can in fact assume that users will have it on their system already since (1) it is the default on all major distros (Red Hat/Fedora, Suse, Ubuntu), and (2) if your clients are running a more obscure distro that uses KDE/Qt, and GTK isn't pre-installed, have your app pop up a little window requesting that they install GTK in order for your app to run. Simple enough.

      If you are talking about other LGPL libraries than GTK, then they might pose actual problems, depends on the specific library of course.
    92. Re:Client vs. Server Applications by gujo-odori · · Score: 1

      Hey, with Linux you get two standard GUIs, not just one, and a whole bunch of less standard ones, too. Such a deal

      Seriously, though, if you want to develop a desktop Linux app, you can choose Gnome or you can choose KDE. Either one or the other of those is the out-of-the-box default on most distros, and even if it's not the default, a KDE app will still run on a Gnome system. If I'm running, say, Ubuntu and want to use Kmail for my mail client, installing Kmail will also cause any dependencies it has to be installed with it.

      Conversely, if I'm using Kubuntu but want to use Evolution for my mail client, installing it will pull in its Gnome dependencies along with it.

      So while the lack of a single standard GUI might appear to be a problem to some extent, it's not nearly as big a one as it appears, and has actually been more of an asset than a liability to Linux and other free platforms, since you can make it be however you want it to be. I have KDE set up to vear a striking resemblance to my Mac :)

      But, if your goal is to sell proprietary software, I fully agree that OS X was a better choice, just because Linux users aren't used to paying for software and most of them don't want to use proprietary software if there is a Free alternative. I've been using Linux for ten years and in that time I have only ever bought one commercial Linux app: Atok for Linux, because it was way, way better than any [Ff]ree Japanese input method that was available in the late nineties. It was as good as its Mac and Linux counterparts, and it ran under (at least) Red Hat. But I wouldn't but it today.

      Which brings me to the other reason why proprietary software for Linux is a hard sell, especially on the desktop: if you come out with something so good that Linux users will pay for it over the [Ff]ree alternatives and put up with the relative hassle of installing proprietary software (compared to, for example, doing an apt-get install on any package in the distro repositories and having it all Just Work), somebody will be out there working very heard to duplicate the feature set in a GPLed product. I don't know if Just Systems still actively develops Atok for Linux or not; the latest pages on it are dated from 2004. If they do, I bet they sell a lot less of it than they used to, because the GPLed alternatives have caught up. Scim + Anthy is a better than the Atok for Linux I bought in the late nineties. I wouldn't be surprised if it gives no quarter to the most current version of Atok, either.

      So if you want to sell software for Linux, you're far better off with some server-side application that does one or both of the following:

      -Occupies a niche significantly held by proprietary software, even on Linux
      -Doesn't occupy such a niche, but blows away every other product available, Free or not

      Even then, you'd be constantly looking over your shoulder at the cloners. The landscape is littered with proprietary software for Linux, much of it later becoming a success under the GPL after failing as a proprietary product. If you want to sell software, by all means develop for OS X. I would. It's just too hard to make a sale to Linux users.

    93. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      B.U.L.L.S.H.I.T. Commercial, non-GPL licensed Qt can be purchased from TrollTech. You're right that if someone wants to use BSD-licensed, Qt-based code in a closed-source project cannot use GPL licensed Qt. But they can purchase a closed-source license for Qt.

    94. Re:Client vs. Server Applications by fyngyrz · · Score: 1
      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.

      So... are you saying it's OK to lock out two guys in a basement?

      My point was that "little" meant that $6000 meant something to the development budget, and that isn't necessarily something that goes by employee count. If the budget is fixed and not very large, then six grand might be a deal breaker. If the "company" is a person is doing something in the evening after work, and getting six grand means no rent money, which is certainly a common scenario, then again we have a deal breaker. The presumption that six grand means nothing is meaningless, really, because the range of contexts varies all over the map. Which was my point. If you're at the moneyed end of the map, or have total control and six grand to spare, then you're golden, as long as the lawyers approve of it, of course. If you're some guy trying to get free of the mouse wheel, you may be in deep trouble and that was really who I was hand-waving about when I made the remark about this model favoring both ends, but not the "small guy."

      --
      I've fallen off your lawn, and I can't get up.
    95. Re:Client vs. Server Applications by gig · · Score: 0, Flamebait

      > Also, if you do your program right, you shouldn't need a lot of UI developers.

      Is this how Linux apps are made? Go figure.

      The killer app for Linux on the desktop is obviously going to be a GPL license arbitrator.

    96. Re:Client vs. Server Applications by KiloByte · · Score: 1

      Lazarus is as close to Delphi-for-Linux as you'll get. It uses GTK 1.2 in Linux though. (2.x is still a bit unstable.)
      GTK 2.x: s/a bit unstable/totally unusable/. For basically any purpose, you need to stick with GTK 1.2, which isn't there anymore on most systems.

      And in general, Lazarus isn't there yet. It can do very simple things at most (with executables starting at 7MB), but for anything non-trivial, forget it. And its development seems to be totally stalled. A pity that, considering the amount of Delphi code in existence, it would be a great thing.

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    97. Re:Client vs. Server Applications by nighty5 · · Score: 1

      This is complete and utter FUD.

      Say its $3k without explaining anything is just adding fuel to the fire.

      Most people may not know this, but if you are a small business, you can get a 65% reduction in the price of QT.

      http://trolltech.com/products/qt/licenses/licensin g/smallbusiness

      This is a HUGE discount, you must earn under 200k per year to get that, and for most small businesses that is easy to do. If you are earning more than that then sure you can should pay for the license to reap the benefits because you should be able to afford it.

      I've thrown out GTK, wxwigets because its just not there in terms of a consistant approach to GUI programming, vast amount of excellent libraries etc.

      I'd prefer to *pay* for licenses for a decent toolkit if it will reap benefits.

    98. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      Don't f*king use Windows then. It's 2007 already. Not 1989.

    99. 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
    100. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      No, it really isn't. LGPL [gnu.org] 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.

      Dynamic linking was invented years ago. Even Windows has it, they call them DLL files.

      Look at the good old Loki-games. All of them used SDL, and SDL is under LGPL. The game binary itself is simply dynamic linked against the SDL library, which is installed in the same directory as the game itself. For those of us who wanted it to use a newer version (the old versions had some problems), simply deleting libSDL.so from the game directory makes the game use the system one instead.

    101. Re:Client vs. Server Applications by Fred_A · · Score: 1

      That's funny, all the good commercial apps I've used for Linux use motif or lesstif.
      That's funny, all the good commercial apps I've used for Linux used QT. Which only goes to show that YMMV...
      --

      May contain traces of nut.
      Made from the freshest electrons.
    102. Re:Client vs. Server Applications by Bert64 · · Score: 1

      It's all about numbers...
      People don't just create opensource software for fun, they do it for a reason... That reason could be because their company derives money from selling support contracts or selling hardware (IBM, Sun), or it could be because they want/need to use the software themselves.
      Mass market software has more users, so more potential support contracts and more chance that some of those users will be competent coders.
      Niche market open source only really works where the niche is a technical one (like development tools, compilers etc) and the people in that niche are competent coders.

      To give a counter example that i encountered recently, a cricket scoring program, i doubt there are too many people who both play cricket and know how to code.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    103. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      In other news, the number of Windows developers tripled in India in the same time period.

    104. Re:Client vs. Server Applications by MysteriousPreacher · · Score: 1

      A survey of the feelings of two people is certainly enough to convince me. Windows here I come!

      --
      -- Using the preview button since 2005
    105. Re:Client vs. Server Applications by richlv · · Score: 1

      Linux's GUI development environment favors free at the one end, and deep-pocket folk at the other, while locking out the small guys. Seems... I dunno, sort of un-linuxy.

      first, this is only one toolkit. yeah, probably the best, but not the only one.

      second, what's so un-linuxy ? would gpl-only be better for you, like linux (the kernel) itself is ?
      --
      Rich
    106. Re:Client vs. Server Applications by QuestorTapes · · Score: 1

      > 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.

      It might also be affected by a higher percentage of server-side code being developed in general. I develop a lot on Windows, and probably the majority of the code I've written over the last few years is server-side.

      Especially as more corporate apps move to web-based interfaces.

    107. Re:Client vs. Server Applications by marcosdumay · · Score: 1

      "...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."

      There are people around here really unable to read a lincese, or refer to FSF to get an explanation... Or that like to spread FUD.

      Look, it is not that hard to dynamic link to a library. It is also not that hard to check if the library is already there when installing your software.

      But if you don't think so, there are other options (see, the license says "one of the following", that means any one) you can simply enable the user to change the library, altough it is less desirable, and will make your customer think that using the system library is too hard for you.

      Also, it is Linux, you can ask the package manager to make sure the library is installed, but for that you'll need to package your software (maybe that is too hard too).

      "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.)"

      Oh, I see... Your legal team won't revise the Windows's EULA (all the hundreds of them)... Or the developer kit's EULA, or the MFC EULA... But will teake eons to read the LGPL.

    108. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      *vomit*
      You owe me a pizza.

    109. Re:Client vs. Server Applications by macurmudgeon · · Score: 1

      A development grade Mac costs slightly less than an equivalent Dell.

    110. Re:Client vs. Server Applications by richlv · · Score: 1
      currenlty kde conference, akademy is in progress.
      of course, trolltech is present there, and from the reports, they are interested in being more open and collaborative with opensource developers :

      The Trolls realize they need to cooperate more, and thus are trying to pursue the common interests. By introducing developer blogs, releasing early snapshots and having a community manager, they hope to increase communication with the community and encourage contributions. Until now, KDE developers often worked around limitations in Qt, but in the future they could send patches.

      http://dot.kde.org/1183385741/

      i guess they might be interested in hearing what problems/regressions you are facing.
      --
      Rich
    111. Re:Client vs. Server Applications by julesh · · Score: 1

      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...

      Except that they *can* buy a commercial license for QT, which makes everything legal. It does work, kind-of...

    112. Re:Client vs. Server Applications by julesh · · Score: 1

      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.

      1. Section 4d (0) doesn't require source code, it requires something that can be relinked. This could be a '.o' file produced by linking together all of your source code and stripping internal symbols, if you wish.

      2. 4d (1) doesn't mean what you think it means, either. The word "already" applies "at run time", which means that it is fine for your program to be executed by a wrapper program that checks for the presence of the library and installs it if it is not already present. The program then starts running, and finds the library "already" present, and links to it.

    113. Re:Client vs. Server Applications by fyngyrz · · Score: 1

      I think you may have misunderstood me. I have no problem with Trolltech's pricing. You found a niche, and you're filling it, and more power to you.

      What I have an issue with is linux itself not having a standard GUI layer, as does OSX and windows, so that applications may be written by anyone from the smallest to the largest without concern for licensing, funding, or availability by platform. This is something for the linux core developers to address.

      That still leaves room for Qt; all you have to do is outperform the OS solution, and/or offer feature sets (like cross-platform compatibility, better, and/or more interesting widgets, ease of use for developers, interface builders... I'm sure you know this list a lot better than I do) and market your advantages, whatever they are, effectively. Like any other business. Nothing wrong with competition; it makes things better.

      I liken it to a situation as if linux had no networking, and the only ways to add networking either (a) cost money, (b) required adherence to the open source philosophy a'la the GPL and LGPL, or (c) excluded commercial use. That'd really put an arrow in the heart of linux being used as a server platform. But that's not the case, and linux is either the best, or one of the best, server platforms out there.

      However, this is precisely the situation that is extant with regard to GUI, and linux is far, far behind when it comes to the number of GUI-centric applications. Without pointing at any specific application, I can think of some that are way, way below the top performers in the field that linux users repeatedly hail as "great" and "good enough" to not require the top performers to pay attention... when the fact is, if those applications arrived on the platform it would be a great day for everyone, except perhaps the developers of the sub-standard apps already here. I think that the two facts - no standard GUI layer and almost no major commercial GUI apps - are inextricably related, and something that, should the lack be addressed, have the potential to cause a surge of applications to arrive on the machine.

      Many of the tools I think would arrive would be closed, commercial applications. This would likely aggravate some people. It would also cause others to say "I think we can use this platform." None of which poses an actual problem for linux folks, unless they consider the commercial people competition. Me, I think competition is a good thing, so I'm rather deaf to those complaints.

      --
      I've fallen off your lawn, and I can't get up.
    114. Re:Client vs. Server Applications by Blakey+Rat · · Score: 1

      Wow, are you seriously that self-delusional? You honestly think a 16x16 pixel mouse cursor is good enough on a 1680x1050 17" display? (Oh sure you can zoom in on it, but it doesn't do any smoothing so you end up with a hideous pixilated cursor.)

      OS X badly, badly needs resolution independence. And unlike Windows and Linux, there's no way to manually change the DPI or fontsize for most text.

    115. Re:Client vs. Server Applications by Blakey+Rat · · Score: 1

      Or if you don't mind using a VB-alike language, you can license RealBasic which supports the same three platforms for, what, $550 a developer now?

    116. Re:Client vs. Server Applications by aichpvee · · Score: 1

      Well, naturally. Qt (note the proper case, btw) is great. I guess if you count Opera as "commercial" I wouldn't say all of the good ones used motif/lesstif. But I wouldn't say it's commercial so much as just proprietary. But I guess that point could be argued.

      What Qt apps are you running?

      --
      The Farewell Tour II
    117. Re:Client vs. Server Applications by LWATCDR · · Score: 1

      Then Use GTK and consider it your standard GUI layer. It is really that simple. QT is really the best solution for multi-platform. GTK is a very good took kit.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    118. Re:Client vs. Server Applications by LWATCDR · · Score: 1

      That small business program is really nice. BTW just one suggestion. How about letting people "develop" with the GPL version and pay for the the commercial version for the release. The current restrictions are at best unenforceable. My company paid for the licenses because it just wasn't worth the risk to us and the cost was low enough.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    119. Re:Client vs. Server Applications by TheSunborn · · Score: 1

      Windows got win32, mfc, and .net. 3 different systems*. And to make matters worse, most applications actuelly make their own system/widgets using win32 as a base. Example: When you click the right mousebutton, will the context menu come when you press the press the button down, or when you release it? That really depend on which application you use.
      And how does windows programs draw the menu at the top of the application? Last time i checked it, there were 5 different looks for the menu, depending on application.
      I mean, just try to look at Internet explorer, outlook 2003, and outlook express. They don't look the same at all.

      And mac Os X still got bot Carbon and Cocooa.

      *Mfc is really a wrapper around win32, but it also adds its own widgets, and change the way programs behave.

      And me: I always use QT4 when i write windows applications, because it is so much better then win32 and mfc.

    120. Re:Client vs. Server Applications by Fred_A · · Score: 1

      I'm running Bibble Pro and Antidote. Both commercial and proprietary, but certainly commercial (even available as boxed sets I think).

      --

      May contain traces of nut.
      Made from the freshest electrons.
    121. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      No you're the fucking moron, haha! Don't tell people they're spastic or
      to blow you when you're the retard.

      You're wrong, plain and simple.

    122. Re:Client vs. Server Applications by __aamnbm3774 · · Score: 0

      You are just another blind /. 'Microsoft-Hater', and regardless of truth you will continue to believe your point is correct.

      Even if some developers are migrating to the Mac/Java/Linux environments, it still doesn't disprove anything that I've said. .Net 3.5 will certainly recoup some of the percentage lost in this crappy report. (if it is even accurate to begin with)

      P.S. You better reply quickly before the school bus comes.

    123. Re:Client vs. Server Applications by ncc74656 · · Score: 1

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

      Is wxWidgets portable enough for you? You can even set up Linux to cross-compile for Windows (maybe Mac OS X as well; I haven't tried yet) and create apps for both with native look & feel with a free-as-in-speech toolchain and desktop environment.

      I don't know if the OP took that approach or if he's using native tools on each supported platform, but what he described isn't exactly outside the realm of possibility.

      --
      20 January 2017: the End of an Error.
    124. Re:Client vs. Server Applications by ncc74656 · · Score: 1

      I wonder, does Windows really have much tht resembles a "native" UI? I know Java apps stand out like a sore thumb, but then again, so do a lot of supposedly native apps on Windows.

      If you're not abusing the Win32 API to apply some horrid skin to your app, yes. Windows apps I've done with MFC, wxWidgets, or just written directly with the Win32 API all have the same look & feel. If you've worked with MFC, there's surprisingly little that's different about wxWidgets (you need to learn to work with sizers so your app can more easily adjust to different widget sizes on different systems, but most of the other stuff bears a large degree of similarity).

      --
      20 January 2017: the End of an Error.
    125. Re:Client vs. Server Applications by LWATCDR · · Score: 1

      It is just FUD. Linux offers you options for your GUI at every price point from free to expensive. GTK is free and LGPL isn't a big problem for commercial software people unless you modify your GTK lib.
      Windows is a huge mess as anyone that has worked with it knows.
      I can not comment on Mac since I don't code for it.
      I other words it is the same old "Linux sucks because..."
      Now here is an interesting question. Are the "Free widgets" in Microsoft and Mac OSx really free?
      The end user is paying for them just not the developer.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    126. Re:Client vs. Server Applications by Anonymous Coward · · Score: 0

      "I guess it is good that most developers have settled on the Big Two toolkits (GTK and Qt) but I would definitly be nice if there was just one standard."
                *rolls eyes*. Fine. I hearby declare GTK to be standard. Even though any distro has both.

  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.
    2. Re:Perhaps Its just gotten easier.. by cromar · · Score: 1

      I agree, it doesn't necessarily mean the market is drying up. I program ASP.NET because that's the work I can find, not because I wouldn't rather be programming for Linux or Mac or BSD or anything besides &*@#ing Windows.

    3. Re:Perhaps Its just gotten easier.. by Anonymous Coward · · Score: 0

      Then make yourself a job.

      Seriously. I got laid off in May. I took my severance, started living... frugally, and started writing a domain specific application. It's about 60% done now, and I already have a company interested in licensing it. Let's just say that if the deal works out, I will have made about $20,000/month since I lost my job.

    4. Re:Perhaps Its just gotten easier.. by Anonymous Coward · · Score: 0

      Dude! Are you hiring?

    5. Re:Perhaps Its just gotten easier.. by Anonymous Coward · · Score: 0

      Heh, not in the foreseeable future.

    6. Re:Perhaps Its just gotten easier.. by Anonymous Coward · · Score: 0

      Windows has some of the best tools out there...
      ... and some of the worst documentation.
    7. Re:Perhaps Its just gotten easier.. by Anonymous Coward · · Score: 0

      I work in an environment with both ... .NET and Java Wow, I don't know which one makes me feel worse for you.
      My condolences.
    8. Re:Perhaps Its just gotten easier.. by Billly+Gates · · Score: 1

      I think he is referring to RAD tools for desktop driven database apps or something. Or perhaps writing quick and dirty intranet apps. Writing gui code by hand before Java and .net/vb was painful with C++ on windows or X.

  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 ranton · · Score: 0

      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). I have never dealt with such an easy to use development environment than the one Microsoft has in Visual Studio. Granted they stole and borrowed most of their best features from Borland, but the end result is still the best development studio I have ever used.

      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. Or at least I have never seen any. RealBasic is the closest I have found, but it is more like going back to VB6 instead of using the newest advances in development user interfaes and other features.

      I cannot wait for a language that is as cross-platform friendly as RealBasic but also as feature rich as Visual Studio. I am certain that it will happen someday, and it will certainly be a major blow to Microsoft.

      I think both Linux and OS X are great operating systems, but my advice to anyone is still to be wary of getting a computer that alot of software will not run on. Even if you arent using anything other than Word Processing and Email today, what about three years from now? Once cross-platform programming is easier things might change (and hopefully will).

      --

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
    2. Re:Linux is not another Windows by Anon-Admin · · Score: 1

      what about three years from now?

      Ummm, you buy a new computer..... How many people use 3 year old PC's, and the more the price falls the more people will replace them.

    3. Re:Linux is not another Windows by Anonymous Coward · · Score: 1, Funny

      VisualWorks Smalltalk. More powerful IDE than Visual Studio and cross platform across windows, linux, unix, mac, etc..etc..

      Last time I used VisualStudio (2 years ago) my thought was "not bad, they're finally up to mid 90s Smalltalk standards for IDE productivity"

    4. Re:Linux is not another Windows by Applekid · · Score: 1

      A) Lots of people use 3 year old PCs. I had a favor called in just the other day to repair an old Pentium-II system.

      B) I think GP was referring to the applications one uses 3 years from now. Today someone might be using word processing and email, while 10 years ago they might just be using word processing. I think it's possible that a next Killer App can come out within 3 years... all it takes is a great idea. And if cross-platform tools are good enough, that Killer App would be truly OS agnostic.

      --
      More Twoson than Cupertino
    5. 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
    6. 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.

    7. 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.
    8. Re:Linux is not another Windows by Breakfast+Pants · · Score: 1

      So the answer is buy a pentium II now, and a new computer 3 years from now.

      --

      --

      WHO ATE MY BREAKFAST PANTS?
    9. 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.

    10. Re:Linux is not another Windows by kurokaze · · Score: 1

      From my experience, Eclipse is just too slow (responsive-wise) for me to work on. I don't know if it was my machine at work (3Ghz P4 - 1GB RAM), but it took Eclipse forever to load, and even after that the menus were very sluggish.

      Now admittedly, VS2005 isn't a heck of alot better in the startup, pretty much thanks to the useless Start Page, but the rest of the UI feels are more responsive than Eclipse ever did.

      Heck, if I could get full .Net support in VS 6.0, I'd stick with that.

    11. 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.
    12. 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.
    13. Re:Linux is not another Windows by Lockejaw · · Score: 1

      Getting GCC installed is a matter of installing the Xcode Tools.
      I'm pretty sure gcc is still included if you don't check the "Developer Tools" box at installation.
      --
      (IANAL)
    14. Re:Linux is not another Windows by immcintosh · · Score: 1

      You might look into the Mono project. Doesn't yet support all the bells and whistles that you get in Microsoft's latest .NET, but I've found for most reasonable projects you can get it running in both Linux and Windows using almost identical code. If you want to do your programming in Linux, MonoDevelop is a pretty decent tool for the job. I'll admit I haven't done much, but with the few projects I've made for myself using it the experience has been quite peasant and very Visual Studioish.

    15. Re:Linux is not another Windows by ranton · · Score: 1

      Excuse me for being naive, but why not Java?

      I guess I have always assumed that Java does not have a rich set of components like C# does. I have looked into 3rd party Java components such as JSuite 7.2 from Infragistics, but none that I have found even touched the .Net equivelants (even from within the same company).

      The best feature of Visual Studio .Net is not really its user interface alone, it is all of the 3rd party support. Having controls that do 80% of the programming for me helps my company finish software faster.

      But I have never really looked into doing Desktop programming with Java. How do the built-in components and 3rd party components in modern Java compare to Visual Studio .Net?

      --

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
    16. Re:Linux is not another Windows by ranton · · Score: 1

      It isnt just the Visual Studio 2005 IDE. It is all of the components, both built-in and 3rd party, that make it so great. I have components from Infragistics that cut out over half of my development time by automatings most of the programming I would have had to do.

      Its just like the cotton gin, just for a different age. I have never worked with anything in OS X or Linux that is easier to use than .NET. And easy to use is ALMOST always more important than more powerful. If it helps get the product finished quicker then you make more money. And when performance is an issue, you have more time to fix the bottlenecks if the other less demanding areas of your project were finished quicker by an easier development environment.

      --

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
    17. Re:Linux is not another Windows by Actually,+I+do+RTFA · · Score: 1

      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.

      Sorry to burst your bubble, but that's not how businesses work. If the cost of writing software that works on Linux/OSX is higher than the possible profit, no one will do it. Because, userbase is nothing, dollars are everthing. But more specifically, if I can write 5 programs that target 85%(?) of users in the same time you can write 4 programs that target 100% of users, I win (assuming all programs are bought by the same % of users.)

      All my development work is Windows-only because I don't have the time to learn another way of doing things, and being locked into Windows/DirectX makes it too damn convinent to change.

      --
      Your ad here. Ask me how!
    18. Re:Linux is not another Windows by ranton · · Score: 1

      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.

      That is rarely true, which is why so much software only works for Windows. Commercial software houses want to sell as much software as possible. If it takes 2 years to develop a Windows program that can sell 2000 copies, and an extra year to port it to OS X & Linux to sell another 350 copies (Windows had about 85% client-side market share in 2004), there is almost no point to porting the software. They could just spend that year working on their next Windows project which will make them three times as much money.

      My company sells about 80 copies of our small niche software per month. By porting it to OS X & Linux we might sell another 10 copies per month. And it would probably be alot less than that, because many of the Linux/Mac users out there also have access to the Windows operating system too. So we can either possibly increase our sales by about 10%, or work on a new peice of software that could possibly double our sales (if it is as successful as the first). It seams like a no-brainer to me.

      Large development companies of course port their software to at least OS X, but there is alot of useful small niche software out there. And it would generally be a bad idea for most of them to spend too much time worrying out cross-platform programming when the tools to write Windows software are so much easier to use. (I am including Visual Studio, .Net, 3rd party components, etc.)

      --

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
    19. Re:Linux is not another Windows by XedLightParticle · · Score: 1

      This one is simple; because Java is not.

      While I've generally been able to adopt just about any other language over a weekend, Java seems to be my everest. Perl has CPAN and languages like Delphi and C# have (perhaps excessive) frameworks/repositories following them, Java can do just about nothing on its own, if I want to develop a GUI application, I'd first need to do some heavy research just to get started, I've heard Swing is the word for GUI, but I have no clue how to get it into my Eclipse, which i think is perhaps the most complete opensource IDE available, but it also seems that there's a million other alternatives, and what's worse, they don't necessarily work alike, there's not really a common codec of how to make GUI, while with mono I can choose GTK# or wx.NET and get going right away because most of the same things are called the same, and the row of order and input/output is almost the same.

      Just a central directory for Java classes, or whatever they're called (just to confuse programmers), like Perl's CPAN, with just basic documentation and a human readable descriptions, would make me reconsider picking up Java, but as it is now, it's a pile of code I have no chance to get a greater picture of.

      --
      If I was as pragmatic and objective as I claim to be, would I be commenting?
    20. Re:Linux is not another Windows by Stamen · · Score: 1

      I think it depends on what kind of development you are talking about. If you're talking about desktop development, then yes if you include 3rd party components, then .net has and advantage because of the huge number of 3rd party vendors.

      If you are talking about large scale (AT&T, Social Security, etc) business logic or database intensive applications, then Java outdoes .net by a mile. .net is immature when it comes to middle tier, message queuing, and other such technologies. Java EE running on big iron rules this space.

      I disagree that .net is "easy". It is easy to do basic stuff, using 3rd party components, and the built in tools and wizards. But it becomes very hard, when you need to move outside what the tools provide; which happens in most applications that are more than trivial. You gain speed in the beginning, only to loose it later as you spend days finding a work-around for some problem.

      Other technologies require a little more up front work to do the basic stuff, but after that are much easier. Microsoft's approach to the problem of complexity has always been the same (not surprising as they are a tool company); they make something complex easy by providing a tool that takes simple input and produces the complex code underneath. I prefer the other approach, which is simply to create new technology that is easy, rather than make a tool that wraps the complexity.

      A great example of this is a DataSet. I have one here, that was created using the tools in Visual Studio. The nice GUI creates a c# class with 50,904 lines of code in it (I'm not even joking). I do admit, that this DataSet probably has 40 tables or so, so it isn't a small one, but wtf? 50k lines of code to define 40 tables; the SQL statements for that would be tiny in comparison. Now you might argue that it doesn't matter because the nice GUI takes care of it; but it does matter. Because in this case, for special reasons, we needed to manually modify this code; as you can imagine that was nightmare. The GUI saved a little bit of time only to waste a ton of time later.

      On the other hand you have something like ActiveRecord in Ruby (Ruby on Rails uses this too). Which is a beautifully simple system for handling database access. They didn't create a tool that hides the complexity of it, they created a new simple system. I don't personally use notepad to write code for it, but it would be easy to do so. Yes, you have to actually learn something, but the something is very simple.

      2 different ways to accomplish the same thing, and after years of experience I don't think Microsoft's solution is the right one.

    21. Re:Linux is not another Windows by MemoryDragon · · Score: 1

      Wrong horse, the most complete oss ide is not eclipse, eclipse is mostly a barebones refactoring tool and editor, and hundreds of plugins of various quality. Netbeans probably is the best all in one oss ide, and also way easier if you want to do swing. As for a central repository, have a look at maven2, this is probably the closest you can get to cpan in the java world... If you want to do serious swing and need a graphical tool it is Netbeans (dunno if VE in eclipse is usable by now)

    22. Re:Linux is not another Windows by ranton · · Score: 1

      If you're talking about desktop development, then yes if you include 3rd party components, then .net has and advantage because of the huge number of 3rd party vendors.

      If you are talking about large scale (AT&T, Social Security, etc) business logic or database intensive applications, then Java outdoes .net by a mile


      I completely agree with both of those statements. But large scale business logic applications are not the ones that are going to affect Window's market share. Desktop Development is what is going to affect Window's market share. Or at least that is my opinion, I make no claims that I am never wrong.

      I disagree that .net is "easy". It is easy to do basic stuff, using 3rd party components, and the built in tools and wizards. But it becomes very hard, when you need to move outside what the tools provide; which happens in most applications that are more than trivial.

      I probably have less experience than you (about 6 years professionally, about 10 more as a young hobbyist) but I have found .Net programming to be easy from start to finish. Of course the beginning is easier, but that can be said for any language. I have found that you can become far more productive by doing things the way that the language developers intend instead of trying to jury rig things.

      As far as DataSets go, 51k lines for 40 tables seams like a bit much (but possible). I have had to handle special cases very often (no project has no "special cases"), and the underlying Designer code is very easy to manage. Editing those many lines of Designer code has been a lot easier than writing it all by hand. Or at least that is what my experience has shown.
      --

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
    23. Re:Linux is not another Windows by ranton · · Score: 1

      Also I just want to say that I agree about the headaches of using DataSets. Years ago I did alot of Access programming and DAO was much easier than these stupid DataSets. I am very proficient with DataSets now, but I still do not think that I am more productive than I was with good old DAO.

      But on the other hand the new advanced in DataGrid components has definetely made me more productive. I doubt that they needed DataSets to improve their DataGrids and DataBinding in general, but I have found that for every crappy new feature in Visual Studio there are a dozen great improvements.

      --

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
    24. Re:Linux is not another Windows by Anonymous Coward · · Score: 0

      That is not a great example. It does not represent the other tools in a fair way, because it is incredibly worse than any other tool. It is like judging the average temperature of the planet by refering to the core temperature.

      Typed DataSets are just horrible.

      You have three choices:
      1. Trash the designer created code and use one of the very good ORM tools if you realy want to use objects
      2. Trash the designer created code and stick to simple DataSets
      3. Trash the designer created code and wait for C# 3.0 (maybe the other way around...)

      This "tool" is realy the worst I have ever seen. It does not wrap complexity. It wraps simple things in a horribly bloated way.

    25. Re:Linux is not another Windows by Blakey+Rat · · Score: 1

      Java is fine for CLI/Server apps, but for desktop apps it doesn't have a native look-and-feel on any platform, and it lacks integration with the OS.

      I'm an OS X user, and on my computer Java apps can't use the built-in spellchecker, they can't use the Services menu, they can't interop with other applications using AppleEvents/AppleScript, the user can't drag&drop objects into or out of the application, etc. There are tons of shortcomings to GUI Java apps.

      That aside, the "flagship" Java apps at the moment appear to be Limewire and Azureus. Both have overly complex hard-to-use GUIs and flaky behavior. (Not redrawing parts of the window correctly, opening windows in strange places and not where you expect, opening dialogs on a different monitor from the main app, etc.) If there were a few better examples of truly great Java apps out there, I'd probably be more able to recommend it.

      (And notice I didn't even mention that they're molasses-slow.)

    26. 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.
    27. Re:Linux is not another Windows by bladesjester · · Score: 1

      I started out consulting in java. Making GUIs gave me a headache. It's not that java is a bad language, it's just that I hate having to spend 80% of my time nudging interface componants around in code until I finally get it to look right.

      Now I use C# in visual studio. Being able to lay out the user interface graphically without having to jump through hoops is such a very nice thing.

      --
      Everything I need to know I learned by killing smart people and eating their brains.
    28. Re:Linux is not another Windows by poopdeville · · Score: 1

      That is rarely true, which is why so much software only works for Windows. Commercial software houses want to sell as much software as possible. If it takes 2 years to develop a Windows program that can sell 2000 copies, and an extra year to port it to OS X & Linux to sell another 350 copies (Windows had about 85% client-side market share in 2004), there is almost no point to porting the software. They could just spend that year working on their next Windows project which will make them three times as much money.

      I expressed myself poorly, but this was part of my point. Windows doesn't include tools to create cross-platform applications (except for Java, but *gross*), so to target the largest userbase, they must target Windows, usually to the exclusion of other platforms.

      --
      After all, I am strangely colored.
    29. Re:Linux is not another Windows by misleb · · Score: 1

      IMHO, Windows will only lose its dominance when cross platform development tools become as easy to use and feature rich as Visual Studio.


      What is it with this slashdot obsession with "cross platform?" I don't use Linux or OS X so that I can run apps that have been dumbed down to the point where they work the same on every platform. I want applications to be as unique to the platform I chose (therefore taking advantage of its strengths) as possible. I LIKE Cooca apps, damn it! If I didn't, I probably wouldn't be using OS X. I despise Java GUI apps.

      What we need are standardized protocols and file formats through which my Cocoa apps can communicate with your GNOME apps effectively.

      But yes, i agree, the development tools for other OS's need to get up to par with the Microsoft tools. Apple's tools aren't bad... if you don't mind picking up Objective-C...

      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. Or at least I have never seen any. RealBasic is the closest I have found, but it is more like going back to VB6 instead of using the newest advances in development user interfaes and other features.


      IMO, there's nothing wrong with targeting specific OS. There are enough developers to go around... given the proper tools, as you mention.

      I cannot wait for a language that is as cross-platform friendly as RealBasic but also as feature rich as Visual Studio. I am certain that it will happen someday, and it will certainly be a major blow to Microsoft.


      If I am not mistaken, .NET allows you to utilize multiple languages in one application. If you structure your applications right (MVC), you coudl write all your business logic in, say, C++ and then just write the interface for each platform in whatever language is most appropriate.

      As a user, I have absolutely no desire to see some uber-language dominate things and limit all application functionality to the lowest common denomonator among platforms. For example, I don't want my desktop app limited in some way because certain features were difficult to implement on, say, mobile devices. I prefer developers that can focus on a particular platforms and cater to it. If that means a limited selection of software, then so be it. It is much better than the alternative.

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    30. 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.

    31. Re:Linux is not another Windows by poopdeville · · Score: 1

      Why is everybody reading this so uncharitably?

      In context it's pretty clear that I mean that development tools for a particular platform don't really affect which platform is most lucrative from a business point of view. Context makes this especially clear since I continued to discuss how Windows doesn't include any good cross-platform development tools, or (outside of Java) language runtimes.

      I bet you stopped reading after the first sentence.

      --
      After all, I am strangely colored.
    32. Re:Linux is not another Windows by Anonymous Coward · · Score: 0

      My old job we were using a public facing webserver running on a K6-2 300 in 2006. And it was running just fine for our needs.

    33. Re:Linux is not another Windows by gabrieltss · · Score: 1

      How many people use 3 year old PC's

      Um, I'm typing this on a PC I built 8 years ago - It's a dual PIII 850 with 1 GIG ram. A little old yes, but not as old as my Amiga 2000 I have sitting on a desk behind this PC.
      I did just purchase hardware to build a newer PC (dual AMD Operteron 2.2ghz 24 gig ram). But, I don't but a new PC every 3 years. I build one that will last me 8 years and I'll spend less money than someone who has to have the latest and greatest piece of hardware. I just upgrade hard drives and cd/dvd burners that's it.

      --
      The Truth is a Virus!!!
    34. Re:Linux is not another Windows by Actually,+I+do+RTFA · · Score: 1

      I read the whole post before replying. Before writing this, I read it again.

      The first point you make is just wrong. Speed of development is an important consideration. If you could write with Notepad and get only a slight userbase advantage, it's not worth it. Never underestimate what businesses are willing to sacrifice as far as features/market in a shortsighted effort to cut costs.

      The last point you made is that it is harder to deploy to Windows because Java is the only cross-platform language. Three things. First, Windows is very easy to deploy to. All you have to do is write the software natively. The problem is when you try to port it to *nix. Second, you left Flash out. I've produced some desktop applications in Flash, and it runs very well, even though the code is extremely hard to read/maintain. Third is that I question the non-development costs associated with Java on Windows. I don't think I've ever seen a Java program where a superior version wasn't compiled as a Windows binary. For some reason, the GUI just feels more responsive.

      --
      Your ad here. Ask me how!
    35. Re:Linux is not another Windows by Max+Littlemore · · Score: 1

      How do the built-in components and 3rd party components in modern Java compare to Visual Studio .Net?

      I'll start by saying up front that my last exposure to a .Net project was a couple of years ago.

      .Net controls are great if you have a standard task to perform and you're doing it exactly as the developers intended, but as soon as you deviate from their path, you're in for a world of pain and sometimes deviation from the path is necessary because of a requirement the third party, or in some cases Microsoft, didn't envision. This leads you down the slippery slope to workaround hell.

      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. When including all third party apps and across all devices, I find the Java platform a bit more powerful as a whole, although for some specific applications, I'd certainly recommend .Net.

      High mouse mileage, or high mouse hand mileage from switching between keyoard and mouse, is something that really irks me so the whole "control" thing sucks for me. When I work with VS .Net, I find myself falling into the trap of using the mouse a little too much. I know this is a personal prefenence thing, and that VS can be keyboard driven, but that's how it occurs for me.

      If you do like WYSIWYG IDEs and are interested in checking out Java, Oracle JDeveloper is a nice free (as in beer) IDE you can download and play with and I think it's a bit quicker to get productive for new users than Eclipse. Can't hurt expanding your tool set.

      --
      I don't therefore I'm not.
    36. Re:Linux is not another Windows by Max+Littlemore · · Score: 1

      I've heard Swing is the word for GUI, but I have no clue how to get it into my Eclipse

      Eclipse is a bitch when it comes to Swing development. At the moment you really need to be comfortable with hand coding your UI and reading a crap load of javadoc and tutorials.

      You could try NetBeans, but last time I used it, it wrote code that it wouldn't let you hand edit, so you have to do everything through the IDE. This can get annoying if you want to quickly hand edit something.

      I recommend Oracle JDeveloper for getting started with Swing. It has a nice visual designer, it's quick to get started and it's free to download and use.

      --
      I don't therefore I'm not.
    37. Re:Linux is not another Windows by Anonymous Coward · · Score: 0

      How many people use 3 year old PC's, and the more the price falls the more people will replace them. I suspect lots of people do. Especially people in South America, Eastern Europe, Africa, etc.. Hell, I'm typing this on an 8yr old PC.

      Believe it or not, this PC serves me fine for web, email, mp3, even watching an occasional movie (and pr0n - well, ok - so the pr0n is a bit more than occasional).
    38. 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/

    39. 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.
    40. Re:Linux is not another Windows by aled · · Score: 1

      Limewire and Azureus. Both have overly complex hard-to-use GUIs and flaky behavior. (Not redrawing parts of the window correctly, opening windows in strange places and not where you expect, opening dialogs on a different monitor from the main app, etc.)


      Seems GP don't like SWT either.
      --

      "I think this line is mostly filler"
    41. Re:Linux is not another Windows by quanticle · · Score: 1

      As far as getting swing to work, its just a simple matter of putting "import javax.swing.*;" at the beginning of your class.

      Also, you can configure a central directory for your 3rd party classes by setting up the CLASSPATH variable in your OS.

      And, as far as simplicity goes, I've found that the complexity of Java and .Net to be similar. Its just that you may be more familiar looking around MSDN rather than Sun's own Javadoc. Frankly, both Java and .Net are large, complex, enterprise grade programming platforms, and are usually overkill for smaller, one-off projects.

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

      Java is fine for CLI/Server apps, but for desktop apps it doesn't have a native look-and-feel on any platform, and it lacks integration with the OS.

      That is a concern I'm willing to acknowledge. Desktop Java apps often look jarringly dissimilar from the native OS look & feel.

      (And notice I didn't even mention that they're molasses-slow.)

      1999 called, and they want their Java criticism back. Besides, its not like C# will be any faster. Both C# and Java are JIT compiled languages that are run inside a virtual machine (JVM for Java vs. .Net CLR for C#).

      --
      We all know what to do, but we don't know how to get re-elected once we have done it
    43. 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.

    44. Re:Linux is not another Windows by jnnnnn · · Score: 1

      You, sir, sound like a psychohistorian!

      Good work.

    45. Re:Linux is not another Windows by gig · · Score: 1

      > I think it's possible that a next Killer App can come out within 3 years

      Web 2.0 on billions of mobiles, dwarfing the personal computer installed base ... I think that is the most significant thing right now and for the next few years. By 2010, PC's may be the minority of Google's clients.

      There was a few years there where we all played MP3's on our computers. During that time we may have been tempted to imagine every CD player in the world being replaced by a PC (Bill Gates certainly did). However what happened is the CD players were replaced by iPods, both portable and home CD players. The Web is the same, it is stuck on the PC only temporarily. Both Apple and Nokia have mobile Web browsers based on WebKit, which is full-spec, it even has CSS3. Internet Explorer will be a minority browser in no time and it is stuck on the PC. Most Web users will be on mobiles soon and from then on.

      Steve Jobs already confirmed the next iPod video runs OS X. Probably has Safari and Wi-Fi also. Half an iPhone for $349 with the flash replaced by disk.

      > cross-platform

      If you do one Web-native GUI you can run it on the Web as well as use it for the UI for your native apps. So your app can run on Mac, Windows, Linux, and Web 2.0. I say Web 2.0 because you want CSS3 for sure, with its shadows and rounded boxes and inset text, you can do the entire iTunes UI in HTML5+JS+CSS3.

      > GTK and QT

      This is all going away in favor of HTML5, JS, CSS3 even on native apps. The apps you see coming out of these toolkits look like 1988's ass. Maybe if you are making a disk utility or something, but even then some art or animation can be amazingly useful.

      To see the future, look at Adobe Lightroom, which although the UI is in Lua it is still entirely scripted. They were able to make massive UI changes from beta to beta based on feedback in very short time, they were able to include tons of artwork for a very distinctive and functional custom interface where the photos always seem to be real objects, and the same interface runs on both Mac and Windows in exactly the same way (and wherever else they take it). Also, the artists and UI people worked on the art and UI while the coders worked on code, it was separate just like how we do it on the Web.

      QT has an imitation Mac GUI that even Apple doesn't use anymore. You are much better off giving your app its own distinctive, custom, media-rich UI.

      Years ago on the Mac, every application had the same icon, an offset square that meant "application". Now we would laugh at the idea of not putting your own custom icon on your app after you did all the coding and libraries and design and QA and all of that. The same applies to your entire UI. The window your app is running in can be iconic also. That's the face of your app and also all of its controls.

      You can prototype the UI in a browser so quickly, refine it until everyone on the team feels like that is the 2.0 interface right there, that is speaking to us all. You can skip thousands of lines of code that way by not writing any until the UI is essentially done.

      Also, let's say you make an app with QT and it does the same things on Mac, Windows, Linux, but in each place it looks different. To many Slashdot readers, that is the same app. To the other 98% of humans, different app. Same as how the antique Web rendering on non-Apple mobiles is only considered to be the Web by a small cadre of technical users. To most people, it ain't the Web if you don't have what the iPhone has. You are better to give your user one app and one UI that works the same on every platform and then if they buy a Mac or Windows or Linux they can still work in e.g. Lightroom at full productivity. Also, you are not constrained by poor UI decisions that one platform makes, you customize what you're doing to the needs of your app.

      The best part of this is that the core operating system recedes behind your app's interface. Whatever it is under there, your code uses it, but the user a

    46. Re:Linux is not another Windows by flukus · · Score: 1

      "real men don't use IDE"

      I never said anything like that. I generally wouldn't be without an IDE, the one I use at work at the moment is visual studio.

      There is a big difference between using an IDE and relying on it though. And if you've programmed much you've probably run into the type of idiot that can't "code" anything if theres no a wizard to let them do it.

      The GP seems to be the type that needs instant gratification like perl for scripts and a gui designer. And hes saying java doesn't have an extensive class library (most people complain it's too bloated).

      "Just a central directory for Java classes, or whatever they're called (just to confuse programmers)"

      He can't read documentation and doesn't understand the concept of classes. So of course hes not going to read documentation. He'll most probably end up in a vb sjop.

    47. Re:Linux is not another Windows by bdjacobson · · Score: 1

      > 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). ? W2k is still supported, and will be until July 13, 2010. XP is going to be supported until 2014. You can Wiki it and I think it links to MS's page about their support. If not just go directly to MS, it's somewhere on their website.

      Just a nitpick.
    48. Re:Linux is not another Windows by MysteriousPreacher · · Score: 1

      Some of the GCC libraries are there, but the GCC package as a whole only comes when you install the developer tools.

      --
      -- Using the preview button since 2005
    49. Re:Linux is not another Windows by Threni · · Score: 1

      > ? W2k is still supported, and will be until July 13, 2010. XP is going to be supported until 2014. You can Wiki it and I think it
      > links to MS's page about their support. If not just go directly to MS, it's somewhere on their website.

      Microsoft can call it "extended support" if they like, but it's not being supported in any meaningful way - ie no Internet Explorer 7, so it's no use for web development unless you want to antagonize 85%+ of the world's internet users.

    50. Re:Linux is not another Windows by julesh · · Score: 1

      Java is fine for CLI/Server apps, but for desktop apps it doesn't have a native look-and-feel on any platform, and it lacks integration with the OS

      (Cough). Have you tried SWT?

    51. 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.

    52. Re:Linux is not another Windows by julesh · · Score: 1

      Something's wrong with your machine. I'm on a 2.7GHz Celeron D / 1GB, and Eclipse is pretty responsive. Startup time is a little slow, at 27s (compared to 8s for VS2005), but responsiveness once the app's loaded is pretty-much flawless.

    53. Re:Linux is not another Windows by Blakey+Rat · · Score: 1

      I honestly have no idea. I'm not a software developer and programs don't generally advertise that they use "SWT." So maybe I've tried it, and maybe I haven't.

      Why don't you link me to a Java program that uses SWT so I can evaluate the quality of the program and answer your question?

    54. Re:Linux is not another Windows by Blakey+Rat · · Score: 1

      1999 called, and they want their Java criticism back. Besides, its not like C# will be any faster. Both C# and Java are JIT compiled languages that are run inside a virtual machine (JVM for Java vs. .Net CLR for C#).

      Both Azureus and Limewire, again the two 'flagship' Java apps I've used to a large degree, are much laggier and perform much worse than native applications, at least on OS X. Period. That Java criticism from 1999 still applies today in 2007, and until it's fixed I don't expect that to change.

      What amazes me more is that you don't realize that Java apps perform worse... either it's some kind of self-delusion, or an amazing lack of observational skills. Or maybe they're just bad on OS X and good on every other platform. I dunno.

      C# apps might run inside a virtual machine, but they run quickly inside a virtual machine and it's impossible for the end-user to notice the difference between a native app and a C# app.

    55. Re:Linux is not another Windows by XedLightParticle · · Score: 1

      Well you've got a few points, I hate excessive unordered documentation, I'm no good at reading it from one end to another, so I need to be able to cut to the bone in a matter of minutes. MSDN is very good at that with C#/.NET even though i use mono (mono-doc is also great but of course MS's is more complete). CPAN is also good at cutting to the bone in minutes. I have looked at the Java documentation, so I guess it's basically my inability to navigate it that has made me think otherwise.

      But I'm sorry that I cannot take your "not being a real developer" seriously. An IDE is, as another comment states, a tool of productivity, no company would like to pay for the time I would need to learn it using just a text editor with syntax highlighting, managing makefiles, deployment folders and so on manually. So basically I stick to IDE's whenever it's not prototyping in Perl or Python, or making obscurely optimized code in C, Pascal or ASM, where I need to know exactly what's going on.

      But on the other hand, you're right, I am rather green, I've only got 14 years experience (out of my 25 years long life) in programming just about anything in a number of languages I've lost count of. I have to mention that I haven't been professional for much more that 6 years, the first 8 years I was just curious and had time to learn from scratch.

      btw. Thanks to MemoryDragon, I'll have a look at Netbeans and maven2.

      --
      If I was as pragmatic and objective as I claim to be, would I be commenting?
    56. Re:Linux is not another Windows by julesh · · Score: 1

      The best known example is Eclipse.

    57. Re:Linux is not another Windows by Blakey+Rat · · Score: 1

      I really have no use for an IDE. Is there any actual applications that use it?

    58. Re:Linux is not another Windows by quanticle · · Score: 1

      Both Azureus and Limewire, again the two 'flagship' Java apps I've used to a large degree, are much laggier and perform much worse than native applications, at least on OS X. Period. That Java criticism from 1999 still applies today in 2007, and until it's fixed I don't expect that to change.

      Azureus and Limewire are slow because of Azureus's and Limewire's code, not Java's. You cannot criticize the behavior of an entire programming environment based on the performance of two applications alone.

      Or maybe they're just bad on OS X and good on every other platform.

      I don't own a Mac, so I can't say.

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

      Azureus and Limewire are slow because of Azureus's and Limewire's code, not Java's. You cannot criticize the behavior of an entire programming environment based on the performance of two applications alone.

      So what program should I use to form an opinion with?

    60. Re:Linux is not another Windows by julesh · · Score: 1

      There's a list of a few here.

    61. Re:Linux is not another Windows by Blakey+Rat · · Score: 1

      Oh, well, I've tried Azureus and it's a steaming pile of crap UI-wise. So I guess that settles that: No SWT doesn't change my mind. Also since Azureus was mentioned in my first post, this was all a huge waste of time for everyone involved.

    62. Re:Linux is not another Windows by Anonymous Coward · · Score: 0
      You still don't seem to have made any serious effort to find documentation, let alone read some of it. An aversion to reading is bad in this industry.

      Here you go. Read the overview, and then just look at individual classes when you need to use them.

      And another hint:

      I've heard Swing is the word for GUI, but I have no clue how to get it into my Eclipse
      import javax.swing.*;
    63. Re:Linux is not another Windows by Anonymous Coward · · Score: 0

      Ah, you are describing skins. I hate skins (unless you can "turn them off"). I truly wish all the apps I use tried to stick to established interface conventions (on functionality, layout, appearance) so I wouldn't have to keep guessing what some crackpot designer had in mind. There's eye-candy, and there's productivity.

    64. Re:Linux is not another Windows by Anonymous Coward · · Score: 0

      ??? Swing is included in the JDK. You don't have to search for it... it's there. If you want an easy to use drag and drop development environment for Swing apps use Netbeans (comes with matisse)... doesn't get much easier than that.

    65. Re:Linux is not another Windows by XedLightParticle · · Score: 1

      Alright then, lets compare the Java and .NET Documentations

      First off trying to find the user interface namespaces, we have the two class overviews:
      http://java.sun.com/j2se/1.5.0/docs/api/
      and
      http://msdn2.microsoft.com/en-us/library/d11h6832( VS.71).aspx

      If one have no prior knowledge of any of the two, one would probably probably start off searching for GUI on the page, no result on the .NET reference, and one result in Java: java.awt.dnd

      So, let's go look closer at java.awt.dnd before ruling it out, even tho I can see this is just something drag'n'drop, it may refer to something more useful, who knows? I continue into DragSource, perhaps it can tell me exactly what kind of objects are used for this? From there I find something about a serialized form, being perhaps 30 pages of not so relevant text, and java awt.GraphicsEnvironment, which seems like some sort of rules for a canvas. So I would at this point give up and return to the overview.
      (in fact I would really give up just seeing the description of java.awt.dnd but if i didn't go there in this experiment I'd be accused of not trying hard enough)

      Okay so the next thing so search for on the overviews would be "Graphical User Interface"... alright, same results as with GUI... Then how about "User Interface"? Alright now something happens (and by knowing where I should be going I also know that I am now on the right way). The Java overview gives me java.awt, java.swing.plaf.basic, java.swing.plaf.metal and java.swing.plaf.multi , while the .NET gives me System.ComponentModel.Design, System.Drawing.Design, System.ServiceProcess, System.Web.UI and System.Windows.Forms

      From the descriptions it's difficult to sort out any of the results from the Java reference, while in the .NET it's easy to rule out System.ServiceProcess and System.Web.UI

      Looking a little closer on my findings I rule out whatever says "custom", because noone starts out with GUI by customizing widgets, and the java.swing.plaf.* seems not very useful for my purpose, looking at their content of Interfaces and Classes, however being on the right path it wouldn't take long from there to find the generic swing namespace.

      So the first useful results from the two would be System.Windows.Forms on .NET and java.awk on Java. Keep in mind that a search with no possible matches takes shorter time than those with useless matches, that doesn't reveal that they're useless from the start. Seeing the java.awk as the first useful result, with Java, I would probably go for that one, even though it resembles writing windows applications in C++ using the default Windows API, with lots of work and slow progress. I'm not the impatient kind, but I'm rather sure my employer would like more action for his money.

      So I'll keep my first statement, Java is tricky to learn if you're on your own, with nobody to point out where to look and what to use. It is my experience that the tutorials available for Java starts with "Hello World" in a terminal, then without explaining what happens in between, they jump to some template project where you are just to handle those objects the template has laid out for you. And those covering more advanced projects usually features only code examples of a few useful features, while the text refers to objects like you "of course" have done that before even starting to read. It appears to me as a gap in what's available, the documentation refers to inside understandings, that I can't get without attending courses. This is most likely because Java is what's most commonly used in education to explain OOP, I learned OOP through C++ (which can also be a b*tch to learn from reference) so I don't know all those inside jokes the documentation refers to, there's too much of-course-you-know's as a result of a very widespread use in education, and I don't have 3, 6 or 9 months to learn a language, as I did during my education. To me it just doesn't seem very accessible.

      --
      If I was as pragmatic and objective as I claim to be, would I be commenting?
  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. Hmmm... by El+Lobo · · Score: 0, Troll
    Stop the horses cowboy. The majority of the developers for Linuzzzzzzzzzzzz are writing multiplatform applications. Which of course include Windows. And OsX and whatever.

    --
    It's time to realise that Abble's products are the biggest abomination these days. Just say NO to the dumb iAbble way!!
    1. Re:Hmmm... by Anonymous Coward · · Score: 0

      Have you considered suicide?
      Still better than trolling on ./

      Get some friends.

    2. Re:Hmmm... by perdelucena · · Score: 1

      Troll

    3. Re:Hmmm... by VON-MAN · · Score: 1

      Those developers answered a questionaire, stupid.

  7. basic math by Anonymous Coward · · Score: 0

    A survey this spring of more than 400 developers and IT managers in North America found that the number of developers targeting Windows for their applications declined 12 percent from a year ago. Just 64.8 percent targeted the platform as opposed to 74 percent in 2006.
    64.8%+12%=74% seems to be a decline in calculator programs too.
    1. Re:basic math by Anonymous Coward · · Score: 0

      That's 74%-(100%-12%)=64.8%, Dr. Fermat.

    2. Re:basic math by Bill+Dimm · · Score: 1

      64.8%+12%=74% seems to be a decline in calculator programs too. The 12% decline is a percentage decline in a number that happens to be a percentage, i.e. falling from 74 to 64.8 is a drop of:
          (74 - 64.8) / 74 -> 12.4%
    3. Re:basic math by KarmaMB84 · · Score: 1

      They had 74% then whatever that total was declined by 12%. They didn't lose 12% of ALL developers, only the ones they had.

      1-(.648/.74) ~= .124 or 12.4%

    4. Re:basic math by BlackPignouf · · Score: 1

      Congratulations! I didn't think it could actually be possible to write something worse than your parent.

    5. Re:basic math by Anonymous Coward · · Score: 0

      I'm glad I at least had the foresight to post that anonymously.

    6. Re:Basic Math by Aidtopia · · Score: 1

      Actually going from 11.8% from 8.8% is only a 3% increase, not 34%.

      No, it's a 3 percentage point increase, but that's still an increase of 34%. Suppose the sample size was 1000 developers, then change was from 88 developers to 118. That's a 34% increase.

    7. Re:Basic Math by camh · · Score: 1

      I'm afraid you just failed basic math. What you describe is a three percentage point increase. Consider it this way. There were 88 linux developers, now there are 118 linux developers, which is a 34 percent increase. That applies whether you started with 8.8%, 8.8 people, 88 companies, etc

    8. Re:Basic Math by Quigley · · Score: 1

      The quantity of developers increases by 34%. A percentage is a ratio, so let's multiply by 100 to get pretend quantities:

      8.8 developers + 8.8 developers * 0.34 = 11.8 developers

      The percentage of developers increases by 3%:

      8.8% + 3% = 11.8%

      I think the frame of reference (quantity or percenage) is usually chosen carefully to provide the most (or least, depending on the intent of the article) dramatic effect.

    9. 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.
    10. Re:Basic Math by je+ne+sais+quoi · · Score: 1
      Well I'm going to reply to you since you put the most effort into your response...

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

      That's true, but that's not what TFA said. Here's the quote again in case you missed it the first time I posted it, "The targeting of Linux by developers increased by 34 percent..." It did not say that the number of Linux developers increased by 34%, it said the number of developers. So either the reporter is intentionally misleading the public or can't do basic math. I suspect it's the former, since 34% is much more impressive than 3%.

      P.S. Incidentally, what I have said really is true, regardless of what the slashdot mods seem to think of the situation (if their modding me into oblivion is any indication). And btw, this is not a slight to linux, I run a completely linux and mac shop, it's just a plea for truth in reporting.
      --
      Gentlemen! You can't fight in here, this is the war room!
  8. 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 ThisIsWhyImHot · · Score: 1

      I have to agree with this. Also the article doesn't seem to make a mention of the developers that write software for both platforms by virtualization or not.

    2. Re:Nice but worthless data by cromar · · Score: 1

      If I carefully pick my 400 to survey I could post a completely legit survey showing that OS2 is making a comeback.

      While I agree with your general point, your survey would not be legitimate if that was its finding and sample :)

    3. 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.
    4. 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
    5. Re:Nice but worthless data by harshaw · · Score: 1

      The whole point of modern web apps is doing *real* development with javascript so I wouldn't pass it off so lightly. And I challenge you to really know javascript in 24 hours - perhaps you would like to look at the Mochikit or prototype source code?

    6. Re:Nice but worthless data by burnin1965 · · Score: 1

      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.


      Actually its not necessary to keep the same 400 developers for the survey, in fact the same arguement could be made that keeping the same 400 would squew the results because your not actually sampling the entire population. With a sample size of 400 they likely have a margin of error less than 5% and since the change from one survey to the next is more than 5 percentage points there is a significant difference which suggests there is a change in the number of developers targeting Windows.

      If you pick the 400 respondents then you no longer have a statistically valid survey.
    7. Re:Nice but worthless data by Lockejaw · · Score: 1
      --
      (IANAL)
    8. Re:Nice but worthless data by maxume · · Score: 1

      Of course, if you do it sloppily, your survey isn't legit either.

      --
      Nerd rage is the funniest rage.
    9. Re:Nice but worthless data by swillden · · Score: 1

      Of course, if you do it sloppily, your survey isn't legit either.

      Absolutely. There are many ways to create a meaningless survey. Gathering reliable data is non-trivial.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    10. Re:Nice but worthless data by Anonymous Coward · · Score: 0

      Where the hell did you come up with Javascript d**khead! I believe if you go back and re-read the post it was referring to Java. The two are completely different. Javascript is one step above HTML, but it's a scripting language, not a real OOP language. Java is a full featured language that is capable of programming complete applications and is every bit as capable and fast as C# or VB.NET. Comparing Java to Javascript is like comparing VB to VBScript. Why don't you learn something before making obnoxious postings!

    11. Re:Nice but worthless data by rabidgnat · · Score: 1

      If you pick your x teams so that there are representatives from all of the different categories, you are probably not getting a representative sample. If there are 800 candidate Windows shops, 500 Linux shops, 600 OSX shops, 3 mainframe shops, and two BSD shops, you're probably not getting a representative sample if you guarantee a spot for the BSD and mainframe shops, because picking a random sample is likely to not produce either.

    12. Re:Nice but worthless data by mhall119 · · Score: 1

      They use many statistical algorithms to smooth that out. Believe me, statistics like this go through some pretty complex processes to ensure that they are as accurate at possible.

      --
      http://www.mhall119.com
  9. Probably news for the Linux Cheerleaders but... by Tempest451 · · Score: 1

    This is really just the nature of business. Microsoft probably doesnt see this as a real issue for concern.

    1. Re:Probably news for the Linux Cheerleaders but... by MobyTurbo · · Score: 1

      This is really just the nature of business. Microsoft probably doesnt see this as a real issue for concern.
      If Microsoft isn't concerned about Linux, why did they make a deal with Novell to sell SUSE Linux vouchers and patent indemnification for alleged "250 patent infringements"? They spent several hundred million on the Novell deal, albeit money Novell has to return in a few years once its a shell of its former self. That doesn't sound like the actions of a company unconcerned about its competition. (Which Microsoft scarcely has a history of.)
    2. Re:Probably news for the Linux Cheerleaders but... by Tempest451 · · Score: 1

      If you think Microsoft throwing a few hundred million to tie up loose ends is a sign of Microsoft being concerned about competition, maybe YOU don't know Microsoft's history.

    3. Re:Probably news for the Linux Cheerleaders but... by MobyTurbo · · Score: 1

      maybe YOU don't know Microsoft's history. Yes, you're right, I guess Microsoft isn't that focused towards stomping out competition at all costs. ;-)
  10. 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 MontyApollo · · Score: 1

      I think they said the survey included developers in enterprises and system integrators, but I'm not sure whether it means it was limited to these or not.

      Is there much of a market for Linux apps? I don't know much about Linux, but it seems like all the stuff I have heard of is free.

    2. Re:Linux is a better target for new developers. by jellomizer · · Score: 1

      There is a fair amount of comerical apps too. Most are not targeted toward consumers. Developer Tools, CAD Systems, Version Controls, Databases... They are more for buisness uses, then indivual uses. Linux is still not a consuemer OS it is good for Businesses but not for homes.

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

      It's easier to port from Linux to Windows than from Windows to Linux due to available source code. OpenOffice.org is developed on Solaris and Linux then ported from there to anything else, for example. There are reasonably good Linux distros for home use as well, but I think the main reason for the increase in Linux development is that Cygwin and MSYS will recompile a lot of Linux sources for Windows easily so it's just plain easier to get software to run on Linux first and then port it to other platforms. It doesn't help Microsoft that scripting languages like Python are more cross-platform compliant than C# since .NET has a HUGE runtime library that takes too much time to port.

    4. 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
    5. Re:Linux is a better target for new developers. by egoproxy · · Score: 1

      Windows is satrated with third party apps.
      Yet they have still not embedded a Spelling & Grammar app.
    6. Re:Linux is a better target for new developers. by Blakey+Rat · · Score: 1

      It's countered by two factors:

      1) Development and distribution for Linux are much harder. There are no real killer GUI development tools like Visual Studio or XCode/Interface Builder, and even if there were you'd have a bunch of mostly equivalent but different APIs to choose from. Distributing a commercial non-open source app is a big pain because all the repository systems are designed for open source apps. If you distribute your app on CD, it's likely the installer you write to go with it will do something the repository doesn't know about and hose up the system.

      2) Linux users don't pay for software. If they like the program, someone will just make an open source clone the next day and you'll be out of business again.

  11. 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.

    1. Re:Not suprising... by westlake · · Score: 1
      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

      Win CE is not Microsoft's only entry in the embedded market.

      The embedded market for devices with a GUI has grown rather larger and more complex than that of the PDA. Microsoft Windows Embedded, Windows Automotive

    2. Re:Not suprising... by Anonymous Coward · · Score: 0

      Well if it makes _YOU_ feel better Windows Mobile downgrades the value of the devices its on.
      For instance the Dell axim x51v ... Nice hardware, No functionality at all... And really slow.
      Only intelligent people who have made the mistake of buying a phone/PDA with windows on it KNOW to
      never do it again!

  12. A more meaningful measure? by Snart+Barfunz · · Score: 1

    How about a survey of platforms? I'd like to see a comparison that includes not just the various OSes, but the web. I suspect the web browser/server is the real growth application platform.

    --
    --- Yx3 = Delilah ---
  13. Excellent by theolein · · Score: 1

    it, linux, microsoft, chairthrowing, developersdevelopersdevelopers (tagging beta)

  14. Why target? by kevin_conaway · · Score: 1

    Why target one platform or another except in very specific cases? Use Java, Python or Perl (as a last resort! :)) and make it cross platform.

    1. 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)
    2. Re:Why target? by dctoastman · · Score: 1

      I prefer the more semantic "i += 1;" or actually just "i++;".
      I don't see the benefit in "i = i++;"

      Oh wait, that's post-increment... ... ...

      That's just sick.

    3. Re:Why target? by Blakey+Rat · · Score: 1

      Because I like windows and buttons?

  15. .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.

    1. Re:.net anyone? by cromar · · Score: 0

      As much as I hate to admit it, coding in .NET/C# is surprisingly pleasant. Obviously, it can't and shouldn't replace C/C++ for a lot things, but comparing it to Visual Basic is harsh. C# IS basically Java, while my main dislike of VB.NET is its horrible, overly verbose syntax.

      Anyway there's always Mono...

    2. Re:.net anyone? by ChronosWS · · Score: 1

      Visual Basic does, in fact, run on .Net, so if that is what you mean by drawing closer, then yes. I suspect that is not what you mean however :) Perhaps if you spent actual time writing C# code you'd be able to better understand the differences it has from Java and the benefits it has over C++ and C for those applications to which it is best suited. Having come from a C++/C background myself, I definitely appreciate how much more clean the language is.

      And C# runs on Linux, supported by the Mono guys. And it's so proprietary it's a standard, see http://www.ecma-international.org/publications/sta ndards/Ecma-334.htm. Nor is it byte-code interpreted. It's JITed which, if you don't know what that means, you certainly aren't qualified to discuss modern Java or C# implementations.

  16. 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.

    1. Re:Metrics by 7ex · · Score: 1

      Only trust in statistics you manipulated yourself!

      --
      http://blog.gauner.org - just a blog
  17. 11%?! by cromar · · Score: 1

    DAMN 11% in one year?! Personally I don't know how reliable their survey was, but being an ASP.NET developer (I assume that would be included for Windows), that scares me a little bit. I'd love to program for Mac or Linux; I do .NET 'cause that's the work I can get right now, but I don't want to become obsolete.

    Being trained to administrate an AIX 4.3.3 box here lately doesn't help... Talk about a triceratops enema!

    1. Re:11%?! by Jason+Earl · · Score: 1

      To a certain extent Microsoft makes a living by forcing developers to learn new technologies. You probably should be somewhat concerned about the long term viability of the skills that you are currently acquiring. On the bright side the Mono hackers appear to be doing a pretty good job of giving people in your position a viable road to a Free Software platform.

      I don't use Microsoft's technologies personally, but I wouldn't be too concerned about .NET becoming the next Powerbuilder. There's a large enough community that your skills are safe, and there's a workable Free Software variant if Microsoft decides to get pushy.

  18. 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 cromar · · Score: 1

      Bad for Microsoft. Good for development in general.

      I recently finished a huge VB web application for a government client of ours. All bullshit bureaucracy aside, VB syntax really bothered me. The fewer people using VB the better; I would love to never have to look at a line of VB.NET ever again.

    2. 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
    3. Re:Blowing off VB6 burned some bridges by blincoln · · Score: 1, Informative

      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.

      What would you have wanted them to do differently? VB6 and prior was a terrible language. MS included a conversion utility in VS 2003 that does a credible job of converting decrepit VB6 code into VB.NET in case you want to retain the ugliness of the old program. I'm not sure what more they could have provided.

      --
      "...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
    4. Re:Blowing off VB6 burned some bridges by MightyMartian · · Score: 1

      VB developers should have seen this coming with the incompatibilities that came when VB4 apps had to be ported. This is the problem with marrying your development to a company that holds no one but itself (and not even that many times) as a standard. Many developers I know don't code in MS environments because they like to, but rather because, being a dominant desktop OS, they have to. It's the risk that the code they're writing may be orphaned when MS decides to toss an existing development environment in the trash.

      It's all part of the forced migration which, one way or the other, MS forces upon all its users. They are not going to hold anyone writing in some older environment, because they're entire profit picture relies upon forcing everyone ahead.

      Quite frankly, I think most people who developed in VB6 knew damn well that they were eating the forbidden fruit.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    5. 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).

    6. Re:Blowing off VB6 burned some bridges by dedazo · · Score: 1
      The transition from VB3 to VB4 was not really problematic for most developers, IMO. First, the developer base was a lot smaller back then. Certainly large, but nowhere near what it was in 2001-2002. Second, the 16-bit edition of VB4 still supported VBX controls, so it was a good upgrade path if your apps required lots of custom controls. And the 16-bit EXEs also ran on Windows 95 just fine. You could then wait until your vendors created 32-bit versions of the controls (OCXs), at which point all you needed to do was open the project in VB4-32 and recompile. Not only that, but the move to Windows 95 obviated a lot of the 'eye candy' controls that were popular in the VB3 days under Windows 3.x.

      Third, there were no breaking language changes. In fact, it wasn't until VB.NET that Microsoft actually deprecated (While/Wend) or changed the meaning (Return) of a VB/Basic language element. Yet they kept that stupid "Option Explicit" option - go figure. Fourth, direct API calls from VB code were not really popular at the time, so application code tended to be simpler. And finally, there was only one type of VB application: the window-based desktop executable. No libraries or custom controls or stacks that were used from ASP or anything like that. There was no COM. It was that relative simplicity coupled with a real upgrade path that made those ports relatively painless.

      I remember playing with the old 'gorilla.bas' QBasic sample when VB6 was first released. It tooke me about an hour to port the direct screen drawing code to bitmaps drawn on a form. The rest of the code worked almost without changes. VB/DOS applications ported all the way through VB6 over the course of 10-12 years are really not that hard to find.

      The Microsoft BASIC dialects were a shining example of forward & legacy support for a development platform, at least until VB.NET arrived.

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

      Why was this modded a Troll? Because s/he said something positive about Microsoft?

      Everything this poster said is true, unless you take exception to the description of VB6 code as "decrepit" (having my share of battles to get VB6 to behave with null-terminated strings for API calls, I would say the poster was charitable)

    8. Re:Blowing off VB6 burned some bridges by Carcass666 · · Score: 1

      I'd bet a lot of it is just all of the "hacks" one comes up with to do anything useful with the VB6. Whether it's your swiss army toolkit of API wrapper calls, voodoo to implement threading, etc. most of this either comes "free" with .NET or it's much easier to implement. People work so hard to get stuff to work under VB6 that they don't want to go through the agony of doing all again, when in fact it is much easier. Not to say that there aren't workarounds required in .NET, but they are less frequent and far less ugly than with VB6.

    9. Re:Blowing off VB6 burned some bridges by Shados · · Score: 1

      Microsoft left VB6 with an incredibly easy upgrade path to .NET. The problem is, VB6 programmers in general really sucked, and their code didn't follow the architecture VB6 had in mind. So the big fat corporations that actually understood how the tool worked upgraded to VB6 as easily as you can expect switching major environments (not saying it was -easy-, but having done it myself a few time, its not hell either).

      The others with their spagetti code got left in the dust and got screwed. Of course, considering that was probably the majority, MS could have thought about it more...

      But there isn't much more they can do beyond "just about any DLL you made will run as is, and we have a wizard that will convert a lot of the code not in DLL, including legacy compatibility classes".

      The fact that VB6 code was difficult to maintain just on its own... not many upgrade paths could have dealt with it. But again, "real" VB6 or ASP code, done using the appropriate development standards, was quite a breeze to port...mainly because you could compile it and run it as is in a .NET environment...

    10. Re:Blowing off VB6 burned some bridges by gabrieltss · · Score: 1

      I'm one who was a VB3.0/VB4.0/VB5.0/VB6.0 developer (Visual Studio EE) who went to Java. I got sick of having to "port" my applications to the next release. At least with Java I get backwards compatability I just get ugly "deprected" warings in my compiles but that is it. The app just runs, be it Java 1.3, 1.4 or 1.5. I spent some time with Visual Studio .Net / VB.net and hated it. I figured my time would be better spent on a more cross platform language. I can make Java talk to about anything - although you could say the same for C/C++, and I can code it on any platform - can't say the same for VB. Heck I even have had it talking to AS/400's and Mainframes. Although .Net's Web Services are a nightmare to talk to. Try to get Apache Axis to talk to it, good luck! I have had Axis talk to just about every SOAP stack except M$'s. M$ tends to break standards the rest of the world uses. Why would I want to be tied to a broken development model like that?

      --
      The Truth is a Virus!!!
    11. Re:Blowing off VB6 burned some bridges by Anonymous Coward · · Score: 0

      I'm using Realbasic http://www.realbasic.com/
      Works great on Windows & Linux (but looks better in Gnome since RB uses GTK for Linux)
      We had to choose - VB / C# .NET, and still be locked in, or get something that can work on more than one OS.
      For half the price of our MSDN subscription, I can easily build multiplatform software.
      It's also made me a better developer, since RB has better OO than VB6.

    12. Re:Blowing off VB6 burned some bridges by Gazzonyx · · Score: 1
      Yeah - especially those of us who are stuck as interns working with an old Access Database... Especially since the original developer (whom we suspect wrote the code high, or at least we hope so) went off on his own from the publisher, never to be heard from again. I'm even stuck with the IDE (which, for those of you fortunate enough to not know, doesn't even have a tabbed interface - single pane of glass) since they offer me no way to export the code from their own IDE!


      On top of this, if you want to get help from Microsoft, all they'll do is talk about how you can 'redevelop your app. in .NET with SQL Server' - sure, that is unless you're using their Nth version of the MDAC and using DAO interface calls which will have to be changed to ADO.NET or wrapped in ODBC. Yet, they say 'we have a tool to export your tables and queries'! How about my crosstab queries? No? Thanks, now what about my reports and forms? No dice, you can recode them or... well, exporting the code isn't an option unless I want to export to another MDB.

      Well, they've given me the pattern - SQL and ODBC. So, next time around we'll be using MySQL and JDBC since everything has to be written again, anyways. If I could just export the code to .NET, and the calls for DAO had the same parameters as ADO(.NET) and if my reports and crosstab queries would export, I probably wouldn't think twice about it. But I'm not going to rewrite half a million lines of code to set myself up for it all over again.

      --

      If I mod you up, it doesn't necessarily mean I agree with what you've said, sorry.

    13. Re:Blowing off VB6 burned some bridges by Maxo-Texas · · Score: 1

      I agree. I don't see anything except normal discussion there.

      It's slashdot, strange modding happens. Could be he has an enemy or it could be someone misread it.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
  19. Hardly Filming. by Anonymous Coward · · Score: 0

    "Keep it all locked up in a nice blue box and what do you get? "

    Red vs Blue

  20. What about cross platform? by jmors · · Score: 1

    I wonder how this survey counts web applications with a browser front end and a mysql/php backend or applications written in java as well as other software development that is purposely not targeted for any specific platform? It is heartening to see linux gaining share but more and more it is possible to code not for a specific platform but rather to requirements in a platform agnostic manner.

    --
    The Matrix is real... but I'm only visiting!
  21. 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!

    1. Re:Java is... by maharg · · Score: 1

      I'll drink to that ! I have JBoss tickling MADs fancy on a regular basis. Schweeet ;o)

      --

      $ strings FTP.EXE | grep Copyright
      @(#) Copyright (c) 1983 The Regents of the University of California.
    2. Re:Java is... by gabrieltss · · Score: 1

      Yeah baby! JBoss rocks! I've developed Java Web applications on Windows and Linux - OS doesn't matter with Java Development. (IMHO .Net/.Nut sucks big green donkey d!cks! I do not like it - Sam I am.) I just fire up Eclipse and JBoss and go. But I must say developing in Linux is far superior to Windows. There really is less overhead in the OS, I notice the performance improvement big time! Although I use OpenSuse - "I know bad, bad Linux user don't you know about Novell!" I just haven't found another distro I'm comfortable in yet, although my new PC will get Kubuntu 64 bit on it - I've told myself to give it at least 60 days to see if I can switch. I just wish Sun would open source Java 1.5....

      --
      The Truth is a Virus!!!
  22. 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.

    1. Re:Different niches by Tarwn · · Score: 1

      It wouldn't take much for Linux to leap forward in manufacturing, they were nearly non-existent in that market a few years ago and I haven't heard much more recently either. I think I recall one historian that would mostly work on Linux, a couple OPC servers or clients, and other minor random things here and there. No cohesive packages we could hand our engineers, very little competition to things like Wonderware, PI, Rockwell, etc.
      Unless we're talking about manufacturing in terms of just the scheduling, routing, etc and lets not tie it into the automation or let the manufacturing equipment communicate instead of making users type, that might be further along.

      Don't get me wrong, I'd like to see more Linux in the manufacturing world, but I don't think it's there yet.

      --
      Whee signature.
  23. 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 Anonymous Coward · · Score: 0

      This is really funny!
      I'm sorry I wasted all my mod points today :-(

    2. 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?
    3. Re:New Ballmer Chant by Anonymous Coward · · Score: 0

      Throw it baby!! Throw!!

  24. Basic Math by je+ne+sais+quoi · · Score: 0
    From TFA:

    The targeting of Linux by developers increased by 34 percent to 11.8 percent. It had been 8.8 a year ago, according to the survey. Linux targeting is expected to reach 16 percent over the next year.
    Actually going from 11.8% from 8.8% is only a 3% increase, not 34%. I always find it odd when people calculate a percent increase in a percent, because it doesn't make any sense, wouldn't that be a perdecamil? (1 part in 100 times 1 part in 100 = one part in 10,000)
    --
    Gentlemen! You can't fight in here, this is the war room!
  25. What took everyone else so long? by Anonymous Coward · · Score: 0

    Windows lost me as a C developer back in 1992 when they suddenly decided to turn their "Developement Community" into profit margin. No room for the little guy after that. But as cross platform tools came a long life got easyer else where.

  26. Targeting Win32 Specifically? Winforms? IIS? .NET? by blcamp · · Score: 0, Flamebait


    It's not clear what is meant by the opening statement "Microsoft's Windows platform is losing traction" means.

    If I am writing a web application that happens to run on IIS, am I really "targeting Microsoft Windows"? I don't think so - all I'm "targeting" a web browser running on a client machine, and I shouldn't know nor care what operating system, platform nor browser it has installed.

    TFA doesn't seem to be making much of a point other than saying "we hate Microsoft, we think others do too, and therefore so should you".

    By the same logic, the folks writing COBOL to run on big iron should have packed it in decades ago. Guess what? They're still around, and they're still going to be around.

    Nice try, Redmond-bashers. You gotta come up with something better than that...

    --
    The problem with socialism is that they always run out of other people's money. - Margaret Thatcher
  27. 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.

  28. Web 2.0 trend (sorry for the buzzword) by Yold · · Score: 1

    TFA said that PHP usage has increased 3x. Web Applications are going to comprise the majority of business applications in the future. This is where management-types seem to be headed with everything. We are replacing CUFS (monolithic UNIX finacial database app used at many Big Ten schools) with a web-based solution. Electronic Medical Records systems are also mostly web-based.
        What would have been done with Visual Basic 6 in 1998, is now being done with PHP/.NET/JSP and Ajax technologies. These technologies (on the server-side) are pretty platform agnostic. The future of the client platform, is the web-browser. Microsoft knows this. It is why their standards compliance is horse-shit. If 60% of webbrowsers (w3wschools.org) are IE6/7, people will continue to develop for it as the primary platform. I can't even access my bank-account outside w/o IE. Microsoft is going to continue with their own standards, know matter how much developers bitch, because it fuels their O/S sales and marketshare.

    1. Re:Web 2.0 trend (sorry for the buzzword) by Anonymous Coward · · Score: 0

      I can't even access my bank-account outside w/o IE.


      change banks and then tell them why.

      a bank forcing you to use windows and / or IE is like a brinks (money pick up and delivery truck business) forcing their customers to leave their cash out on the curb for pick up.

      it just isn't smart.

      if nothing else, get a bank that will work with firefox and use a cd bootable distro to do your financial work.
  29. Good point :) by cromar · · Score: 1

    I like coding in Java. Especially now that it's been GPL'd.

    1. Re:Good point :) by steveheath · · Score: 1

      I don't really understand the stats at all. Leaving aside the small sample group, I wonder what question was asked. For example, do I target a windows platform? Well, generally, no! I almost always use Java or some other cross platform toolkit. However, when my current project goes live, what will it be hosted on? Is this the platform I am deemed to be targeting? (As it happens, it's still not windows ;-)).

      I wonder that Java was not in the results. Certainly in the UK, there's a *lot* of development that it targeting the Java platform (if my experience and the current job market is to be believed).

      I really think this article and associated survey don't actually say anything of merit..

      Perhaps a couple of /. surveys might me more representative? :)

  30. Re:Targeting Win32 Specifically? Winforms? IIS? .N by Anonymous Coward · · Score: 0

    If I am writing a web application that happens to run on IIS, am I really "targeting Microsoft Windows"?
    Is this a trick question?

  31. Statistics by E.+Edward+Grey · · Score: 0, Troll

    Another important percentage of which you should take note:

    The percentage of developers who make their living developing for Linux holds steady at 0%.

    --

    ---don't make me break out my red pen.

    1. Re:Statistics by monxrtr · · Score: 0

      Another important percentage of which you should take note: The percentage of people who make their living COPYING others holds steady at 100%.

      --
      "From DNA to P2P, we are all Copycats now. Go Go Copycat Power! Copycat Powers activate! Form of, a Copycat." --monxrtr
  32. 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!
    1. Re:Developing for Linux is just easier. by ChronosWS · · Score: 1

      Try writing a significant program using ONLY POSIX APIs. Once you are done writing all the libraries you need to do any real work for a project of any significance, then tell me what the documentation story looks like.

      You have to remember that the Windows API does an awful lot more than the POSIX APIs do. Microsoft saw a lot of benefit in giving developers a broad range of high-level features in the standard API, and as a result there is probably a library call that will do just about anything you need in Windows. Also, the entire Microsoft .NET API doesn't use any binders at all, because it's all online, searchable and cross referenced, made freely available to anyone who cares to use it. Includes lots of sample code too. It's called MSDN. It's not the amount of information to be documented which matters, it's how accessible it is.

      Speaking of Intellisense, it is one of the great features of our day, IMHO. Again, it is most useful because there are so many APIs to deal with which do so many things. The nice thing about Intellisense is that is also applies to your own code. If you do any .Net programming it's a wonderful thing, allowing you to even inspect an object for methods and properties without bothering to open up the source code or other documentation for it. Besides, it's easy enough to hit ESC to cancel Intellisense. Straw man if ever there was one. Oh, and Win32 is not .Net. It's not necessary to write directly to Win32 APIs any more except in limited circumstances.

      As for debugging, any application of more than basic complexity will benefit from, if not demand, quality debugging tools. This says nothing about the API and everything about how hard it is to write good software, especially on the time constraints to which most of us must adhere.

    2. Re:Developing for Linux is just easier. by Dr.+Manhattan · · Score: 1

      Try writing a significant program using ONLY POSIX APIs. Once you are done writing all the libraries you need to do any real work for a project of any significance, then tell me what the documentation story looks like.

      Um, the comparison was more than fair. It compared the .NET SYSTEM stuff to the POSIX spec. To re-quote: "Tabulating only MSCORLIB.DLL and those assemblies that begin with word System..." I mean, doesn't .NET consist of more than an interface to the operating system?

      So, are you going to write a significant Windows app with only MSCORLIB.DLL and the "assemblies that begin with the word System"? I'll quote someone else: "Once you are done writing all the libraries you need to do any real work for a project of any significance, then tell me what the documentation story looks like."

      --
      PHEM - party like it's 1997-2003!
    3. Re:Developing for Linux is just easier. by Ironpoint · · Score: 1


      "One of the reason skyscraper builders have cranes is because the NEED them. Building skyscrapers without them is nearly unmanageable. Skyscrape blueprints are huge, complex, only occasionally and accidentally orthogonal, and in my experience mostly very poorly documented."

      "Meanwhile, my entire treehouse blueprints, suitable for fully implementing a treehouse, fits in about two and a half feet of binders."

      "Welders are practically mandated if you want to work with any material as difficult as steel."

      "I develop many buildings at work. Its a core part of my job. I mostly enjoy working on treehouses, and think about skyscrapers. Treehouse blueprints are small, well-thought-out and are simple. I find very few parts of a skyscraper that have these traits."

      "I've rarely felt the need for more engineering support than a tape measure and a bucket of nails. The problems tend to be simpler and more easily uncovered. Nailguns are nice, and appear to take many of the good things about rivet guns and leave much of the weight behind. For some projects, it's very useful. For others, it's overkill."

    4. Re:Developing for Linux is just easier. by Blakey+Rat · · Score: 1

      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.

      The entire Windows API compared to POSIX? Talk about an unfair comparison.

      Try comparing the entire Windows API with (for example) the entire OS X API. Or Linux including POSIX *and* GNOME. POSIX on its own may be fine for writing a simple CLI program, but it can't do a fourth of the stuff .net is doing.

    5. Re:Developing for Linux is just easier. by Dr.+Manhattan · · Score: 1

      You really do need to read The Art Of Unix Programming, don't you?

      --
      PHEM - party like it's 1997-2003!
    6. Re:Developing for Linux is just easier. by Dr.+Manhattan · · Score: 1

      Gee, I didn't think I was that unclear. You're the second person to miss that I wasn't comparing all of POSIX to all of the Windows API. I was comparing all of POSIX to just the operating system part of the Windows .NET API. Again: "Tabulating only MSCORLIB.DLL and those assemblies that begin with word System..." I mean, don't you realize that .NET contains way more than that?

      --
      PHEM - party like it's 1997-2003!
    7. Re:Developing for Linux is just easier. by Com2Kid · · Score: 1

      So, are you going to write a significant Windows app with only MSCORLIB.DLL and the "assemblies that begin with the word System"? I'll quote someone else: "Once you are done writing all the libraries you need to do any real work for a project of any significance, then tell me what the documentation story looks like."


      Hey now. Don't get me wrong, I love developing for POSIX, but MS has far more under System.* than POSIX has all together.

      The comparison was also between the .NET api printed on 3x5 note cards, and between POSIX printed 8.5x11 paper (double or single sided?)

      Oh, and the programming paradigms are vastly different as well. Add a proper exception handling system and a hierarchy of exceptions, written in C, as well as the thousand other niceties of modern programming that .NET provides through its libraries (and through language support as well, of course) and then tell me how much more documentation is needed.

      Intellisense is needed yes, but for ickier parts of the POSIX api, tabbed terminals with MAN pages open is needed.
    8. Re:Developing for Linux is just easier. by Keeper · · Score: 1

      System.* contains way more than "operating system part" of the .Net API; in fact, I'd submit that most of the content under the System.* namespace isn't remotely comparable to the type of functionality present in POSIX. System.Xml, System.Text, System.Refleciton, System.Collections ...

    9. Re:Developing for Linux is just easier. by mr_man · · Score: 1

      The OP got it right here and you are in the wrong. If you look at the assemblies that are in %WINDIR%\Microsoft.NET\Framework\v2.0.50727 (which is the RTM version of the 2.0 Framework) you'll find 28 files.

      C:\Windows\Microsoft.NET\Framework\v2.0.50727>dir /B System*.dll
      System.configuration.dll
      System.Configuration.Install.dll
      System.Data.dll
      System.Data.OracleClient.dll
      System.Data.SqlXml.dll
      System.Deployment.dll
      System.Design.dll
      System.DirectoryServices.dll
      System.DirectoryServices.Protocols.dll
      System.dll
      System.Drawing.Design.dll
      System.Drawing.dll
      System.EnterpriseServices.dll
      System.EnterpriseServices.Thunk.dll
      System.EnterpriseServices.Wrapper.dll
      System.Management.dll
      System.Messaging.dll
      System.Runtime.Remoting.dll
      System.Runtime.Serialization.Formatters.Soap.dll
      System.Security.dll
      System.ServiceProcess.dll
      System.Transactions.dll
      System.Web.dll
      System.Web.Mobile.dll
      System.Web.RegularExpressions.dll
      System.Web.Services.dll
      System.Windows.Forms.dll
      System.XML.dll

      For example, this list includes System.Windows.Forms.dll (WinForms) which is the GUI component of the .NET Framework. You aren't comparing apples to apples here. You might have better luck comparing just mscorlib.dll and System.dll to the POSIX standard, but I still think it wouldn't be fair (There are collections in both mscorlib.dll and System.dll and I don't think that's something that POSIX defines, but I could be wrong here).

    10. Re:Developing for Linux is just easier. by ozphx · · Score: 1

      Complexity of a system will increase with its expressiveness. I had a long argument with a mate about this, and it seems to be a basic tenet of information theory.

      Bascially with a POSIX system it means you are stuck with munging text pipes...

      --
      3laws: No freebies, no backsies, GTFO.
    11. Re:Developing for Linux is just easier. by Dr.+Manhattan · · Score: 1

      The comparison was also between the .NET api printed on 3x5 note cards, and between POSIX printed 8.5x11 paper (double or single sided?)

      Single-sided, POSIX comes out to less than 16 feet, .NET System to 40 feet. (Check my math.) And, again, the POSIX spec contains a lot more than just the kernel interface, and includes commentary and design rationales.

      Oh, and the programming paradigms are vastly different as well.

      I think we're in violent agreement there. And I didn't say POSIX was perfect, just much easier to develop for. For example of the problems, see here.

      --
      PHEM - party like it's 1997-2003!
    12. Re:Developing for Linux is just easier. by Anonymous Coward · · Score: 0

      Your post displays a profound misunderstanding of Windows. The .NET 2.0 framework class library is *not* Win32. Also, your comparison of "feet of 3x5 cards" to "feet of binders" seems irrelevant. The only meaningful thing we can learn from CP's statement is that 60,000 index cards are 40 feet tall when you stack them.

      The System.* assemblies? They contain things like:
      System.Data (all of ADO.NET)
      System.Web (all of ASP.NET and web services)
      System.Windows.Forms (all things GUI)
      System.Drawing (GDI+)
      System.XML
      System.Security
      System.Management
      System.a whole bunch of other stuff

      It's pretty much everything you can do with .NET on Windows, and basically only doesn't include the Microsoft.* assemblies that most people don't use anyway.

    13. Re:Developing for Linux is just easier. by Blakey+Rat · · Score: 1

      Single-sided, POSIX comes out to less than 16 feet, .NET System to 40 feet. (Check my math.) And, again, the POSIX spec contains a lot more than just the kernel interface, and includes commentary and design rationales.

      And .NET System contains System.Windows.Forms (i.e. pretty much everything you need for a GUI app in Windows), it includes an XML parser, it includes all kinds of web libraries.

      POSIX has none of those. It is truly an unfair comparison.

    14. Re:Developing for Linux is just easier. by julesh · · Score: 1

      Um, the comparison was more than fair. It compared the .NET SYSTEM stuff to the POSIX spec. To re-quote: "Tabulating only MSCORLIB.DLL and those assemblies that begin with word System..." I mean, doesn't .NET consist of more than an interface to the operating system?

      Err... The "System" heirarchy in .NET contains a lot more than OS interfacing. It contains, among other things, basic data types including string and number handling, a collections library, class reflection and runtime invocation, a GUI framework, database access, XML and HTML DOM implementations, an in-memory database implementation that uses the XML DOM as its storage target, a framework for writing web applications, image manipulation libraries, three data serialization frameworks (binary, xml and soap), remote procedure call handling, and a whole load of other useful junk.

      So, are you going to write a significant Windows app with only MSCORLIB.DLL and the "assemblies that begin with the word System"?

      Yes. I have written a reasonably complex domain-specific CAD application in C++/CLI using only System packages (System, System::ComponentModel, System::Collections, System::Windows::Forms, System::Data, System::Drawing, System::IO and System::Runtime::Serialization::Formatters::Soap). The only library-like code I had to write was a set of domain-specific objects that could be included in drawings.

    15. Re:Developing for Linux is just easier. by Com2Kid · · Score: 1

      And, again, the POSIX spec contains a lot more than just the kernel interface, and includes commentary and design rationales.



      And the .NET API includes variable names of more than one character! :-D

      Ultimatly though, both are rather nice APIs to code against. Even ignoring GUI work, both are much nicer to use than (aside from .NET) most of Window's other APIs.

    16. Re:Developing for Linux is just easier. by Dr.+Manhattan · · Score: 1

      Single-sided, POSIX comes out to less than 16 feet, .NET System to 40 feet.

      Actually, I checked today. It's double-sided, but the binders themselves add thickness. An unbound set comes out to ~8 inches, and that works out to (8.5*11)/(3*5)*(2*8 inches/12 inches per foot) or ~8.3 feet of 3.5 cards, or about 1/5 of .NET. (And about three feet of POSIX would be devoted to the introduction, definitions, utilities (like tar, compress, vi, and such), and rationales.)

      And .NET System contains System.Windows.Forms (i.e. pretty much everything you need for a GUI app in Windows), it includes an XML parser, it includes all kinds of web libraries.

      As I've pointed out, the POSIX spec covers pretty much an entire operating system and environment with attendant utilities sufficient to run a business on. But you're right, I wasn't correct regarding what .NET "System" contained, so the comparison is not entirely fair.

      So, let's even it up. Add another 6 feet to POSIX for the GUI stuff. Now POSIX+GTK (thoroughly documented) comes out to ~14.5 feet, or just over 1/3 of a sketchily-documented .NET.

      Of course the metric here isn't totally scientific. But we know that Windows is just more complex than Linux or other POSIX-style systems. My overarching point was... let's see, what was it again... ah, yes, here it is:

      "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... 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."

      --
      PHEM - party like it's 1997-2003!
    17. Re:Developing for Linux is just easier. by Anonymous Coward · · Score: 0

      Have you ever actually coded on a serious .NET project? I've been doing .NET since it first came out. The documentation resources are massive and typically well written. On top of that you have a slew
      of books, sites, and forums. I've hardly ever found myself lacking for an answer to a problem or
      details on some aspect of .NET.

      I also certainly wouldn't make the case the .NET is driving people from windows. Quite the oppposite.
      C/C++ is pratically non-existant, Java gone on the UI, and .NET carving a large portion of web and
      server. I've been to a lot of business and one only has to look at the job number comparisons. Last
      time I checked I'm in no danger of going hungry from lack of work.

  33. Re:Targeting Win32 Specifically? Winforms? IIS? .N by cromar · · Score: 1

    Another point is that Windows is losing developers.

    And yes, if you code .NET for IIS that is Windows dev for the time being (we'll see how Mono will do). Because you are using the web for you GUI doesn't mean that your code isn't running under windows...

  34. What would they expect... by xtracto · · Score: 1

    ... If they sue the same developers that program on their platforms. I will never develop for a closed platform like Windows which such EULAs, NDAs and whatever else license they put... you never know with what will they come up next in their licenses.

    Personally I do Java and love it. I have programmed in C# (Visual studio 2005 I think) and I prefer Eclipse, for production (read, real enterprise applications) environments.

    --
    Ubuntu is an African word meaning 'I can't configure Debian'
  35. True but by Sycraft-fu · · Score: 1

    Simply randomly picking 400 doesn't necessairily do a good job either, especially if it really isn't random. One big problem with many surveys is they are self selecting to a large degree. The survey company sends out paper surveys or makes calls. While they may do so in a truly random to stratified random fashion, the people that elect to respond may not be a random subset. For example, suppose that Linux developers are much more likely to want to evangelize their choice. We certainly know that minority platform supporters are extremely vocal as a whole (you see it here daily on Slashdot). So perhaps they call 4000 developers, and only 10% elect to respond. However of that 4000 developer set, only 50 (1.25%) are Linux developers. However all but two elect to respond. That would give the 12% result reported, yet be grossly inaccurate of the overall picture.

    I'm not saying that is what happened, but simply saying "Well we called a random sample," doesn't cut it since you are dealing with self selection. Likewise, if you try to control for that and screw up the way you pick your sample you can bias it yourself.

    This is not an easy thing to deal with, and pollsters fuck it up ALL the time. Witness the Family Guy fiasco. Fox canceled it because their numbers said people weren't watching it. DVD sales proved that their numbers were full of shit, they just hadn't been measuring most of the demographic that did watch it properly.

  36. Flawed by Anonymous Coward · · Score: 0

    Honestly, I don't believe this "study" for a second.

  37. 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.

    1. Re:Number != percent by vga_init · · Score: 1

      I wasn't mislead; it seems that percentage is the most relevant piece of information anyway. Obviously, people who are already skilled in developing for Windows are going to keep up with it, but if the market is changing overall as new work goes into it, that is very important.

      By that token, are there really any fewer COBOL developers than there have always been? Heheh...

  38. 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.

  39. Re:Targeting Win32 Specifically? Winforms? IIS? .N by SatanicPuppy · · Score: 1

    Cobol is niche, and like a lot of niche languages, if you don't know it, it's not going to limit your job prospects very much. I haven't polished my FORTRAN in a decade, and I don't really miss it. I feel the same way about VB6, and ASP.NET I view to be on the same level. C# I still use, just because it's no mental stretch to shift back and forth between it and Java. But the day when I don't need C# anymore, I'll dump it into the mental dustbin with FORTRAN, SCHEME, PASCAL, and VB6.

    And the fact that that day is getting nearer should scare the shit out of Microsoft. They absolutely depend on people being forced to learn their stuff, they absolutely depend on IE-only apps driving IE marketshare (and windows marketshare along with it). When no coder ever needs to learn C# or ASP.NET, then they will have truly become irrelevant to the internet.

    --
    ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
  40. Evans Data simply not reliable by Anonymous Coward · · Score: 0

    They claimed Java would be the dominate platform back in 2001.

  41. .NET for web a big mistake by diodeus · · Score: 1

    With the growth of web-based development I found that .NET was a big step sideways for M$. The problem being that the .NET IDE tried to make building a web app a lot like building a desktop app. You are no longer intimate with your code and depend too heavily on generators and libraries. Unless you're a newbie as web development it's a big hindrance.

    1. Re:.NET for web a big mistake by 16K+Ram+Pack · · Score: 1

      .net is like many other forms of code abstraction. It's great for what it does, but when you want to try and break its rules (like doing javascript), it can make life real difficult.

  42. Hmm?? by j_w_d · · Score: 1

    ...but simply saying "Well we called a random sample," doesn't cut it since you are dealing with self selection....

    How does it deal with self selection? If you post a "survey" on the internet, the respondent's are very likely to be self selected and sensitive to the issue. If you post a query about Bush pardoning Libby on a Limbaugh website, you can readily predict the outcome. That is self-selection. If you have someone pull phone numbers for developers and create a blind list from which to randomly draw a sample and ask what platforms they develop for, there can be no self-selection except with respect to a willingness to be interviewed.

    --
    ------ The only greater hazard to your liberty than n politicians is n+1 politicians.
    1. Re:Hmm?? by Sycraft-fu · · Score: 1

      Because most people won't answer the survey. You cannot force them to do so. Thus those that do self select to do so. It turns out that it is NOT random who does and does not answer surveys of various types. Thus you have a self selection problem. It is further problematic since you can't find out why a person does or doesn't choose to answer the survey. You can't ask those that don't and those that do may not give an accurate answer since they many not know why they chose to.

  43. Delivery mechanism for apps by leather_helmet · · Score: 1
    The delivery mechanism for applications is shifting, in a relatively rapid manner, to the web browser. With the adoption of standards I think this shift will continue into the foreseeable future. In addition, other form factors (Post PC devices) are gaining more market share everyday.

    Is windows doomed as a development platform? Nope, it still has some of the best and most mature development tools around - It still has the largest market share as an OS, etc.

    We have been using Visual Studio and related tools for quite a while, but have realized that the various license fees, etc. do not justify us using the Windows platform as our only dev platform - we will continue to support it as long as we have paying clients

  44. Not really... by Anonymous Coward · · Score: 0

    because the BSD code is still under BSD. If someone wanted to take that code and use it in a propritaty system, they could

    1) buy a license for QT (same binary, different license)
    2) not use the QT calls (port to another UI library like WX)
    3) not use the GUI bit at all (if it isn't necessary for the code taken

    All that will happen is that the application sans QT will be available for a closed application, but that works because the QT calls are dynamically bound: it just won't work without the QT libraries.

    1. Re:Not really... by nebosuke · · Score: 1

      Developing code with the GPL version of QT (note that the code being developed need not itself be GPL'd) and later purchasing the commercial version as a drop-in replacement just before product shipment was explicitly disallowed last time I looked into QT.

    2. Re:Not really... by Anonymous Coward · · Score: 0

      Is that legally enforceable? If it really is, then any code written while using the GPL version could only be used if released as GPL for as long as Trolltech wishes. How is it possible for a third party to have so much power over work you own?

      That really doesn't seem right and I doubt it's possible.

  45. 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.

  46. Yes, why not Java? by Latent+Heat · · Score: 1
    My version of "not developing for Windows" is to write the graphical front end in Java Swing and write the numeric back end in non-graphical C++.

    Yes, you have to recompile the C++ for the different OS's, but Java Swing is everywhere -- Windows, OS-X (yeah, yeah, true believer Mac people don't like the way Swing apps look), Linux.

    If I am going to leave Windows, I am going platform-independent rather than down the path of the flavor-of-the-month-GUI (cough, cough Qt, GTK). Yes, there is some degree of platform independence with those other things, but Java is everywhere these days. Much less futz factor having the target GUI layer available on other machines. There is a near universal expectation of having Java installed on network-share systems where I don't get to install those other things.

  47. Funny thing... by Anonymous Coward · · Score: 0

    Those 12% that develop for Linux also make up the entirety of Linux users!

  48. Market share by core_dump_0 · · Score: 1

    I have been developing software for fun since I was younger.

    I never develop *exclusively* for Windows (i.e. Visual Basic, Visual C++) anymore, given that Java and text-based apps with source code can run on more platforms.

    It's simply a matter of market share: the more operating systems your program can run on, the better. Java and open-source text-based apps win hands-down in that department. The Microsoft "monopoly" is gone. (I never believed it was a true monopoly, more like a matter of personal preference and convenience, which changed with Mac OS X and easier Linux.) It's a cross-compatible world now, and Microsoft is becoming irrelevant unless they change their business model.

    1. Re:Market share by dsvick · · Score: 1

      I have been developing software for fun since I was younger.

      Technically we all have.

    2. Re:Market share by MysteriousPreacher · · Score: 1

      You're technically correct, the best kind of correct.

      --
      -- Using the preview button since 2005
  49. Too bad no Mac numbers... by micromuncher · · Score: 2, Insightful

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

    --
    /\/\icro/\/\uncher
  50. There is NO linux by zymano · · Score: 0, Redundant

    linux is just a kernel.

    Last time i used linux, software wasn't interoperable,nor drivers.

    linux to me is a huge headache with hundreds of different os'.

    Hope for Haiku os.

    1. Re:There is NO linux by SEMW · · Score: 1

      Not only did that not make the slightest bit of sense ("hundreds of different os'"?), it wasn't even a haiku. Haiku's are 5-7-5.

      --
      What's purple and commutes? An Abelian grape.
    2. Re:There is NO linux by Anonymous Coward · · Score: 0

      Isn't Haiku the free version of BeOS? (Or some similar excellent also-ran.)

  51. Perhaps Its just gotten easier: It has & matur by Anonymous Coward · · Score: 0

    "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." - by cybrthng (22291) on Tuesday July 03, @02:47PM (#19733963)

    Agreed, 110%, & great points you made. Windows wares are VERY solid nowadays, & I suppose it almost makes it a "rule of thumb" that after a decade on any given platform, such as Win32? You WILL have high-quality wares by the truckload, that are matured & solid!

    Even shareware/freeware nowadays? Is of such quality, it would have rivalled if not exceeded in many a way, the commercialware of 5-10 years ago... imo, @ least!

    (And, I consider myself somewhat of a "software connoiseur" of the shareware/freeware AND commercialware world...)

    However, "not only am I a client of Win32 softwares in commercial/shareware/freewares, but, I am ALSO a 'developer member' as well" & I have been for over a decade in the freeware/shareware arena (that statement's all in reference/analogy to "THE HAIR CLUB FOR MEN", lol, bad attempt @ humor, but see the URL below for backing proof of it):

    http://www.techpowerup.com/downloads/389/foowhatev ermakesgooglehappy.html

    APK

  52. Java is the best platform right now. by master_p · · Score: 1

    Java has really matured. Its VMs are very fast, on par with C/C++, the language offers excellent facilities like generics, Eclipse is quite a good IDE (not the best, but quite good, especially if you get used to its intricacies), there is a huge community and the SDK is excellent.

    So why code specifically for Windows? we have nothing to gain from a Windows-only application. We write our apps in Java, we pay attention to platform specific details, and most code runs as is in Windows, Unix/Linux and Mac OS.

    1. Re:Java is the best platform right now. by shutdown+-p+now · · Score: 1

      Short answer: Java GUIs still look like crap compared to native GUIs (or Qt, for that matter). 1.5 was way better than 1.4, and 1.6 is somewhat better than 1.5 ("hey, it's 2007, and we've finally got subpixel aliasing, like the rest of the applications on this OS did since 2001! yay! except it still looks weird, and some shapes are wrong, but whatever..."), so things are getting better slowly. But they're not yet good enough.

    2. Re:Java is the best platform right now. by master_p · · Score: 1

      Not if you use JGoodies.

    3. Re:Java is the best platform right now. by julesh · · Score: 1

      Short answer: Java GUIs still look like crap compared to native GUIs (or Qt, for that matter).

      Come again?

      Could you give me a rundown on what's wrong with these screenshots compared to a "native" GUI? Because frankly I don't see the slightest difference.

  53. 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.

    1. Re:I'm actually sad about this by Anonymous Coward · · Score: 0

      In the last few years Microsoft has increasingly taken a "My way" or the "High way" approach to software development.

      You mean "my way or the highway". Quotes around the entire thing, highway is one word.

      The very thing Operating systems are supposed to enable.

      First of all, this is a sentence fragment and doesn't make any sense. I assume you were trying to say something about operating systems enabling programs, but I'm not sure what your point was.

      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.

      Wait, what? Name one documented feature in an API that has been "unexpectedly denied."

      Add to that this crazy program (I refuse to call it an operating system) called Vista

      Why? That's what it is. Do you refuse to call your mother a woman?

      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.

      No, you mean that you have a huge skill base in Windows XP. You're just setting yourself up to be disappointed if you think you won't have to learn quite a bit to use Vista just as well. And if you expect your XP skills to translate to Linux -- get ready for an even larger disappointment!

    2. Re:I'm actually sad about this by pjabardo · · Score: 1

      I think that your turnkey solution will become more common as virtualization becomes popular. This could be a solution to several problems.

  54. Computing economics by lilfields · · Score: 1

    I think this raises the question of who really has control of which OS has the dominant market share, the developers, or the consumers. I'm going to go with the consumer on this one, no consumer means developer goes out of business, no developer means consumer goes elsewhere. Elsewhere appears to be Microsoft; just because you don't like Microsoft doesn't mean that "OMG Microsoft won't be the number one operating system in a matter of years! GO LINUX!"...Why can't most enthusiasts just realize there are advantages to different platforms and leave it at that, don't turn software into a religion. Admittedly I usually stand up for Microsoft because they are usually the ones hated with the most passion, but my desktops run on Windows (XP, Vista), my server runs on Linux. I also vastly enjoy open source, but that doesn't mean that I like running an open source operating system on my desktops. I think maybe the survey lacks that understanding with some of the developers.

  55. smells by Anonymous Coward · · Score: 0

    "...In other findings in the Evans Data Spring North American Development survey, Evans found that JavaScript is the most widely used scripting language. It has more than three times the users of PHP (Hypertext Preprocessor), Ruby, or Python. But Ruby usage is expected to increase by 50 percent within the coming year."

    hmmm there is something that doesnt smell right in that survey...

  56. Advertisers, advertisers, advertisers, advertisers by Anonymous Coward · · Score: 0

    Not a problem. According to Balmer, "developers, developers, developers, developers" is old news. It's "advertisers, advertisers, advertisers, advertisers" now.

  57. I bet they're only polling US devs by justdrew · · Score: 0

    most of that 11% is outsourced is my bet, not an actual reduction.

  58. Linux Fanboy Drivel by Anonymous Coward · · Score: 0

    OS X has Linux beat all the way. This is just silly.

  59. Visual Studio verses Notepad by LifesABeach · · Score: 1

    Visual Studio fills a lot of gaps, for the day to day needs. My problem has been that sometimes the Sales staff have gotten a contract in which .NET does not like; For example XML preprocessing statements in a XML output from a .NET Web Service. Web 2.0 applications security could be increased greatly if this were allowed. But it was solved by using Notepad, that I was able to side step this issue. That is when software engineering begins. I am glad I know both.

  60. 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.

    1. Re:North American developers? by Anonymous Coward · · Score: 0

      What's the point of polling North American developers? Because that's the only nation where Microsoft still looks dominant.
  61. How to tell the difference. by twitter · · Score: 1

    How do you determine a windows coder vs a universal or only a linux/unix coder?

    All but the Linux/unix coders have bags under their eyes.

    Just because there are more developers in other environments, doesn't mean the market has dried up, just that it has matured.

    The proportion of Windoze only developers just lurched 11% down to 65%. Give it a year or two and they will be less than 50%.

    What's surprising is that they could find so many in 400 developers. GNU has owned the web for a while and now owns embeded systems. Student and small business users would be clueless or crazy to do anything but download a Linux distro to make things work because of the cost and performance differences. The way M$ calls developers "pawns" and the way they have put the smack down on the largest "competitors" you have to wonder why even those people would be Windoze only. In the Windoze world, you have to pay to play and M$ will steal the pie if you make anything.

    --

    Friends don't help friends install M$ junk.

    1. Re:How to tell the difference. by Anonymous Coward · · Score: 0
      twitter, please read this carefully. Following this advice will make Slashdot a better place for everyone, including yourself.

      • As a representative of the Linux community, participate in mailing list and newsgroup discussions in a professional manner. Refrain from name-calling and use of vulgar language. Consider yourself a member of a virtual corporation with Mr. Torvalds as your Chief Executive Officer. Your words will either enhance or degrade the image the reader has of the Linux community.
      • Avoid hyperbole and unsubstantiated claims at all costs. It's unprofessional and will result in unproductive discussions.
      • A thoughtful, well-reasoned response to a posting will not only provide insight for your readers, but will also increase their respect for your knowledge and abilities.
      • Always remember that if you insult or are disrespectful to someone, their negative experience may be shared with many others. If you do offend someone, please try to make amends.
      • Focus on what Linux has to offer. There is no need to bash the competition. Linux is a good, solid product that stands on its own.
      • Respect the use of other operating systems. While Linux is a wonderful platform, it does not meet everyone's needs.
      • Refer to another product by its proper name. There's nothing to be gained by attempting to ridicule a company or its products by using "creative spelling". If we expect respect for Linux, we must respect other products.
      • Give credit where credit is due. Linux is just the kernel. Without the efforts of people involved with the GNU project , MIT, Berkeley and others too numerous to mention, the Linux kernel would not be very useful to most people.
      • Don't insist that Linux is the only answer for a particular application. Just as the Linux community cherishes the freedom that Linux provides them, Linux only solutions would deprive others of their freedom.
      • There will be cases where Linux is not the answer. Be the first to recognize this and offer another solution.

      From http://www.ibiblio.org/pub/linux/docs/HOWTO/Advoca cy

    2. Re:How to tell the difference. by gig · · Score: 1

      > The proportion of Windoze only developers just lurched 11% down to 65%. Give it a year or two and they will be less than 50%.

      In a year or two, Windows may be less than 50% of the Web also now that phones are getting real browsers. It's going to be harder and harder to convince people to use the backslash.

      As an aside, when somebody says "forward slash" to me I immediately write them off as an idiot and I have never regretted it.

  62. 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

    2. Re:If only it were true. by John+Sokol · · Score: 1


        Yes, but again, 400 samples taken where? How?
        I agree with those number, but this only holds true under certain conditions where there are random distributions and no biasing.

          For example are you measuring people height this would be fine normally, unless your samples were taking in front of a big and tall clothing outlet or inside an NBA locker room.

        This is the thing that always messes up almost every political poll is finding a un-biased source to take your samples.

          Even something like poll taking in a Red State or Blue state would bias the linux vs. windows results. Where I suspect red states would lean more towards windows.

      --
      I am always doing that which I can not do, in order that I may learn how to do it. - Pablo Picasso
  63. Known vs. Unknown Applications by Anonymous Coward · · Score: 0

    ""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."

    Enlightenment if you want to be different AND unknown.

  64. Or gtkmm by owlman17 · · Score: 1

    gtkmm is a nice C++ inteface to GTK+ if you want to code in C++ and GTK+.

  65. GUI Layout and Java by Anonymous Coward · · Score: 0

    Try Netbeans 5.5 or 6 and the Matisse graphical
    editor. It's finally nearly right. Not perfect,
    but close.

  66. Visual Studio prices by Anonymous Coward · · Score: 0

    I'd wager it is because Visual Studio went from $1,400 (VS.NET) to $5,000+ (VS 2003). The Team Systems crap is rediculous. $10,000+ to get all of the "types" of VS, per seat. Developer, Architect, Tester, Database. What team under 20 doesn't have 50%+ team members filling all of those roles at one time or another.

  67. Should have mentioned Mac by Anonymous Coward · · Score: 0

    Well, I develop on a Mac. Being able to run all major OSs, not to mention the power of Mac OS X.
    It's great for a developer.

  68. 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?

  69. What's different about WebSphere? by ghostunit · · Score: 1

    I'm just starting to develop a java app for websphere so your remark got my attention. Could you explain it a little bit please?

  70. jesus by Anonymous Coward · · Score: 0

    i can't belive you even posted this.
    this is like linus getting stoned and going on tv claiming 99% of people use linux now.Not that 60% of stupid people wouldn't fall for it and switch right over...

  71. That is not true by rolfwind · · Score: 1

    I would buy software for linux. But only for needs I have which free software does not already fill. Hence, no ftp programs and the like.

    BUT... the big problem is, if there is a free alternative, I'll take the free alternative first. Windows users do the same or they often pirate (at home). The difference is that Linux has a ton of decent software for free. And that linux users used to be more technically apt so they could make their own small utilities. This freezes a lot of small time Windows users out who used to make small programs and make a healthy living off of them. Programs for Linux can't be so simple.

    The other problem is that a lot of software for Windows are only made to make up for the built in unnecessary deficiencies of Windows - adaware, windows start-up monitor, registry cleaners, etcetera. Linux has less deficiencies and it also generally does what the user tells it to without overwriting settings on whim. So that market is out.

    Another problem is an easy installer for Joe Average (no CLI) but without package management. I think Click-n-Run, when ported to Ubuntu later this year by Linspire, will offer a great opportunity for non-free software - for the first time on a widely popular distro software can be PURCHASED easily.

    I think there is opportunity for nonfree apps on Linux, but the market is different and one has to recognize that. One such software would definitely be turbotax or an alternative. Another would be something like an eBay Blackthorne (auction management software).

    There are niches to be filled, to be sure - and I think a lean, enterprising developer will be able to take advantage of it. With click-n-run on Ubuntu, Ubuntu on Dells, etcetera - the situation is shaping up soon where some business can be made. The market for Linux is smaller, but that ecosystem is not yet saturated by developers either - so there are advantages/disadvantage either way you look at it.

    As well, all three major platforms (OS X, Linux, Windows) can be programmed for simultaneously with a toolkit like Qt - so the risk does not have to be taken while the same advantages gained.

  72. indian programmers? by chrisranjana.com · · Score: 0

    Wonder what is the percentage statistics with the indian programmers community ? would they have embraced linux or windows?

    --
    Chris ,
    Php Programmers.
  73. Good Morning by Anonymous Coward · · Score: 0

    The native one, perhaps?

  74. It's changing faster than that by laird · · Score: 1

    While the overall population of programmers may be shifting slowly away from Windows, the shift new developers coming out of school is much more dramatic. My company (Pando Networks) ships an application on Windows, Mac and Linux, and when we recruit new developers from school we see ZERO experience with Windows development coming from the universities. Schools are completely focused on modern, portable languages (e.g. Java, Ruby), and they're writing mainly "web apps", so few students have more than a passing acquaintence with C++, a few played with .Net on servers, and none have written a "Windows app". If our experience is typical, I'd say that MS has completely lost the next generation of softare developers.

    From the corporate IT perspective, I think that this also the case. IT would rather implement Web apps, which are easy to deploy and support. So while the developers might use Windows computers on their desktops, and perhaps as the servers, that doesn't particularly affect the software - Java, PHP, etc., are effectively the same on all platforms. And even the developers writing .Net server software are less tied to Windows than they would have been if they were writing a Win32 client/server app.

  75. Machines not built to last by ruewan · · Score: 1

    I would be running a 3 year old PC if I could get one to last that long. The laptop I had before this one lasted 25 months. The one before that lasted 12, died just after the warranty. I think it is a conspiracy to make me pay more windows tax.

    As for running Pentium 1 systems I guess that is fine if the systems are not windows machines or if those machines don't surf the internet. I don't think those systems would run windows xp very well and their are unpatched holes in the older versions of windows that are no longer supported by Microsoft.

    1. Re:Machines not built to last by Billly+Gates · · Score: 1

      A pentium runs windows98 and NT 4 just fine. Typically those who don't upgrade hardware wont upgrade software either.

      My father's windows98 pentiumII keeps running like an old japanese car with everyone else broke like both cdroms, the sound card, etc. He runs firefox and it will run forever until it breaks before he buys a new system.

      BTW I have only seen 1 system of mine fail for hardware reasons. The rest I broke myself :-)

      I build my own systems and never buy Dell, Sony, or Emachine units that are known to break. These systems can work for years without an issue. I have a compaq pressario notebook and after Carly Fiona left HP, the quality has gone up as well for their products.

  76. Re:Open your eyes.... by Technician · · Score: 1

    I'm guessing the majority of the applications written to target Linux are server applications.

    Open Office, Ghostscript (all in one priners are getting support), Q-Light, Gimp, Kstars, Flash 9 for Linux, Non-free codecs ;-), Acidrip, Mplayer, Banchee, mtp Libraries for the Zen etc.., Myth, Astrisk, Ekiga, Bittorrent, Network Manager (Wireless support.. WooHoo), the list goes on..

    If you have a Ubuntu box, when is the last time you did an update? Everytime I do an update, I see lots of evidence of programmers at work on Linux.

    --
    The truth shall set you free!
  77. What do you mean? by twitter · · Score: 1

    In a year or two, Windows may be less than 50% of the Web also

    M$ has a hard time getting more than a third of the web and their expansion is capped. Only terminal M$ partners run M$ web servers. Ventures into M$ hosting have met disaster and DIY types will always use some kind of free software. What do you mean when you say Windows may be less than 50% of the web?

    --

    Friends don't help friends install M$ junk.

    1. Re:What do you mean? by Macthorpe · · Score: 1

      Ventures into M$ hosting have met disaster Let me see. From the top 20 US websites by traffic:

      Myspace.com - Windows Server 2003
      Microsoft.com - Windows Server 2008
      eBay.com - Windows Server 2003/Windows 2000
      Live.com - Windows Server 2003
      AOL.com - Windows Server 2003
      Go.com - various including Windows 2000
      comcast.net - various including Windows 2000
      MSN.com - Windows Server 2003

      I must remember to change the definition of 'disaster' to include 'becoming the third most used website in America'.
      --
      "It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
  78. Not even, that way. by twitter · · Score: 1

    Clueless M$ user Macthorpe is confused by hosting and dreams of a M$ dominated web. By M$ hosting disaster I mean companies that tried to sell web hosting all bellied up. Your little partial quote of the top twenty web sites does not bring the results you want either (an old list). You can add up all of the M$ sites and barely beat either Yahoo or Google but not both. AOL does not use M$ . When you add them, youtube, wikipedia and other great GNU powered sites, M$ quickly vanishes. When you include the traffic from all the smaller sites, there's no contest at all.

    --

    Friends don't help friends install M$ junk.

    1. Re:Not even, that way. by Macthorpe · · Score: 1
      Clueless Linux zealot and complete moron Twitter can't wrap his head around the fact that '33% of the market' doesn't mean 'loss-making money sink', and also can't understand that 'someone who tells the truth' does not equal 'Microsoft shill'.

      By M$ hosting disaster I mean companies that tried to sell web hosting all bellied up. Bullshit. How weird is it that they can offer a 99.99% uptime guarantee and yet still not lose money on Microsoft servers? Can I put it to you that it's because they know more about hosting websites than you? I'm willing to bet that it's that.

      Your little partial quote of the top twenty web sites does not bring the results you want either My list was from Alexa who are very much up to date thank you very much. Just because you click the first google search you see, doesn't mean I do.

      AOL does not use M$ Try doing a wider search of Netcraft instead of taking the first result you see and accepting it as gospel, because it looks like all their webmail hosting is on Windows Server 2003. How about that.

      When you add them, youtube, wikipedia and other great GNU powered sites, M$ quickly vanishes. When you include the traffic from all the smaller sites, there's no contest at all. You only wish it would vanish, but it won't. There will always be people like me who will carry on using Microsoft because we prefer it. It's just a bonus that it irritates people like you.
      --
      "It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
  79. still dreaming. by twitter · · Score: 1

    Macthorpe reveals his motive for self torture:

    There will always be people like me who will carry on using Microsoft because we prefer it. It's just a bonus that it irritates people like you.

    Classic fanboy.

    AOL's web mail is probably the only way they can work with M$ mail clients, if anything from M$ ever works. Of course it's mediated by aol.com and none of those other sites or servers show up on the list, so what's your point again? That web use is dominated by M$ servers?

    Also, your little M$ hosting service also has another tab called "hosting" which offers the same features for less money. I'm not sure how they can continue offering M$ servers where everyone else doing the same lost their ass.

    Face it - non free is not competitive. M$ share is going to do nothing but shrink.

    --

    Friends don't help friends install M$ junk.

    1. Re:still dreaming. by Macthorpe · · Score: 1
      Troll, troll, troll.

      Macthorpe reveals his motive for self torture: The only torture here is your absence of understanding, brains or reason.

      AOL's web mail is probably the only way they can work with M$ mail clients, if anything from M$ ever works. Which shows a fundamental lack of understanding for how hosting actually works. Good job.

      so what's your point again? That web use is dominated by M$ servers? Did you get that from the part where I actually said '33% of the market'? I don't claim web use is dominated by MS servers. I merely pointed out that your claim that MS servers are unprofitable and anyone who uses them faces disaster was complete and utter bollocks.

      Also, your little M$ hosting service also has another tab called "hosting" which offers the same features for less money. I'm not sure how they can continue offering M$ servers where everyone else doing the same lost their ass. Because, again, you're lying and nobody lost their business (or in fact their buttocks) by hosting on an MS server. They wouldn't offer it if it wasn't profitable, simple as that.

      Face it - non free is not competitive. M$ share is going to do nothing but shrink. Who's dreaming now?

      Your comments start with a complete lack of understanding of how the market works and finishes with you telling lies that you can't hope to corrobate with a single fact.
      --
      "It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
    2. Re:still dreaming. by Anonymous Coward · · Score: 0
      You stupid retarded gip, he's just invalidating your dumb claims that "M$" is dying or whatever, but you need to interpret everything as defending Microsoft because otherwise the little dream just doesn't function well, does it?

      Why don't you do us all a really big favor and fuck off?

  80. ROTFLMAO by Anonymous Coward · · Score: 0
    By M$ hosting disaster I mean companies that tried to sell web hosting all bellied up

    Wow, all those companies offering Server 2003 hosting and doing great at it must be a figment of my imagination.

    Are you an actual retard or do you just play one on Slashdot?

  81. WXWdigets by hitchhacker · · Score: 1

    They renamed it WXWidgets.. and yes, it really is "super-cool". Especially with Code::Blocks and the new wxSmith stuff.

    -metric

  82. Nothing wrong with 3 year old computers ... by AHumbleOpinion · · Score: 1

    How many people use 3 year old PC's

    Most. Unless you are a hard core gamer with generous parents, or the less common job ;-), there is little reason to replace a 3 year old computer. Software apps and computers have exceeded the demands of general home and business users many years ago.