Slashdot Mirror


The Longhorn Dream Reborn

gbjbaanb writes "Early this month, Microsoft dropped something of a bombshell on Windows developers: the new Windows 8 touch-friendly immersive style would use a developer platform not based on .NET. Cue howls of outrage from .NET developers everywhere, but here Ars Technica describes what's more likely to have been going on and why Microsoft is finally getting its act together for developers."

254 comments

  1. Microsoft Obsoletes [Another] Developer Tool by Anonymous Coward · · Score: 0, Redundant

    Film at 11.

    Seriously, was it not expected at this point?

    1. Re:Microsoft Obsoletes [Another] Developer Tool by Anonymous Coward · · Score: 0

      Suck my longhorn.

    2. Re:Microsoft Obsoletes [Another] Developer Tool by xkuehn · · Score: 1

      And people ask me why I don't want to be a programmer.

    3. Re:Microsoft Obsoletes [Another] Developer Tool by Anonymous Coward · · Score: 1

      Say what you like about PulseAudio, OSS, and GTK/QT - when you write something for *nix, or more specifically for FOSS, it tends to have long-term viability.

    4. Re:Microsoft Obsoletes [Another] Developer Tool by hedwards · · Score: 2

      It's harder to obsolete a library when people can just fork it and keep on as they always were. Unfortunately, they're free to do so whether or not the new option is worse than the older one.

    5. Re:Microsoft Obsoletes [Another] Developer Tool by RightSaidFred99 · · Score: 2

      As opposed to all those MFC apps I wrote 15 years ago, which no longer work. Oh, wait... they do work.

    6. Re:Microsoft Obsoletes [Another] Developer Tool by carlzum · · Score: 1

      I wasn't expecting it, and I bet Windows 8 supports .NET applications in some manner when it's released. It's always been hard for MS to drop anything corporate customers rely on... VB, 16-bit apps, FoxPro. If they hope to put Windows 8 on business desktops, the lack of .NET support will be a major obstacle.

    7. Re:Microsoft Obsoletes [Another] Developer Tool by Eraesr · · Score: 2

      Did you even read TFA? The entire article is about how Windows 8 will not lack .NET support, nor native C++ support.

    8. Re:Microsoft Obsoletes [Another] Developer Tool by unencode200x · · Score: 1
      From TFA:

      "The point of all this? It gives parity to native C++ and managed .NET code. Instead of being separate, each with its own different capabilities and strengths, they will be peers. If Microsoft adds new APIs to core Windows, the WinRT system will ensure that they're seamlessly available to managed code, meaning that .NET developers will no longer be at a disadvantage relative to native ones. Conversely, existing native applications can be updated to use the new UI without having to be substantially rewritten to use .NET. This same flexibility applies to Microsoft: putting native and .NET code on an equal footing opens the door to actually seeing .NET applications shipping with the operating system."

      and

      "Far from being a developer disaster, Windows 8 should be a huge leap forward: a release that threatens to make development a pleasure for native, managed, and Web developers alike. The unification of the .NET and native worlds; the full hardware acceleration; the clean, modern APIs; Avalon as the primary solution for creating Windows UIs—this is what Longhorn's WinFX promised all those years ago, and this time around it looks like it might actually happen."

      --

      Chance favors the prepared mind.
      Perfect is the enemy of good.
    9. Re:Microsoft Obsoletes [Another] Developer Tool by gabebear · · Score: 1

      I think that's a pie in the sky idea; In reality .Net is getting marginalized. The only APIs I've seen that actually work between many different languages are ones that are mapped off of C APIs that don't have any object oriented ideas attached to calling conventions(e.g. OpenGL and SDL).

      API Parity for something like .Net-WPF/Java-SWT/C++-MFC/Javascript-HTML5-Canvas doesn't work when languages have different takes on object oriented paradigms(C++ is compile-time focussed with a rich inheritance model, Java/C# are runtime focused with much simpler inheritance, Javascript isn't even really object oriented). Microsoft had to bastardize the hell out of C++ to make it work with .Net (Managed C++).

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

    i love it when it's blatantly obvious you didn't read the article. i guess i shouldn't expect more from here though

  3. Re:So then, by airfoobar · · Score: 3, Funny

    Toss a few chairs and you'll get over it.

  4. Re:Not quite... by Z34107 · · Score: 5, Informative

    RTFA.

    Windows developers want to be able to build immersive applications, and they don't want to have to use HTML5 and JavaScript to do it. They won't have to. ... Far from being left behind on the legacy desktop - which was the impression that many took from the presentation - native C++ and managed C# will both be first-class, supported ways of developing immersive, touch-first, tablet-friendly Windows 8-style applications.

    --
    DATABASE WOW WOW
  5. Re:Not quite... by the+linux+geek · · Score: 0

    Sure I did. It can be summarized, roughly, as "Microsoft won't abandon developers because, uh, they won't. And the reason they've said nothing about native and .NET development is... hmm. BUT THEY'LL PULL THROUGH!"

  6. Standard modus operandi by mrsam · · Score: 3, Interesting

    If anything, we should be surprised that anyone's surprised. Whether or not TFA's theory is true, one thing is absolutely clear: .NET, like any Microsoft technology, has an expiration date.

    Anyone remember COM, VBX, and other MS-Windows technologies of yesteryear? Or the Visual Basic debacle of more recent vintage. For as long as I can remember, there's been a steady churn of Microsoft technologies, coming and going.

    Microsoft makes a lot of money from selling its development tools, documentation, etc... to its developer base. Microsoft simply runs the whole show. They are in full control, and call all the shots. And they understand perfectly well that if they keep the same technology platform in place, over time, they lose a good chunk of their revenue stream. That's why they have to obsolete their technology platforms, time and time again. They need revenue. It makes perfect sense. If you are a Microsoft Windows developer, one of your primary job functions is to generate revenue to Microsoft. Perhaps not from you, directly; maybe from your company. Whoever pays the bills for Visual Studio, MSDN, and all the other development tools. Maybe it's not you, personally, but it's going to be someone, that's for sure.

    So, perhaps this is the death knell for .NET. Perhaps not. If not this time, maybe next year. But it's inevitable. It's a certainty. If you are a .NET developer, your skills will be obsolete. If you were a COM developer, or a VB6 developer, your skills became obsolete a long time. I see no reason why .NET developers will escape the same fate. It's only a matter of time, but that's ok: all you have to do is invest some time and money to retrain yourself on the replacement Microsoft Windows technology, whatever it's going to be, when its time comes. But, it'll come.

    Originally I came from a Unix background. Many, many moons ago I explored the possibility of boning up on the MS-Windows ways of doing things. But, after a bit of some exploratory peeks and pokes, this became painfully clear to me; that whatever I learned, all of it was going go to waste, in its due time. And that was pretty much the end of my venture into the Windows landscape.

    Well, I'm happy to report that read(2), write(2), and all the other syscalls that make up POSIX, and its derivatives, still work the same as they did decades ago. Everything I have learned, as the sands of time have rolled on and on, I still put to good use today, and I make a pretty good living using them. Nothing has gone to waste. Honestly, this is more than I could say for my peers who practice their craft on MS-Windows. A lot -- not everything but a lot -- they learned decades ago is now completely and totally worthless to them, and to anyone else.

    So, whether Windows 8 is Longhorn reborn, as TFA says, or not, one thing can be said for certain. .NET is dead. It's just a matter of time. Good luck learning its eventual replacement. Of course, you understand that it'll be dead too, some years after that, of course; just keep that in mind, as you make your long term plans.

    1. Re:Standard modus operandi by exomondo · · Score: 5, Insightful

      I'm happy to report that read(2), write(2), and all the other syscalls that make up POSIX, and its derivatives, still work the same as they did decades ago.

      Great, so it's dead too since it hasn't changed for decades? Same as with COM, there's nothing stopping you from using it and it still works the same as it did many years ago. You can still use all the old technologies and they still all work just the same as they used to.

    2. Re:Standard modus operandi by David+Gerard · · Score: 4, Interesting

      Fortunately, free software means that Windows developers can use Win32 approximately forever! On WINE.

      I have a theory: like backups, no-one ever really gets the idea of free software until the lack of it has bitten them in the arse, good and hard.

      --
      http://rocknerd.co.uk
    3. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      Yeah .Net is dead. Don't know why people ever liked it, it has no wifi and less space then a nomad. Lame.

    4. Re:Standard modus operandi by RightSaidFred99 · · Score: 0, Troll

      How did this long, rambling, factually inaccurate glob of nonsense get modded up? .NET isn't going anywhere. You're just a UNIX dinosaur trying to blather on about how the primitive tools you write to develop primitive applications are so stable. Congratulations on that, btw. And I have no problem with UNIX, I just find the old school who never bothered to learn anything outside their little domain but still knock it to be risible.

      Here's a clue - you're not a fucking COM developer, you're a C++ or .NET or (other) developer who uses COM technology. Here's another clue - it's still around and you can use it if you want.

      I'm glad, though, you can spend 10X as much time writing an app in C/C++ and using (lol) your read(2) and write(2) calls.

      I'll be back to mock you in 10 years when .NET 8.0 is being released, btw.

    5. Re:Standard modus operandi by obarthelemy · · Score: 3, Informative

      You're kinda comparing apples and oranges: on the one hand, MS is trying to provide APIs, libraries features and tools for advanced, maybe even "innovative" features (maybe in misguided ways, but that's not my point), on the other hand, you list almost bare-metal APIs.

      As far as I know, these haven"t changed in Windows much either, but most devs simply don't use them.

      I'm fully aware that COBOL isn't dead either... It's just not where most of the jobs/money/action is, though I'm sure quite a few people are quite happy working in that space.

      --
      The Cloud - because you don't care if your apps and data are up in the air.
    6. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      You are comparing POSIX syscalls to application development frameworks. To be fair, most of the syscalls in Windows have not changed. Today you are still able to write an application in pure Win32, and it will work.

    7. Re:Standard modus operandi by WrongSizeGlass · · Score: 4, Interesting

      I have a client that has been dragging their feet about leaving their VB6 codebase running on an Access DB and migrating to .NET on MS SQL. Last week one of them saw the Microsoft announcement about 'HTML5 & JavaScript' and now they're afraid transitioning to .NET will be a dead end. Now they want to wait to see how Windows 8 will run their VB6/Access code. They have a lot of time invested in Office 2003 macros & Access code modules, but their DB is nearing the 2GB Access limit and their programmer is retiring in 6 - 12 months. They'll be running XP, Office 2003 & VB6 until they have no other options.

    8. Re:Standard modus operandi by Jahava · · Score: 5, Insightful

      Microsoft makes a lot of money from selling its development tools, documentation, etc... to its developer base. Microsoft simply runs the whole show. They are in full control, and call all the shots. And they understand perfectly well that if they keep the same technology platform in place, over time, they lose a good chunk of their revenue stream. That's why they have to obsolete their technology platforms, time and time again. They need revenue. It makes perfect sense. If you are a Microsoft Windows developer, one of your primary job functions is to generate revenue to Microsoft. Perhaps not from you, directly; maybe from your company. Whoever pays the bills for Visual Studio, MSDN, and all the other development tools. Maybe it's not you, personally, but it's going to be someone, that's for sure.

      So your argument is that Microsoft intentionally periodically obsoletes languages in order to make money? Am I reading this correctly?

      You do understand that:

      • Pretty much every commercial MS developer already has an MSDN license, which (minimally) gives them access to the latest development languages, SDKs, and tools.
      • Developing a new language that is at least as compelling as a current one is an expensive and non-trivial feat.
      • Obsoleting a language costs Microsoft a ton of money in rewriting their own software to create new APIs and then use them.
      • Each API and system rewrite introduces new bugs, costing Microsoft even more money identifying, patching, and being held accountable for.
      • One of the oldest MS-supported development languages, C++, has not been obsoleted.
      • One of the major issues with MS development is the legacy APIs that bias towards C++ functionality.

      I think your theory has some holes. Now, Microsoft has definitely obsoleted languages - Visual Basic for one (and good riddance) - but they did that because the language had shortcomings. I'd detail them but we have a nice article that already does that. The .NET framework and language stack, C# in particular, is on the same general level as Java: it is a language that more or less suits the needs of every platform developer. Why the hell would they want to obsolete that?

      No, languages aren't the issue with MS development, nor are they the theme of the article; frameworks are. A perfectly good language can be horrendous to use if it is unable to properly interact with its host environment to accomplish what it needs to accomplish. In this case (once again FTFA) C++ could interact worlds better with Windows than .NET could, and so .NET use suffered. This was an implementation failure on Microsoft's part. The article stipulates that Windows 8 intends to bring .NET back on-par with C++ as a development language, which (if true) means that it will be stronger than ever.

      It's also worth mentioning that in terms of accumulated skills and experience, learning a new language is trivial compared to truly learning a new framework. How you interact with the system and cause it to give you the resources and services that you want in the manner in which you want them is the heart of all modern systems programming, regardless of language. If Microsoft emphasizes .NET in their APIs, then .NET will be a viable Windows development platform; if not, then who knows? None of that reflects on the language itself, but rather on its appeal over other languages.

      Now, eventually every language will be obsoleted ... probably? I suppose we haven't been through that many generations of languages to know for sure, but that seems to be the case so far. There are various reasons languages die ... they suck, better ones come out, nobody likes them, no frameworks support them, or their target developer group gives up on it. .NET's main backer is cu

    9. Re:Standard modus operandi by guardiangod · · Score: 1

      It wouldn't kill you to actually read the article, you know.

    10. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      Not true. Allot of the programs need to be run in compatibility mode for a reason. Not to mention the development environment and so forth do not support it.

    11. Re:Standard modus operandi by Anonymous Coward · · Score: 1

      Originally I came from a Unix background. Many, many moons ago I explored the possibility of boning up on the MS-Windows ways of doing things. But, after a bit of some exploratory peeks and pokes, this became painfully clear to me; that whatever I learned, all of it was going go to waste, in its due time. And that was pretty much the end of my venture into the Windows landscape.

      Well, I'm happy to report that read(2), write(2), and all the other syscalls that make up POSIX, and its derivatives, still work the same as they did decades ago. Everything I have learned, as the sands of time have rolled on and on, I still put to good use today, and I make a pretty good living using them. Nothing has gone to waste. Honestly, this is more than I could say for my peers who practice their craft on MS-Windows. A lot -- not everything but a lot -- they learned decades ago is now completely and totally worthless to them, and to anyone else.

      Way to compare apples to oranges. .NET is a high-level framework... POSIX is an interface standard. You should be comparing POSIX to the Win32 API which has been around since the late 1980s and still works. Many programmers still make programs with it.

      And oh guess what, Windows has a POSIX subsystem that is compatible except for threads and sockets, or you can get the Microsoft Windows Services for UNIX download (built in to Vista/7 Ultimate) and have full POSIX compatibility.

      Also, I bet your peers learned many things that you cannot do in POSIX, like you know.. GUI applications... I suppose you never need to write any GUI stuff though, lucky you.

    12. Re:Standard modus operandi by Raenex · · Score: 1

      Microsoft makes a lot of money from selling its development tools, documentation, etc... to its developer base. [..] That's why they have to obsolete their technology platforms, time and time again. They need revenue.

      Tinfoil hat ranting. Do you have references to back this up? Microsoft makes the bulk of their money by selling Windows and Office. Do you think they actually want to drive developers away? Note that "Tools" sales are bundled into "Server and Tools", which includes things like SQL Server, so only a tiny portion of Microsoft's profit comes from selling tools, if any.

    13. Re:Standard modus operandi by sg_oneill · · Score: 2

      I think your sort of missing where .NET was targetted. In my view .NET was never intended to be a replacement to the native C interfaces (MFC, COM, etc) but rather as a way of taking on the Java market for servers and Delphi/VLC market for desktop development, and succeeded in it because Java (at least at the time) was utterly unsuited to agile high turnover development, and Delphi was being tragically mismanaged, priced out of the market and being ignored in favor of utterly wierd "middleware" frameworks that nobody cared about by borland. The evidence for this all is compelling. C# had a distinct "java-ness" to it, but seemed to avoid javas worst language sins. It did however include a dot net library that out-of-the-box contained a metric tonne of useful but easy to use libraries for enterprisey-servery sort of stuff (and especially so when the workflow and soap type stuff is thrown into the mix. There was also a lot of Delphis best manners thrown in as well including an exceptionally well balanced GUI editor and widget toolkit that blew the old VB one out the water. The dot net libraries had a distinctly VLC flavor to them and in fact where designed by the same guy who designed delphi.

      Delphi pretty rapidly disapeared from the mainstream, also aided by borlands ridiculous business and technical decisions (Many coders to this day hold Delphi 4 to be one of the most productive environments of all time, and later delphis to be complete messes) and Java is definately still around but arguably not the first choice anymore for doing dev on windows servers.

      Microsoft put the final dagger in on this by realising what made delphi both boom and then die. Delphi took off because a generation of coders where raised on Turbo Pascal, and around the time Delphi 4 came out, Borland started putting Delphi 2 for free on magazine covers (which a LOT of my old workmates started out on) , an open source hobbyist community built amazing libraries and components and this made development bitchin' fast. But borland started pricing updates at astronomical prices. I could never convince my boss to update our Delphi 4's to 5,6 or 7 (and by that point we'd moved to linux) because the prices where just astronomical. Many thousands to get the features we needed. And there was NO WAY to be a delphi hobbyist anymore.

      So microsoft comes along and basically gives dot net away. You could get free versions of vb.net and c# and whilst not totally suited to enterprise , where plenty good for hobbyists, and updating to a more enterprisey-suited visual studio (which included everything) really wasnt a huge hole in the pocket. And despite our suspicions that dot net would run like a dog compared to delphis highly optimized compiler (at one point it competed favorably with the intel C compiler) it actually ran more than good enough for pretty much everything except (at the time) high performance gaming (And to be honest, most high performance gaming was in C/C++ anyway, although I strongly suspect the old delphi compilers where infact up to the task)

      Dot net is a fantastic platform. Its just a shame I cant use it on my mac. Or for that matter its a shame I cant use Cocoa on a PC, thats a pretty fantastic platform too.

      --
      Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
    14. Re:Standard modus operandi by antifoidulus · · Score: 2, Interesting

      Your confusing implementation with interface. read and write's implementation has kept up with the times while maintaining the same interface. So to the programmer it doesn't matter if you are doing a read on a floppy or a wide scale distributed file system via the FUSE interface*, logically it's all the same. Furthermore, although the read and write interfaces haven't changed, there is absolutely nothing stopping you from developing new interfaces that run on top of these functions.

      Now compare that to Microsoft who constantly deprecates interfaces which means no new features are ever back ported, doesn't release new dev tools that are compatible with the old interfaces etc. There's a huge difference.

      * logically it doesn't matter, though obviously the more the programmer knows about whats going on in the black box the better.

    15. Re:Standard modus operandi by exomondo · · Score: 2

      Not true. Allot of the programs need to be run in compatibility mode for a reason.

      Because they are either unsafe or have been used incorrectly, so they get run in compatibility mode, but as i said they don't work any differently. Just the same as how apple worked in their technology transition phases.

      Not to mention the development environment and so forth do not support it.

      Of course the development environment supports it, are you sure you know what COM is?
      And what's the 'and so forth'? Is that just an attempt to pad out your argument?

    16. Re:Standard modus operandi by exomondo · · Score: 2

      Your confusing implementation with interface. read and write's implementation has kept up with the times while maintaining the same interface.

      Kept up with the times? So has Win32.

      Now compare that to Microsoft who constantly deprecates interfaces which means no new features are ever back ported

      Oh come on don't be obtuse, look at MFC, it's nearly 20 years old yet it still gets new features, it even got the new ribbon APIs.

    17. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      I maintain a COM addin for Outlook 2003 written in C. It has a companion service program also written in C and calls only Win32 APIs. I really doubt that I am the only one. How is COM dead?

    18. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      compare that to Microsoft who constantly deprecates interfaces

      yeah POSIX never deprecates interfaces...lol...

    19. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      He may be a dinosaur, but you're just too scared (or too stupid) to actually learn anything hard.
      Developer time isn't always the most important thing. Generally, the more important the application, the more important efficiency is.
      You're probably just gutted that the things you make every day aren't that important. They're just for small to medium sized businesses or home users. They're not very exciting.
      Shame.

    20. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      troll fail

    21. Re:Standard modus operandi by assertation · · Score: 1

      Of course the technologies still work, but does Microsoft support them? Does Microsoft update them to fit modern needs? Can you get as many jobs writing in them? Can you get jobs other than maintenance jobs in them?

    22. Re:Standard modus operandi by exomondo · · Score: 1

      Of course the technologies still work, but does Microsoft support them?

      Well ancient things like COM and MFC are still available in the latest VS and are still supported.

      Does Microsoft update them to fit modern needs?

      MFC is nearly 20 years old and got all the recent ribbon updates.

      Can you get as many jobs writing in them?

      I don't know.

      Can you get jobs other than maintenance jobs in them?

      Of course, you can't find any?

    23. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      Good luck explaining to your why 2GB is a limit now-a-days and in fact good luck to you, sir, explaining why their system which has worked perfectly well up till now is effectively redundant.

      Just to re-iterate, the solution you have been running for the past X years to the client's utmost satisfaction is now REDUNDANT.

      Int the software world there is (literally) no need to be redundant.

      I have spent some time working with MS technologies (MS Exchange was the worst offender) and this xGB limit is the way these motherfuckers sell you some other `solution`. My advice? Dump all your info into a free solution - MySQL would be my first suggestion. It will take you around one month (at the outside. In reality maybe around one day or even one hour)

      Once you are there, laugh at the artificial glass ceiling MS imposes on you and enjoy your freedom to operate.

      Really, this proprietary vs free software argument is getting old, when there *is* no argument in favour of the old, artificially crippled shite.

    24. Re:Standard modus operandi by bored · · Score: 2

      Many coders to this day hold Delphi 4 to be one of the most productive environments of all time

      I will buy that, in fact I would probably put it ahead of current .net platforms as well. Then there was C++ Builder which was basically delphi with ugly syntax. Either way, M$ started switching their API's to COM even before .net. That was the first major change in the M$ API churn. When that happened I pretty much started to write the native platform off because there wasn't any reason that those API's couldn't have been directly C callable with a COM wrapper. Then .net came out, and everyone was like WTF, and it constantly was lagging the platform (64-bit support was probably 1 year after the 2003 64-bit beta), and now with some of the win7 functionality. So it wasn't really a platform either, just a bunch of crap on the platform. Now this, which isn't particularly surprising, it was only a matter of time.

      The developer interest in iphone/android proves that there are developers out there looking for a platform to write apps on because M$ has pushed basically every group away at this point.

      I don't think I could consider writing a heavyweight application for a MS platform that I expected would have more than a 5 year life. I would probably end up using QT but I would seriously have to evaluate Lazarus.

    25. Re:Standard modus operandi by FrootLoops · · Score: 1

      What money does Microsoft stand to gain by not releasing IE9 on Windows XP? The most recent version of Visual FoxPro will also be supported through 2015. Asking a company to support old versions indefinitely is probably too much.

      Your post is essentially a rambling rant against "evil" Microsoft. I suppose that's why you posted AC...?

    26. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      That is, of course, until Microsoft decides nobody use them anymore, and will discontinue support.

      that's generally what you do when no-one uses something anymore, why support something no-one uses?

      Everything Microsoft does, it does for money.

      newsflash: companies exist to make money.

      Want a modern example? IE9. It won't work on Windows XP.

      and the latest version of safari won't work on System7 oh no!

      When us devs finally thought we could get rid of Microsoft's broken implementations of web standards, it drops the bomb on us. "Oh, we had to do it this way because of the accelerated graphics support". Accelerated graphics my ass.

      'Accelerated graphics my ass'? oh what a response.

      They did it for the money.

      yes so much money for accelerated graphics.

    27. Re:Standard modus operandi by MightyYar · · Score: 2

      You have a funny definition of "mainstream". Apache? Java? Firefox? Android? Linux? GCC? Hell, even the "closed" iPhone has free software at it's roots.

      Apple was able take a pre-written free kernel and FreeBSD and pop some proprietary shine on it and rival the largest software company in the world on the desktop, and hand them their ass in mobile.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    28. Re:Standard modus operandi by MightyYar · · Score: 2

      However, the article makes the point that Microsoft's .NET framework capabilities are increasing substantially, not decreasing. This speaks positively for its future.

      That's true if the desktop stays dominant. With C++, you can write desktop, iPhone, and Android apps (well, you need to learn enough Java/Objective C to do the interfaces)... so I guess if non-windows platforms take off, you might still see .NET wain.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    29. Re:Standard modus operandi by cecom · · Score: 1

      No, no, you don't understand. Microsoft does this because they care! Ask any Windows developer :-)

      Seriously though, objectively speaking, no matter how ridiculous this technology churn seems to us looking from outside of the Microsoft universe, it does keep people perpetually employed. It feeds not only Microsoft but a huge ecosystem of businesses, consultants, IT experts, MCEs, support stuff, technical book authors, administrators, etc. It is great!

      It may look inefficient, but if it was really inefficient, would it continue to exist and be successful in a market-driven economy? Well, of course market rules wouldn't apply if there was a monopolist in the room :-)

      Just to show how objective I can be, the constant API churn of the Linux kernel acts in much the same way. And it sucks.

    30. Re:Standard modus operandi by MightyYar · · Score: 1

      I maintain a COM addin for Outlook 2003 written in C. It has a companion service program also written in C and calls only Win32 APIs. I really doubt that I am the only one. How is COM dead?

      I'm risking a "whoosh" here... did you really just ask why your program written for an 8-year-old piece of software is considered... a bit dated?

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    31. Re:Standard modus operandi by 10101001+10101001 · · Score: 2

      The .NET framework and language stack, C# in particular, is on the same general level as Java: it is a language that more or less suits the needs of every platform developer. Why the hell would they want to obsolete that?

      No, languages aren't the issue with MS development, nor are they the theme of the article; frameworks are. A perfectly good language can be horrendous to use if it is unable to properly interact with its host environment to accomplish what it needs to accomplish. In this case (once again FTFA) C++ could interact worlds better with Windows than .NET could, and so .NET use suffered. This was an implementation failure on Microsoft's part. The article stipulates that Windows 8 intends to bring .NET back on-par with C++ as a development language, which (if true) means that it will be stronger than ever.

      It's funny you say that as I've always saw that as the Catch-22 of the .NET framework and why Java doesn't see as much widespread use on client systems. A major point of the .NET framework was precisely that it was a clean-slate, well designed system that could run on many platforms. In effect, .NET framework (like Java) became the platform and the major task to consider for the client was whether they could reasonably run that platform on the various hardware they had, be it a low-power (cpu and battery life) netbook or smartphone or a high end server.

      The obvious catch is, once you start introducing hooks into a specific platform, you start having problems. If you merely punt the work into the native API of one platform, you necessitate writing a lot of duplicate code on other platforms which tends to create a clear performance disparity as you've added an extra layer of redirection. More importantly, you in many ways are for the framework for some platform to faithfully duplicate all the quirks of another underlying API. Meanwhile, if you merely duplicate a near clone of one platform's API, you can mostly avoid the quirks issue but you balloon up the size and complexity of the framework and odds are good the result will be something less optimal than the original native API which discourages extant developers from moving to your new platform, especially when it lacks various functions, changes how things are done to be more consistent with some design vision, etc. Finally, this all tends to translate into a much larger framework as it moves less away from a clean design and more into providing for the wants and needs of the original native API developers which makes the whole framework less viable on lower powered devices, effectively limiting the real world application of the framework.

      Now, there have obviously been attempts to make these points less of an issue through the use of name spacing, sufficient fragmentation of the components of a framework, and the packing of micro frameworks that try to provide clean subsets of the framework that work well enough on even the tiniest of expected common hardware, but that still heavily relies upon the developer making the consideration to target that smaller subset of the framework and leaves the end user still stuck with the reality that only a major subset or the whole framework is enough to seriously run many applications.

      Personally, I don't see a way out of the fundamental problem. The only idea I can think to mitigate it is to have even more extreme fragmentation of name spacing and have the expectation of being able to stream only the needed components onto a device, effectively making a very custom micro framework library that's dependent heavily on the running applications and nothing more. I don't really know how viably that really is or if it'd have any real effect, either.

      PS - If not obvious, this is all my own armchair analysis of the situation and it's probably way off base.

      --
      Eurohacker European paranoia, gun rights, and h
    32. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      What a bunch of ignorant crap that you write just to vent your anti-MS (from your moms basement I assume?). I can trivially prove you totally wrong on many levels but many slashdotters already did so on their replies. Ive been coding professionally for over 20 years and continue using 20year old tech from MS that works fine (VC++ for example, which continues to get better every version). I also use .net and if you were to actually read the article you will see that .net will continue to exist just fine, except it will use a new unified API. thats great because .net developers can keep coding just as before and get the new api calls for free. I could keep going but you dont deserve a longer reply.

    33. Re:Standard modus operandi by Gadget_Guy · · Score: 1

      Anyone remember COM, VBX, and other MS-Windows technologies of yesteryear? Or the Visual Basic debacle of more recent vintage. For as long as I can remember, there's been a steady churn of Microsoft technologies, coming and going.

      Well COM is still used as the basic programming interface today. Look at one of the most recent additions to the Windows UI - the Ribbon. According to the Ribbon introduction on MSDN:

      "The Ribbon framework provides this flexibility by separating functionality from presentation with two distinct development structures: an Extensible Application Markup Language (XAML)-based markup language to declare controls and the visual layout of a Ribbon implementation, and C++ COM-based interfaces to initialize the framework and handle events at run time."

      And VBX? You want to lament a technology built for Windows 3.1 that got superceded by a technology that would be built-in to the OS for all programming languages in Windows 95, was 32 bit instead of VBX's 16 bit (did you really want Windows to stay 16 bit forever?), and is built with that the COM system that you just learnt is still actively in use 17 years later.

    34. Re:Standard modus operandi by Spykk · · Score: 1

      If Microsoft can come out with something new that is as big an improvement over .NET as .NET was over VB6 then I will happily spend the time required to learn it. Writing forms applications in C# is downright pleasant.

    35. Re:Standard modus operandi by Jahava · · Score: 1

      PS - If not obvious, this is all my own armchair analysis of the situation and it's probably way off base.

      Not at all; I totally agree, and the problem is systemic and probably not a bad thing. It's a simple consequence of choice and variety. Different people and companies will take different approaches to solve problems, while several developers may want to solve the same problem for all platforms. Everyone has to meet in the middle.

      There are several approaches to the problem. Some involve comprehensive frameworks (QT, Java/Swing, Java/SWT, .NET, Mono, and tons of others), there are attempts to enhance one language to the capabilities of another via bindings, and there are approaches to obsolete underlying systems with standards (like web browsers). There's no one-size-fits-all, and there really shouldn't be. What's important is that no one technology gets supported to the point where developers lose interest in the other (e.g., IE6).

      Frameworks are nice because you can learn to program for the framework, and then your code is more or less consistent across platforms. The problem is that then you lock your experience into that framework, and so your general development capability is constrained by that of the framework. But I suppose that's true for all tools. Metaphorically, you take having a shovel for granted when you garden, but there's an entire history of generations of people focused on inventing, refining, and developing that shovel. There's nothing wrong with that - it's a simple distribution of focus and responsibility. We build on each other, and programming is no different; it just starts from near-scratch more often and progresses more rapidly.

    36. Re:Standard modus operandi by afabbro · · Score: 1

      Everything I have learned, as the sands of time have rolled on and on, I still put to good use today, and I make a pretty good living using them. Nothing has gone to waste.

      Yeah, it's a snap finding those jobs supporting UUCP on Irix. Well, as long as they're COFF binaries and I can telnet or rsh into the box, it's not too bad. I just look at the K&R source with pcat.

      --
      Advice: on VPS providers
    37. Re:Standard modus operandi by CodeBuster · · Score: 2

      It's a certainty. If you are a .NET developer, your skills will be obsolete.

      I disagree. Having been in development for some time now, I've had ample opportunity to observe the various trends in programming and software development. The churn that was more characteristic of many previous technologies, going all the way back to the early mainframes from IBM and others, stemmed in large part from the close association between software and the hardware on which it ran. However, beginning with the rise and popularity of Java and continuing with .NET we see the increasing virtualization of the hardware; especially for main stream business and other large scale commodity software development. This ties in with the increasing use of server virtualization technologies, mobile and cloud (yes I hate that word too, but like it or not it has gained currency) computing. Indeed it's an understatement to say that the .NET framework is expansive; it's gigantic. It makes sense, therefore, for Microsoft to continue developing and adding to .NET, especially given its expansive and abstract nature, well into the foreseeable future. The technologies that you mention as predecessors of .NET were of a much more limited scope by way of comparison. Another interesting property of the .NET platform is that it's extremely promiscuous, borrowing and incorporating the best ideas from the languages and frameworks that preceded it and to which it certainly owes a debt. Why would Microsoft need or want to replace .NET when it easily incorporates anything and everything that has and is coming along?

    38. Re:Standard modus operandi by smash · · Score: 1

      If you think .net is going anywhere, you've got rocks in your head.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    39. Re:Standard modus operandi by smash · · Score: 2

      You realise .net is more than a language variant, and that .net objects are pervasive throughout the core of Windows these days - and that every administration tool has been rebuilt to work with Powershell cmdlets and .net objects?

      I love seeing anti-microsoft trolls who run decades old operating systems because they refuse to upgrade talking about how the new tech sucks or is being obsoleted because of reason X when its clear they have zero experience with current offerings.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    40. Re:Standard modus operandi by man_of_mr_e · · Score: 1

      Dude. It's VCL, not VLC. And Delphi (and it's retarded cousin, C++ Builder) were nice tools, but suffered from a major flaw. The component model was brittle, and required recompilation to change anything. COM and .NET have ways to extend components with multiple interfaces. VCL did not.

      This is why, when you look at Delphi and BCB components, you have to buy them for a specific version. This is not true of COM and C++ components.

    41. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      This is what you get for choosing Microsoft.

      Why not go for MySQL (or Postgres) in first place? Open solutions ftw.

    42. Re:Standard modus operandi by Lanteran · · Score: 1

      It's called a simile.

      --
      "People don't want to learn linux" hasn't been a valid excuse since '03.
    43. Re:Standard modus operandi by bmajik · · Score: 5, Interesting

      I am a Microsoft employee in DevDiv.

      (PS: Buy Visual Studio LightSwitch when it comes out! It rocks!)

      I will not comment on the accuracy of what is in the ars article, other than to say: I know the answers to some of the questions they are worried about, and the answers do not worry me and shouldn't worry you either (unless you're a competing non-MS technology, perhaps :))

      Regarding your post: I don't see how you'd conclude that .net is going anywhere from the article you supposedly read.

      First and foremost, you would need to be specific about what you mean by ".net" for your statement to even make sense. Are you claiming that C#, the language, is on an EOL path? Or the .NET runtime will no longer be a supported way of writing userland apps?

      Your claim that we intentionally obsolete developer technologies as some sort of money making scheme is hillarious. Have you worked in the commercial software industry before? Let me explain how it works.

      1) we spend a ginormous amount of money paying engineers to make something that we hope developers use.
      2) we figure out if its something we can even charge money for, or if we need to give it away so more people will develop for our huge money making platforms (Windows, SQL, Office, Sharepoint)
      3) when we have something we can give away / sell for a pittance, we start doing so
      4) this is when we might actually start getting money for our efforts.

      Now then, if our strategy was to make money at any cost, you'd think that we'd fire all of the engineers and keep selling licenses at the same price indefinitely.

      But as you've noted, our engineering staff moves on to new things and eventually the old things get phased out.

      We don't start working on new platforms because we need to figure out how to get more money out of existing customers. We work on new platforms because we think they'll be better than the old ones; that customers will like them more; that they'll provide more value to everyone. There are all kinds of features and products we'd LIKE to put out there in the real world but they all cost us more money to do. And as you've noted, everything we release causes someone to get upset if we want to stop supporting years later. For every one of these developer technologies we ship, we end up supporting it for years after we're not selling it (and thus not getting new revenue). Our support life cycle is a hell of a lot longer than Apples, or any of the for-pay Linux distros, for instance.

      Finally, regarding what a huge revenue stream deveopers tools are for us... I've never come across anyone in Windows or Office who is worried their project is going to be killed and their staff moved onto a _real_ money making project like the F# compiler :)

      Sure, DevDiv does great revenue compared to a lot of entire companies. But look who we're competing against. I'm not sure we've ever sold 300 million seats ever, counting everything we do. Windows does that _every release_.

      (nothing against the F# compiler guys. I just picked something :))

      --
      My opinions are my own, and do not necessarily represent those of my employer.
    44. Re:Standard modus operandi by Anonymous Coward · · Score: 1

      What money does Microsoft stand to gain by not releasing IE9 on Windows XP?

      It could force people to upgrade to Windows 7 (which involves Microsoft getting more money) rather than using the old Windows XP they already have.

    45. Re:Standard modus operandi by Malc · · Score: 1

      What are you talking about? COM is far from dead, and still represents a very important core technology on Windows. It's very mature now, even though it doesn't get nor need much hype or attention. It's a language neutral binary spec that has lasted the test of time. In fact I've used it on two projects this year already because it seemed the easiest and quickest solution to either exposing a .Net assembly to a native C++ app, and for providing a 64-bit app access to a 32-bit DLL that can't currently be ported.

    46. Re:Standard modus operandi by inglorion_on_the_net · · Score: 2

      I'm happy to report that read(2), write(2), and all the other syscalls that make up POSIX, and its derivatives, still work the same as they did decades ago.

      Great, so it's dead too since it hasn't changed for decades?

      Why would you think that? We still have files with bytes in them, pipes, sockets, and all the other things these system calls work on. And since we're still working with the same concepts, and we have a good API for them, why would we want to change the API?

      Same as with COM, there's nothing stopping you from using it and it still works the same as it did many years ago. You can still use all the old technologies and they still all work just the same as they used to.

      That may be true for COM, but is the same true for ActiveX, VBA, or DirectX? I've worked on an app for a mobile device that was developed in Visual Studio 2008, that would compile in no other version of Visual Studio. Apparently, Microsoft introduced APIs in one version of their flagship development environment and removed them in the next.

      I am not saying everything is doom and gloom with Microsoft, but they certainly do kill off support for some of their previously promoted APIs sometimes. To avoid any misunderstandings: I am not saying this is a bad thing, just that it happens.

      --
      Please correct me if I got my facts wrong.
    47. Re:Standard modus operandi by Spad · · Score: 3, Funny

      The 2Gb Access Database limit is nature's way of telling you that you should never have used Access for anything in the first place.

    48. Re:Standard modus operandi by WrongSizeGlass · · Score: 1

      This is what you get for choosing Microsoft.

      Why not go for MySQL (or Postgres) in first place? Open solutions ftw.

      Their solution pre-dates my arrival. In fact, it goes back to the late 90's. They've been even less receptive to a non-Microsoft solution, such as browser-based app using PHP/MySQL (their data and workflow would work nicely with this approach). It's my job to look out for my client's best interests, so anything that would get them off Access would be a progress whether or not it's MySQL or MS SQL.

    49. Re:Standard modus operandi by terjeber · · Score: 1

      You should never open your mouth and give strong opinion on things you are just guessing about. Your sentences were grammatically correct but contain no real information. Please stop using your deranged fantasy as a source for "facts".

    50. Re:Standard modus operandi by terjeber · · Score: 1

      Goodness. So much fantasy. So little fact.

    51. Re:Standard modus operandi by terjeber · · Score: 1
      • does Microsoft support them? - Yes
      • Does Microsoft update them...? - Yes
      • Can you get as many jobs writing in them? - Yes
      • Can you get jobs other than maintenance jobs in them? - Yes

      Any further questions?

    52. Re:Standard modus operandi by bloodhawk · · Score: 1

      You might want to actually read the full article, as usual the slashdot summary is full of shit. The only thing Microsoft announced was that you could use HTML5 and java script for the new interface, they are adding to .NET not dropping or reducing its use. If you read the full article their was no actual bombshell at all, just sensationalist journalism for the article title. obviously your client never bothered to read past the opening paragraph either so it can't have been much of an issue for them if their project wasn't even worth reading for a few minutes to see if their was any substance to what they saw.

    53. Re:Standard modus operandi by gbjbaanb · · Score: 1

      If you'd read TFA you'd realise that .NET is *not* pervasive throughout the core of Windows. WinDiv doesn't like .NET and the only windows app that is written in.NET (Windows Media Center) doesn't use the GUI bits anyway.

      The big reason about running old systems is that they work, the bugs have been found and stomped on. now, sure there's always some churn in rewriting systems when they need to be rewritten due to massive changes in requirements, or too much evolving of the existing codebase having taken place, but that's an entirely different position than having to rewrite just because Microsoft says you have to. New tech always sucks, its in its nature. It takes a while for it to settle down, the 'features' to be found and updates applied to make it work properly. Or we'd obviously still be using .NET 1.0

      the other issue about new tech sucking is that, as things stand today, it sucks because it will be too-quickly replaced. Why bother learning Java when .NET is coming out, why bother learning .NET/WPF when Win8 APIs are coming out. You might as well stick with the old reliable ways until you need the new.

    54. Re:Standard modus operandi by Kamiza+Ikioi · · Score: 1

      I rather thought free software means they could abandon Windows altogether, forever.

      --
      I8-D
    55. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      (PS: Buy Visual Studio LightSwitch when it comes out! It rocks!)

      Oh, hell no!

    56. Re:Standard modus operandi by Dog-Cow · · Score: 1

      You do not know what redundant means.

    57. Re:Standard modus operandi by unencode200x · · Score: 1

      We're talking about Microsoft here. They've always gone through great pains to allow backwards compatibility. Windows 8 will be no different.

      Just last week I took a 10 year old app written in VB, *copied* it to windows 7 and it fired right up and worked perfectly.

      --

      Chance favors the prepared mind.
      Perfect is the enemy of good.
    58. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      Which one? Are you sure it wasn't some library you were using? I've not seen that behavior with native .NET classes.

    59. Re:Standard modus operandi by unencode200x · · Score: 1

      I've supported some of these homebrew Access frankenstein "apps" after the original "developer" is long gone. "Utmost satisfaction" is not how I would describe users' experience.

      --

      Chance favors the prepared mind.
      Perfect is the enemy of good.
    60. Re:Standard modus operandi by Dog-Cow · · Score: 1

      Dated != Dead.

      COM is not dated. It's still a good component model, and has been supported by MS ever since its introduction.

    61. Re:Standard modus operandi by David+Gerard · · Score: 1

      As the Wine FAQ points out, there's a billion lines of Windows code out there that isn't going away; and one of the really important functions for Wine is to run that "just one app" that keeps you stuck on Windows.

      This is not just a hypothetical consideration. My previous workplace dealt with digital TV, which means dealing with proprietary vertical-market software running only on Windows; in one content chain, we ran the compiler piece on Wine (where it ran flawlessly) rather than commission yet more Windows boxes and try to hook them into the middle of an otherwise-Linux chain. The result was functionally superior in every way. Wine is quite up to commercial production use involving proper money.

      --
      http://rocknerd.co.uk
    62. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      COM, VBX, and other MS-Windows technologies of yesteryear? Or the Visual Basic debacle of more recent vintage.

      Not that I am happy about it but all of those technology stacks are still very much alive.

    63. Re:Standard modus operandi by MightyYar · · Score: 1

      LOL, I know but you see the humor in pointing to your Office 2003 project as a contemporary example in the year 2011...

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    64. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      This is absolutely FUD. The Windows API hasn't changed significantly in the past ten years. There are a few different conventions and it got a rename, but other than that it's almost exactly the same. The system calls on Windows work exactly the same as they used to. Everything I learned years ago still applies today.

    65. Re:Standard modus operandi by godefroi · · Score: 1

      It's funny you say that as I've always saw that as the Catch-22 of the .NET framework and why Java doesn't see as much widespread use on client systems. A major point of the .NET framework was precisely that it was a clean-slate, well designed system that could run on many platforms. In effect, .NET framework (like Java) became the platform and the major task to consider for the client was whether they could reasonably run that platform on the various hardware they had, be it a low-power (cpu and battery life) netbook or smartphone or a high end server.

      You know that C#/.NET (as well as Java) run on some pretty tightly constrained hardware platforms, right?

      --
      Karma: Poor (Mostly affected by lame karma-joke sigs)
    66. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      I am a Microsoft employee in DevDiv.

      (PS: Buy Visual Studio LightSwitch when it comes out! It rocks!)

      ...

      I think that sales pitch right there completely erodes any credibility you would have had to refute the GP's claims.

    67. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      You can make Access use the MS SQL server without changing any of the programming which should alleviate the 2GB limit of MS Jet DB. I realize that you are rightfully trying to make them change based on this, but there is a solution within easy grasp.

    68. Re:Standard modus operandi by yarnosh · · Score: 1

      I know I've only been a professional programmer for a few years, but all I can say is that I hope I don't end up using one framework and one language for the rest of my career. That would be awful. Doesn't it kind of depend on what level you're working at? SUre, if you're working at the system level or lower (kernel), you might need tried and true methods like read() and write() that dont' change, but at the higher, application level, shit changes. While I don't think you should necessarily jump to the framework du jour the day it is released, what's really so bad about moving to a new language and/or framework ever X number of years, if only for a change of scenery? Do you really need that kind of stability/longevity or are you balking at the fact that you don't have control over when a a framework is depreciated?

      Also, just because a vendor depreciates a framework doesn't mean you have to stop using it. I could be wrong, but it seems to me that most applications on Windows doesn't even use .NET at all. Developers are still writing stuff in C++ using MFC on WIndows and targeting Windows XP.

    69. Re:Standard modus operandi by ckaminski · · Score: 1

      Someone suggested it above - you can use any linked ODBC database to access data from Access. You could easily move that data into a PostgreSQL database and be all set. Unless of course you have multiple copies of this Access database running around - then you might have consistency and security issues you need to worry about.

    70. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      You say that MS obsoleted VB and you say "good riddance" and that it "had problems".

      When I said this in 1999, that VB had many problems, all the then MS fan boys, said that I was wrong and VB was the future, and MS WOULD NEVER STOPPED supporting VB.

      They were wrong, according to YOU, and YOU are also wrong now.

    71. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      I am a Microsoft employee in DevDiv.

      The vast majority of programmers/people are not. So spare us the blunt advertisement.

      we figure out if its something we can even charge money for, or if we need to give it away so more people will develop for our huge money making platforms (Windows, SQL, Office, Sharepoint)

      Exactly. That is why Microsoft is a convicted monopolist, even by American law. By what you say, they should be convicted again and again. I doubt that it will happen though, in this era that obamaism rules (it rules even slashdot).

      when we have something we can give away / sell for a pittance, we start doing so

      And what might that be? What of value has MS given away? And what is "a pittance"? Is it, let us say, $199 for each of the 20 or so computers I administer in a tiny company? Thanks for the generosity but I am not buying. By the way, I also give away my old Amstrad 1640PC (it can run DOS! it has 640KB memory; it ought to be sufficient for anyone!). Or I might charge a pittance $99 for it.

    72. Re:Standard modus operandi by guanxi · · Score: 1

      I am a Microsoft employee in DevDiv.

      The vast majority of programmers/people are not. So spare us the blunt advertisement.

      Huh? It sure seems like an essential, valuable thing to say. It would be a little shady if he didn't reveal it.

    73. Re:Standard modus operandi by exomondo · · Score: 1

      Why would you think that? We still have files with bytes in them, pipes, sockets, and all the other things these system calls work on. And since we're still working with the same concepts, and we have a good API for them, why would we want to change the API?

      That's exactly my point, just because it hasn't changed doesn't mean it's dead.

      That may be true for COM, but is the same true for ActiveX, VBA, or DirectX? I've worked on an app for a mobile device that was developed in Visual Studio 2008, that would compile in no other version of Visual Studio. Apparently, Microsoft introduced APIs in one version of their flagship development environment and removed them in the next.

      There could be many reasons for that, and by exactly the same token there are plenty of libraries on unix-like OSes that will only compile with a certain version of gcc and will not build with later versions.

      I am not saying this is a bad thing, just that it happens.

      Fair enough, but my point is that it's not just an MS thing, POSIX deprecates APIs, Khronos deprecates APIs, some software will build only with certain versions of gcc because they aren't compatible...it happens.

    74. Re:Standard modus operandi by Anonymous Coward · · Score: 0

      You know, a "P.S." is supposed to go at the end of a letter/post/comment, if you can't get that right it doesn't give me much faith in anything else you do.

  7. Re:So then, by RightSaidFred99 · · Score: 5, Interesting

    They're not dropping Silverlight or .NET. Try to pay attention. Nobody with any sense ever thought they were going to, but the usual suspects took every opportunity to make a "Durr hurr, Microsoft screwing over developers" thing out of it when there was no indication whatsoever this would happen.

    Nobody sane wants to develop large applications in fucking native JS and HTML5, and Microsoft knows that.

  8. PulseAudio - indeed by unity100 · · Score: 3, Interesting

    im somewhat of an audophile, and despite i have been using windows xp with extra software like srs audio sandbox (cryztalizes and clears sounds) and a good sound card (original x-fi x-treme music, from the production batch which got the good chips) with crystallizer and so on, on top of an altec lansing fx6021 speaker set (in-concert array microdrives totaling 12, crystal clear) for a long time,

    i was dumbstruck with the audio quality pulseaudio + x-fi x-treme music + audacious media player with crystallizer plugin gave, when i switched to linux.

    now im switching to linux every time i want to listen to music in high quality.

    1. Re:PulseAudio - indeed by Anonymous Coward · · Score: 1

      most audiophiles prefer unaltered streams.. there is no 'crystalizer' support for xfi under linux.

    2. Re:PulseAudio - indeed by PopeRatzo · · Score: 1

      now im switching to linux every time i want to listen to music in high quality.

      If only there were similarly good tools for professional music production in Linux. It's getting there, but not yet.

      Though as I've written before, there's definitely a place for Linux in the studio. Especially with Cockos' Reamote.

      --
      You are welcome on my lawn.
    3. Re:PulseAudio - indeed by petteyg359 · · Score: 2

      The terms "audiophile" and "cryztalize" don't go together. Not even if you spell crystallize (or crystallise for the silly country) correctly.

    4. Re:PulseAudio - indeed by unity100 · · Score: 1

      criyztalizea is better than listening to crap that went through dynamic range compression.

    5. Re:PulseAudio - indeed by Stuarticus · · Score: 1

      Ardour is pretty incredible for OSS.

      --
      If you think someone isn't free to have a different definition of "freedom" you may be a tyrant.
    6. Re:PulseAudio - indeed by dave420 · · Score: 1

      When you don't have to qualify that claim with "for OSS", you'd have something.

    7. Re:PulseAudio - indeed by fuzzix · · Score: 1

      criyztalizea is better than listening to crap that went through dynamic range compression.

      Haha, you say that as if compressors haven't been around for decades. Have you ever heard a Frank Zappa record?

    8. Re:PulseAudio - indeed by Anonymus · · Score: 1

      You are repeatedly claiming that, as an audiophile, you listen to horrible recordings and then try to artificially clean them up.

      The reason everyone keeps arguing with you is because that makes no sense. Why not just choose recordings that actually sound good to begin with instead of trying to polish turds?

    9. Re:PulseAudio - indeed by unity100 · · Score: 1

      im at a loss to understand. it is because of the very fact that compressors were around for decades, we need crystalizers. crystalizers try to amend the audio range lost by compressors by expanding on those ranges.

    10. Re:PulseAudio - indeed by unity100 · · Score: 1

      i said i am SOMEWHAT of an audophile. i dont have $4000 to sink on a lamp amp.

    11. Re:PulseAudio - indeed by Stuarticus · · Score: 1

      For OSS audio software? It's better than SADiE which I have to use regularly and look what that costs.

      --
      If you think someone isn't free to have a different definition of "freedom" you may be a tyrant.
  9. Re:So then, by exomondo · · Score: 2, Insightful

    You'll never find a shortage of people who will take anything they can to shout about how microsoft is screwing everyone (these days it's often done with Apple too). Seriously this is entirely based on the fact that they announced that the apps they showed were based on HTML5 and Javascript, yet from that you end up with morons shouting 'MS are killing silverlight and .Net!!!'.

  10. Database Filesystem? by Anonymous Coward · · Score: 0

    Call me when they start talking about that again. The one thing Microsoft stringed me along for so many years... it'll be in the next version we promise!

  11. Re:So then, by MightyMartian · · Score: 3, Funny

    You mean that rumor I heard about Steve Ballmer turning tricks in Bellingham are false?

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  12. Re:Not quite... by RightSaidFred99 · · Score: 3, Insightful

    No, because they looked at Windows 8. And because anybody who's not, literally, mentally defective knows Microsoft isn't going to abandon .NET. You have to be a little smarter (say, 105 IQ) to know they're not going to abandon Silverlight, so I'll cut you a little slack there.

    The idea is ridiculous. You seriously think people are going to write complex end user and enterprise apps in JS/HTML5? Seriously?

  13. Re:So then, by exomondo · · Score: 2

    You mean that rumor I heard about Steve Ballmer turning tricks in Bellingham are false?

    I wouldn't go that far ;)

  14. Not necessarily a good thing.. by Junta · · Score: 2

    The thing about talking about something so significant in highly abstract terms is you'll tend to imagine it doing precisely what *you* think the words mean and how you think a vision could be realized.

    Then, when you actually get to touch it, you realize their vision either isn't the same as yours, or even if it matches what you had in your head, in practice it won't work out so well.

    The ultimate end-user filesystem experience hasn't changed in years for good reason. Any generic approach is going to be fraught with too much work to bother. Sure, Music, Video, Document, etc applications could use the filesystem as a standardized way to store metadata instead of proprietary databases here and there, but much of the time a file containing data is a shared thing in a central place, with much of the pertinent metadata a user caring about specific to their view, making combining that data in the filesystem awkward. Notably some permament attributes (that should go with the file on transfer so it can't just exist outside the file) like title, release year, etc exist that are global in nature, but personal tags, ratings, bookmarks, etc just don't mesh.

    --
    XML is like violence. If it doesn't solve the problem, use more.
    1. Re:Not necessarily a good thing.. by bored · · Score: 1

      If your just talking about file meta data. NTFS as had extensible attribute (basically meta data) on files since at least NT 3.51 (maybe earlier). Plus the alternate file stream system would basically allow any application (aka backup applications, media applications, shell replacements whatever) to extend the concept in any way they wanted.

      None of this is new, when I heard about the database filesystem back in 2002/2003 I though WFT, someone at M$ doesn't even know what their current filesystem is capable of. Nothing they were listing wasn't possible with just minor shell tweaks and a couple standardized api's on the existing filesystem. Plus, the whole thing strikes of a fundamental misunderstanding of how OS's manage resources and the fairly tight integration between a filesystem and the virtual memory subsystem in every modern OS.

      Sure the concept of a database and a filesystem are pretty similar, in fact you can often substitute one for the other. Its a matter of what the data storage engine is optimized for. Database are optimized to speed up searching and modifying small records of a predefined length. Filesystems are optimized to minimize data access latencies on hierarchical pieces of data that are constantly growing and shrinking.

      In fact writing a filesystem that backs its data in a database would be fairly easy. I could probably write a linux FUSE plugin to talk to sqllite in under a week. Making it work well would be another matter.

  15. all of it was going go to waste by nurb432 · · Score: 2

    Originally I came from a Unix background. Many, many moons ago I explored the possibility of boning up on the MS-Windows ways of doing things. But, after a bit of some exploratory peeks and pokes, this became painfully clear to me; that whatever I learned, all of it was going go to waste, in its due time. And that was pretty much the end of my venture into the Windows landscape.

    I have to disagree, as anything learned is an advantage you can leverage in future learning.. Also, during the time that 'xyz tech' is in vogue, you are employed and making money from it.. that's not a waste in my book..

    --
    ---- Booth was a patriot ----
  16. Re:Not quite... by segedunum · · Score: 3, Informative

    Unfortunately the article doesn't explain how they arrived at that conclusion other than it being their own opinion and possibly their own wish. That whole Longhorn WinFX finally coming to reality thing is another opinion piece. We heard many similar stories for Cairo many moons ago and that whole object oriented operating system rubbish around Windows 2000.

  17. Re:Not quite... by sortius_nod · · Score: 1

    The way I see it is that MS is trying to push toward an easy interface for creating apps, while still leaving "legacy" languages functioning. It's a good sign really, there's a lot on the wind about where iOS will be headed. While Apple may not be able to beat MS at raw market penetration, iOS has shown that you can decimate market leaders by simplifying application development, delivery and accessibility. Look at Nokia, at one stage they almost owned the mobile market, now they have lost almost all their market power.

    If MS can pull this off by streamlining mobile, tablet & desktop development I am betting we'll see a final clash of the titans between Apple and MS. At the moment it's just a bit of a dance around each other, will be a great fight to watch.

  18. RTFA by darkwing_bmf · · Score: 5, Informative

    The article says windows is getting a new API, WinRT, which is a modern version of Win32. .NET and C++ development will both be updated for WinRT and have the same capability as each other so you can work in the environment you choose. Silverlight is supported, updated and renamed (codenamed?) Jupiter. Some other new things were added. In summary, .NET developers, you're getting new functionality. C++ developers, you're getting new functionality. Plus it will be easier than ever to go back and forth between the two because, underlying it all, is a new unified API.

    1. Re:RTFA by Punkster812 · · Score: 1

      Thank you. I thought I was the only one. Why so many people thought Microsoft would simply drop .NET so quickly is beyond me. But I guess it's more fun to freak out first.

    2. Re:RTFA by HyperQuantum · · Score: 1

      So they're adding another layer of abstraction? Reminds me of a quote somewhere...

      --
      I am not really here right now.
  19. Re:Not quite... by exomondo · · Score: 1

    It solves the architecture-compatibility issue easily enough, but there are serious limits in what currently exists as "HTML5 and Javascript" (lack of threads, performance, etc) that make this a potentially very bad decision.

    What decision? They aren't 'moving developers' to this platform, all i've seen is that they have a new development platform - clearly not as technically capable as their multiple existing development platforms - based on HTML5 and Javascript.

  20. Re:So then, by Anonymous Coward · · Score: 1

    +1 to this, some of the tards crying on linkedin was priceless

  21. Re:Not quite... by postbigbang · · Score: 2

    The whole idea is to confuse you, so that you won't jump ship, and the ______ that you use now will kinda sorta be ok, and hey, imagine stuff working from phones to tablets to notebooks to desktops, any of which could have a cool GPU to do stuff, and you can maybe sorta use your old code.

    Got it? Great. Logon now. Please. Pretty Please. HTML5! Java! You're a FOSS guy, right? You like that Java stuff! We promise not to fork it! Not like that stuff that's in court facing a huge settlement with Oracle, right? C'mon, please???

    --
    ---- Teach Peace. It's Cheaper Than War.
  22. Another Summary by FrootLoops · · Score: 1
    Peter Bright, an Ars Technica contributor, writes that

    Early this month, Microsoft dropped something of a bombshell on Windows developers: the new Windows 8 touch-friendly immersive style would use a developer platform not based on .NET, which Microsoft has been championing for the past decade. Instead, it would use HTML5 and JavaScript.

    But he doesn't believe the alarmist hype:

    Windows developers want to be able to build immersive applications, and they don't want to have to use HTML5 and JavaScript to do it.

    They won't have to. Want to write an immersive application in native C++? That's cool. Want to use C# and Silverlight? That's cool too. Both will be supported. Far from being left behind on the legacy desktop—which was the impression that many took from the presentation—native C++ and managed C# will both be first-class, supported ways of developing immersive, touch-first, tablet-friendly Windows 8-style applications.

    (Feel free to write another, better summary. The one given is just completely inadequate for such a long article.)

    1. Re:Another Summary by shutdown+-p+now · · Score: 2

      For that matter Peter Bright is wrong, whether he believes the hype or not, because there was no bombshell to begin with. At no point it was said that "the new Windows 8 touch-friendly immersive style would use a developer platform not based on .NET". The only thing that was said is that you will be able to develop for Windows 8 using HTML5 & JS. A few people took the latter to imply the former, and published stories where said implication was treated as plain fact - like the one mentioned in TFA - and from there the hysteria took over.

      As usual, if you want to know what's actually going on, stick to the primary sources - in this case, Win8 presentation videos. And they say: 1) There will be HTML5/JS, and 2) Full dev story will be told on BUILD in September. That's all there is to it for now.

  23. So what's better? by Anonymous Coward · · Score: 1, Insightful

    Currently I am working in a software project that is cross platform with Mac and Windows. I alone do the WPF/.Net side of things, a few other guys work on the Cocoa side of things. I am getting really tired of hearing them complain that it is hard or even impossible to create a rich and custom UI experience on OS X because of the lousy tools and development platform Apple offers. The Mac product is full of bugs and is about a good month behind on parity, and this is with 2 guys working on. I am sure they are equally tired of hearing me tell my project manager that I have just finished whatever feature they dreamed up of using WPF and .Net. Bottom line is, there is something wrong with a person or developer that prefers constant headaches and lack of productivity over something that offers rapid development, quality code, and ability to develop a rich applications without limitations. I should mention there is a small team looking to port to Linux and they are so lost they are at least a year behind to even reach parity with the Windows version.

    I know everybody hates Microsoft at Slashdot, but you don't know sh*t about f*ck when it comes to software development if you are bitching about how bad C# or .Net or WPF is for developing applications. Bottom line is I get paid to develop software for Windows, and I can do it quickly, easily, and have a lot of fun doing it, but if I had to use the OS X or Linux tools for developing software, I would probably shoot myself.

    1. Re:So what's better? by NerdENerd · · Score: 2

      So why did this post get a zero rating? I am a .NET developer and agree 100%. Visual Studio 2010 is a fantastic development experience. I tried to do some iPhone development and hated XCode on the Mac. Objective C seems like going back in time. Why would I give up my managed environment and want to worry about de-constructors and managing resources. Anyone who criticises .NET development has probably never done any.

    2. Re:So what's better? by gr8_phk · · Score: 1

      So if they knew they wanted a cross-platform product, why didn't your company select tools that work on all three platforms? For cross-platform GUIs there is ummm QT, GTK and wx. OK, wx is a wrapper but in some ways that's actually better because it uses native widgets. All three work on all 3 OSes you mentioned. Don't think your .net is better than what your MAC coworkers are doing - the company wants a cross-platform product and your chosen tool doesn't provide that - in fact, it hurts by not being common to all 3.

    3. Re:So what's better? by mswhippingboy · · Score: 1
      Cross-platform? Lol... just when I think I've heard it all.

      I wonder what kind of idiotic apps manager would say - Hmmm we need an application that runs on Windows, Mac and Linux. What tools should we use? - I know - three development teams developing completely separate apps using completely separate languages and tool chains!!! Brilliant!

      I guess someone failed to tell him there are cross platform tools that would allow the app to be developed once and deployed to all platforms.

      but you don't know sh*t about f*ck when it comes to software development if you are bitching about how bad C# or .Net or WPF is for developing applications.

      You post would suggest that maybe you and/or your management are the ones who "don't know sh*t about f*ck"

      --
      Sometimes the light at the end of the tunnel is the headlight of an oncoming train.
    4. Re:So what's better? by mini+me · · Score: 2

      So why did this post get a zero rating?

      All Anonymous Coward posts default to 0.

      Why would I give up my managed environment and want to worry about de-constructors and managing resources.

      Cocoa's evolution goes way back to the early 80s, so it does have some cruft. However, Objective-C on the Mac has included garbage collection for quite a long time. Managing resources is really a non-issue in the parent's case.

      What I find most interesting about Cocoa is how many recent projects have been inspired by the API. Cappuccino, SproutCore, and SNAP to name a few. While I personally have nothing bad to say about Windows development on .NET, I do find it interesting that nobody has really adapted the API outside of Windows. Mono does to some extent, but typically use their own frameworks where compatibility is not needed.

    5. Re:So what's better? by SoupIsGoodFood_42 · · Score: 1

      Does the Mac version have a different design spec, or is it about trying to offer as similar experience as possible on both platforms?

    6. Re:So what's better? by Anonymous Coward · · Score: 0

      It sounds like you have shitty Mac and Linux devs. I can't tell with the information provided whether you are also a shitty Windows dev, because .NET makes it easy for idiots to churn out crap.

      Maybe your shitty Mac and Linux devs should be churning out crap in Java instead.

    7. Re:So what's better? by FrootLoops · · Score: 1

      So if they knew they wanted a cross-platform product, why didn't your company select tools that work on all three platforms?

      Who says they knew they wanted a cross-platform product? Maybe the program started as Windows-only. It's unclear what decisions went into their current split development and whether or not they were poor ones.

      Don't think your .net is better than what your MAC coworkers are doing

      You didn't support this statement (which I'm actually interested in, as I've never developed for a Mac)... you just said that .net isn't cross-platform so is worse than the cross-platform GUIs you mentioned.

    8. Re:So what's better? by SuperKendall · · Score: 1

      I'm not sure why this is but frankly I find IB to be the best UI development tool I have ever used (including VS), I'm not sure what problems your developers are running into with it.

      C# and WPF are nice, but you are off base with thinking Mac development is so hard or even much behind VS...

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
    9. Re:So what's better? by bongey · · Score: 0

      Food for thought . You are the type of programmer they will outsource to India. You have no real skills, you are a MSDN copy, paste coder, nothing more.
      I work for a very,very large MS shop(department) everyone loves VS. We have more than 100 devs in are department, and I code circles around every SINGLE ONE of them. Even when fixing their problems in their Windows only apps, visual studio, shit projects.
      Funny thing is all the really , really productive/ good programmers at my company outside of my group, there favorite editor is
      VIM , Yes fucking VIM
      VIM >> VS .

      I would bet you still code with your mouse .

    10. Re:So what's better? by smash · · Score: 1

      No garbage collection on iOS. But thats not Cocoa's fault as such, its a design decision to minimize overhead on the memory/cpu constrained i-devices.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    11. Re:So what's better? by mini+me · · Score: 1

      Very true, but the original parent was talking about Mac development. Also, iOS has ARC now, which is not a whole lot different than GC from the developer's perspective.

    12. Re:So what's better? by inglorion_on_the_net · · Score: 1

      Cross-platform? Lol... just when I think I've heard it all.
      I wonder what kind of idiotic apps manager would say - Hmmm we need an application that runs on Windows, Mac and Linux. What tools should we use? - I know - three development teams developing completely separate apps using completely separate languages and tool chains!!! Brilliant!

      You laugh, but there are people who claim this is actually the way to go, at least for the user interface. Their argument is that you can never really get the user interface to feel right for the platform, unless you use the tools for that platform.

      Since I don't do any GUI development other than in web pages, I don't know if they are right. I just wanted to point it out.

      --
      Please correct me if I got my facts wrong.
    13. Re:So what's better? by inglorion_on_the_net · · Score: 1

      Bottom line is I get paid to develop software for Windows, and I can do it quickly, easily, and have a lot of fun doing it, but if I had to use the OS X or Linux tools for developing software, I would probably shoot myself.

      Maybe it's just a matter of what you are used to, or personal preference. You claim the Microsoft tools are fantastic and clearly better than those for other platforms. I've heard this from other people, too.

      I've also heard people say that the development tools for the Mac are fantastic and the best they've ever used. From the cursory glance I took at Xcode back in the day, I was impressed, but I don't use or develop for Mac OS X, so it wasn't really an option for me.

      I've worked with Visual Studio a few times, and I'm always glad when it's over and I can go back to the tools I love (they change, but it's currently Emacs with a read-eval-print-loop for the language I'm developing in, and the Unix shell). I actually once quit from a company that developed using only Microsoft's latest and greatest software, because I couldn't stand it.

      Yet other people swear by Java and their favorite IDE (Eclipse/IntelliJ/NetBeans). Personally, I think Java is a huge waste of time. The IDEs are very impressive, and actually manage to make Java pretty usable. Still, I'm happy I don't have to do Java development anymore.

      One of my colleagues uses Delphi whenever he can. He has developed a lot of software in his career, and has used a lot of other tools before and after, but he says that, for him, Delphi still works best. He's currently looking at Lazarus, because the Delphi that he loves is no longer developed or maintained.

      So, strong opinions abound. Perhaps it's personal preference. Perhaps it's what you're used to. For some people, I strongly suspect that it's simply not knowing anything else. But the fact is: many people feel strongly about the technology they use to build software, and what one person prefers, another person abhors.

      --
      Please correct me if I got my facts wrong.
    14. Re:So what's better? by SplashMyBandit · · Score: 1

      Oh, so you're such an amateur that Java does not enter your consciousness. One technology for way more than three platforms. Incidentally, if is not product managers that demand cross-platform (again, novice thinking to think that shrink-wrapped software dominates; here's a clue, bespoke custom software dominates total number of development projects, and the public never sees it). It is the clients of that mass of bespoke software who work for big companies/government departments/defence who have all sorts of systems (a bit of everything). The number of desktops is huge, but they have a smaller pool of software than the fewer servers that each run a lot of customized stuff.

    15. Re:So what's better? by gbjbaanb · · Score: 1

      Why would I give up my managed environment and want to worry about de-constructors and managing resources

      spoken like a true .NET weener. You *still* have to worry about resource management, only now you have to slap Dispose() and using calls all over the place and basically manage them manually.

      Memory migth be cheap (but using all of it makes your app slow) but other resources are not, and those still have to be managed. GC doesn't do it for you. You should look into RAII and see what you're missing for "automatic" resource management.

    16. Re:So what's better? by terjeber · · Score: 1

      Here is why. If they had gone with a QT, GTK or wx solution, they would, with the current staff, have no solutions ready on any platform. With their current approach they have a rapidly evolving Windows version that probably covers 90-95% of their potential market. They make a token nod in the direction of Apple and Linux, but are not too worried that the teams are unable to deliver given that the increase in market would be insignificant.

      Being able to claim you are on all those platforms has a nice marketing value but no real tangible (bottom line) value.

      Such is the nature of developing niche products with small development teams. Windows is, by a pretty significant margin, above an beyond what exists on any other platform. If you care about delivering, you deliver for Windows.

      If you are Adobe and need to be present on OSX, then you hire a few hundred devs and let them take it up the out-door. On the other hand, if you are Adobe you are probably either on Win32 direct or MFC (Microsoft Frustration Classes) anyway, which means that all of your dev teams suffer equally. It seems people, even on /. are unable to understand that the typical enterprise dev team (one, two or a handful of devs) doing vertical niche apps have hugely different requirements than a mass-marked shop like Adobe. For the small dev teams, there is nothing that can touch Windows for development right now. Nothing in the same league. Nothing even in the same type of game. A good Ruby setup comes close, but even that is not quite there since it is mostly appropriate for html (javascript)-only apps, which is great until that is not enough. A lot of the vertical apps are simply not suited for pure html/js.

    17. Re:So what's better? by terjeber · · Score: 1

      Oh, so you're such an amateur that Java does not enter your consciousness

      Assuming here that he is talking about client-side apps, Java should stay out of his consciousness, far out. Should never enter it. Should not even be let close to the door of his consciousness.

      For client-side, you are probably better off doing client-specific development. A lot of the vertical stuff simply doesn't fit very well with the html/js way of doing things. You'd be a moron do go that route in many situations. That leaves you with either a cross-platform toolkit like Qt or doing each client in platform native tools. The latter would typically be preferable since it would leave you with a working Windows client rather quickly, an OSX client "coming soon" and a Linux client "in the works". Qt would leave you with three sub-optimal client applications "coming soon".

    18. Re:So what's better? by terjeber · · Score: 1

      I install VIM on every PC I run together with a whole host of other stuff from cygwin. I would never even dream of claiming VIM beats VS as a tool for software development though. Anyone who codes in VIM is a Luddite moron and I would have him fired from my team for being too religious and too dumb. Eclipse, sure, even Emacs is tolerable, but VIM is not a programmers editor. It is great for quick fixes to text files, and I used to use VIM for search-replace (but even there VS is better than VIM now).

      If all your "really productive" programmers use VIM they are in fact Luddite morons. At least they should use Emacs, or even better (probably) Eclipse.

      someObject.someProperty = otherObject.someRelevantProperty;

      In VIM that is 59 key presses or so. In VS2010 it would be 7-8 key presses. Not only that, after those 7-8 key presses I know that it will compile since it is once I hit the semicolon, a VIM user would not. Sure, there is insenvim, but I can't say it works too well. Hasn't for me anyway. This is an overly simplistic case. With templates and snippets I can have VS write significant amounts of my boiler-plate code, and that improves productivity.

      So, I'll repeat it. Anyone who thinks he is more productive in VIM than in a proper IDE like Eclipse or VS is a Luddite moron with such strong religious attitudes he isn't worth keeping on your team. Mostly because he's refusing, on religious grounds, to use tools that will significantly improve his productivity.

    19. Re:So what's better? by gr8_phk · · Score: 1

      You didn't support this statement (which I'm actually interested in, as I've never developed for a Mac)... you just said that .net isn't cross-platform so is worse than the cross-platform GUIs you mentioned.

      It is worse for *their* application. Because it is not cross platform they will need to maintain 2 large chunks of redundant code for the other platforms. I didn't mean to say .net is bad for windows, but it's bad for cross platform projects because it simply doesn't handle that for you, and using different GUI libraries within you product basically mean you reinvent wx in-house. And I'm only talking GUIs - they may have a bunch of .net code for other things that simply won't run on the others.

    20. Re:So what's better? by mswhippingboy · · Score: 1

      Methinks perhaps rereading my post might sharpen your comprehension skills.
      When I referred to "cross platform tools" I very much had Java in mind (I spend about 60% of my days developing enterprise java applications that run across Windows, Mac and Solaris platforms - the rest I spend doing Windows (.Net or MFC) and/or Android and iOS development), but it's not the only choice (e.g. C/C++, python, perl, etc., etc...).
      My point was that, unless the application is very small in scope it makes sense to develop one set of source code that is cross platform. If each platform implementation requires special functionality, then fine - develop that functionality as modules called by the mainline code, but keep as much code as possible platform independent.

      --
      Sometimes the light at the end of the tunnel is the headlight of an oncoming train.
    21. Re:So what's better? by mswhippingboy · · Score: 1

      Oh, so you're such an amateur that Java does not enter your consciousness

      Assuming here that he is talking about client-side apps, Java should stay out of his consciousness, far out. Should never enter it. Should not even be let close to the door of his consciousness.

      For client-side, you are probably better off doing client-specific development. A lot of the vertical stuff simply doesn't fit very well with the html/js way of doing things. You'd be a moron do go that route in many situations. That leaves you with either a cross-platform toolkit like Qt or doing each client in platform native tools. The latter would typically be preferable since it would leave you with a working Windows client rather quickly, an OSX client "coming soon" and a Linux client "in the works". Qt would leave you with three sub-optimal client applications "coming soon".

      In general, I agree with your comments, except that I think you are a little harsh (or unknowledgeable) on Java client side development. I've developed plenty of GUI client apps in Java that are every bit as performant as those developed in .Net, though you do have to know what you are doing (e.g. steer away from Swing and use SWT instead) and client side apps for Windows are certainly easier to develop in VS (or better yet - Powerbuilder), just as OSX apps are easier to develop in XCode. For the vast majority of enterprise applications (which is my space) though, the functionality provided with a cross platform tool like Qt is more than adequate.
      Unless you have a large budget and the inhouse skillset to support three development teams, developing completely separate applications is the last alternative I would choose. Again, I'm speaking from an enterprise development perspective. I would agree however for certain "vertical" applications that will be deployed to a wide number of users it may be worthwhile to develop completely different clients for each platform that create the best user experience on that platform, but I would certainly not label that as 'cross platform development'.

      --
      Sometimes the light at the end of the tunnel is the headlight of an oncoming train.
    22. Re:So what's better? by Anonymous Coward · · Score: 0

      Amen, brother.

      Although personally, I prefer Delphi and Delphi Prism to the MS tools. Slightly more productive for .NET, and much more productive for native/Win32. Looking forward to upcoming Delphi for Mac, when we'll likely ditch XCode.

    23. Re:So what's better? by SplashMyBandit · · Score: 1

      As long as you know what you are doing (which I'm sure you do) with regard to Swing's Event Dispatch Thread it is extremely performance ever since 1.6.0_u10 (when all of Java 2D became fully hardware shader accelerated). Plus, you don't have to deal with the macro-madness of Qt. Swing is a viable option, and if you know what you are doing (using profiler-guided optimisation) then enterprise customers don't even know the difference between that and something written in another toolkit.

    24. Re:So what's better? by SplashMyBandit · · Score: 1

      Done any Swing development since Java 1.6.0_u10 came out, or are you basing your comments on half-decade old experience (which is the Stone Age in IT, yeah)? Turns out that Java2D (which Swing uses) is *fully* hardware shader accelerated since that JDK release - that is, used DirextX or OpenGL to draw (depending on platform). You can't make Swing slow unless you block the Event Dispatch Thread (EDT) - which unfortunately many inexperienced people do (which is definitely one negative for Swing). We make and sell apps on GWT and Swing and no-one knows the difference (in fact, most people comment on how the 'Nimbus' Look & Feel is so much nicer than most of the (native Windows) apps they have - which I was surprised by).

    25. Re:So what's better? by SplashMyBandit · · Score: 1

      Good one, blame the reader for their comprehension skills, when perhaps the writing had better clarity and was more direct then misunderstandings would not arise. Thanks for clarifying though, I agree with you analysis (now that it has been clarified).

    26. Re:So what's better? by mswhippingboy · · Score: 1

      Thanks for that.

      I may take another look at Swing since I haven't used it much since I picked up SWT. I did prefer the programming model of Swing over SWT, but I felt the resulting GUIs were too sluggish and were giving Java in general a bad reputation for client side apps. As a side bar though, it's beginning to sound like JavaFX 2.0 with it's scene graph architecture is pretty promising and might well turn out be to better alternative to either SWT or Swing.

      --
      Sometimes the light at the end of the tunnel is the headlight of an oncoming train.
    27. Re:So what's better? by terjeber · · Score: 1

      SWT is a good thing, and Eclipse as a platform is a Very Interesting thing. Sadly it hasn't taken off though, and that is partly because of the bad rep Java as a client framework got from AWT and Swing, both, in different ways, abominations onto anything holy.

    28. Re:So what's better? by terjeber · · Score: 1

      No, I have not done Swing since 1.5, but I have heard positive things about it. Will look into it this summer. If it is good enough I'll drop client-specific of course, I much prefer cross-platform. Now, performance was never my primary beef with swing though, looks was.Nimbus looks great. Next time I do a desktop app, Nimbus will be at the top of my list. Currently only doing HTML stuff using .NET MVC and Play! on GAE.

      Curious - is Swing also accelerated as a browser plug-in (applet)? If it is, awsomeness might still happen to Java client stuff. Now, if I can only get my employer to understand how much nicer both Play! and Spring is than that JBoss monstrosity, life would be perfect. Next -> Oracle Fusion!

    29. Re:So what's better? by bongey · · Score: 0

      ctags,cscope + super tab above command done in 7-8 keystrokes , including the tab. You haven't use vim that much so don't act like you have.
      Finally I used VS for 8 years, use to be my favorite, along with being a windows fan. Sorry but I grew out of it and it got in the way more than helped.
      VS is really designed to dumb down programming well for stupid programmers, bad thing is they make bad programs that just don't work or fucking stupid.
      GUI everywhere when there shouldn't be, incredibly slow.
      Oh yeah I might have eclipse, intellij , vim , slickedit open at the same time for the same code base depending on what I am doing.
      The only thing that is really nice in VS is the C++ debugger , and C++ intellisense (sometimes).
      You install cygwin just for vim? http://www.vim.org/download.php#pc there is a windows edition.

    30. Re:So what's better? by SplashMyBandit · · Score: 1

      Swing lets you do desktop, applet, and 'Webstart', which is kinda mixture of the two (Webstart applets start 5x faster than traditional applets if you've copied the Webstart applet to the desktop, but you still get the benefit that the applet checks for and applies any updates from the server).

      Also, don't forget to check out Google Web Toolkit (GWT) for web development. It is a fantastic way to do AJAX webapps without too much worry about browser-specific (unlike 'raw' Javascript development).

    31. Re:So what's better? by terjeber · · Score: 1

      I've done a bit of GWT, and so far it hasn't really been working out. Still too many issues where there is marginally different behavior on different browsers.

    32. Re:So what's better? by jon3k · · Score: 1

      Let me guess, you've never developed software on any platform besides Windows.

  24. Re:So then, by erroneus · · Score: 0

    I'm kinda glad to see .NET go. It was a nice idea but like so many things Microsoft tries to invent, they just don't seem to carry on the way they imagine. Sure some things stick but those are usually the things they force on users, businesses and governments everywhere. But you know, I like my xboxes...

  25. Re:Not quite... by the+linux+geek · · Score: 1

    You know Java isn't related Javascript, right?

  26. Re:Not quite... by icebraining · · Score: 1

    HTML5 plus JS can be a nice option for small stuff - gadgets, simple apps, etc. Lack of threading isn't very important - you can use asynchronous tasks, Ã la Web Workers. Sure it's less powerful, but more than enough for many tasks (and probably preferable if you don't really need threads).

    The main concern is Trident's performance compared to V8 or TraceMonkey.

  27. Microsoft fanfiction. by Alex+Belits · · Score: 2, Funny

    The article is something that I have never seen before -- Microsoft fanfiction.

    What creates an interesting problem -- since Microsoft fanfiction exists, according to the rule 34 there must be Microsoft slash fanfiction. But since there is only one instance of Microsoft fanfiction and it is not slash, someone on the Internet must write Microsoft slash fanfiction.

    Go, Internet, go!

    --
    Contrary to the popular belief, there indeed is no God.
    1. Re:Microsoft fanfiction. by Anonymous Coward · · Score: 1

      I call "Blue Sex of Death"!

    2. Re:Microsoft fanfiction. by Anonymous Coward · · Score: 0

      Wouldn't it have to be Microsoft backslash fanfiction?

    3. Re:Microsoft fanfiction. by Alex+Belits · · Score: 1

      Wouldn't it have to be Microsoft backslash fanfiction?

      Steve Ballmer \ Rick Belluzzo?

      (can't unthink...)

      --
      Contrary to the popular belief, there indeed is no God.
    4. Re:Microsoft fanfiction. by VortexCortex · · Score: 3, Informative

      There are official MS OS Anime personifications, and there have been for quite some time.

      I see that although you are not new to the net, you are new to this topic, so I'll link you to one list of the OS-tans. I'm sure you'll have no problem finding the other less NSFW places yourself to see more and better quality pics/fics, if you are so inclined...

      There is indeed slash fiction. I read one not too long ago about XP-tan having an affair with Windows7-tan, Vista-tan was quite upset (her abandonment issues surfacing yet again); The always compassionate Linux-tan tried to console her, but it made the needy OSX Leopard-tan very jealous (apparently consoling a rival is a grave transgression on her home planet).

      There are OS-kuns (males) as well... My girlfriend told me of the new yaoi slash she was reading where OSX-Kun fell in love with the heroic and savage XP-kun who had rescued him from the lair of the evil scientist Dr. Mac-Defender. In the heat of their passion OSX-kun had unknowingly infected XP-kun with a virus; Thus, both OS-kuns were soon on their way to see the comically bungling Dr. Norton-kun.

      Fear not my friends, Rule 34 can not be denied.

    5. Re:Microsoft fanfiction. by Alex+Belits · · Score: 1

      But that's not Microsoft fanfiction, it does not describe fictional events happening with real (a real-life equivalent of "canon" Microsoft), written by fans if Microsoft. OS-tans are original fiction, that refers to real-life things through allegory. A story about Steve Ballmer and Rick Belluzzo having sex (that I have mentioned before), would be slash fanfiction if written by someone who likes Microsoft.

      --
      Contrary to the popular belief, there indeed is no God.
    6. Re:Microsoft fanfiction. by VortexCortex · · Score: 1

      Hair splitting seems to be your specialty... It's called Potter slash when Ron and Harry play with eachother's "wands". By your definition the slash would have had to involve Pratchett humping a book. MS makes OSs, and fictional representations of them as well (much like the fictional characters in the Harry Potter series), thus slash involving said characters is indeed MS slash fiction. Perhaps a more accurate "slash" fiction (by your standards) would involve AI evolving from actual MS OSes, and their holographic representations having intercourse? (How is this much different from the above cited slash?)

      This is the Internet, it would not surprise me that some would like to see the sexual acts described in your post -- if fact, I have stumbled upon Ballmer's Gates' heads transposed onto gay porn images. Would that meet your criteria, given that it was accompanied by some rather raunchy textual descriptions of their lovemaking? If so, you may sate your twisted desire for such things at 4chan.org.

      I'm sure if you simply apply your searching skills and know of the proper key words you'll find the specific gay porn fiction of which you speak. You'll also find "erotic" pictures of people having sex with real OS install disks. If you look hard enough, and are of twisted enough mind you may even stumble upon the "money-shots" involving real men and their beloved Sandy-Bridge chips (as I have -- anonymous image-boards are not a place for the feint of heart).

    7. Re:Microsoft fanfiction. by Anonymous Coward · · Score: 0

      The article is something that I have never seen before -- Microsoft fanfiction.

      What creates an interesting problem -- since Microsoft fanfiction exists, according to the rule 34 there must be Microsoft slash fanfiction. But since there is only one instance of Microsoft fanfiction and it is not slash, someone on the Internet must write Microsoft slash fanfiction.

      Go, Internet, go!

      Never seen that picture of Bill Gates with Oprah? You are at least 10 years too late.

    8. Re:Microsoft fanfiction. by Anonymous Coward · · Score: 0

      As Bill lay in bed gently caressing the MacBook's hard aluminum case he knew what he was doing was wrong but he couldn't help himself. It felt so good.

    9. Re:Microsoft fanfiction. by Anonymous Coward · · Score: 0

      Rule 34 is that is it exists, there must be porn of it. Where did you get 'slash fanfiction' from?

    10. Re:Microsoft fanfiction. by Alex+Belits · · Score: 1

      "It" being Microsoft fanfiction, therefore porn of it would be Microsoft slash fanfiction.

      --
      Contrary to the popular belief, there indeed is no God.
  28. Re:Not quite... by postbigbang · · Score: 1

    Yeah.

    --
    ---- Teach Peace. It's Cheaper Than War.
  29. Oh THAT Longhorn... by Alimony+Pakhdan · · Score: 1

    Came here hoping for something about Texas, left disappointed.

  30. Re:Not quite... by Xtravar · · Score: 1

    Enterprise, yes. Personal, maybe/probably not. Lemme answer for him since I work on "enterprise" applications.

    In the enterprise, you have two options for deploying to hundreds of users: installing local apps on every workstation, or using Citrix (which is nice, but pretty flakey sometimes). Citrix is basically Windows Remote Desktop, but more tuned to the task. In fact, MS licensed the technology from them.

    Anyhow, when you need to perform maintenance or upgrades, you have to touch hundreds of workstations. Yes, there are ways to do this more easily, but it's easier with Citrix. And it's most easy if you just have web server software to upgrade.

    Now, none of this actually relates to Microsoft per se, but this is how large ISV enterprise-oriented companies are moving. Hope that helps!

    --
    Buckle your ROFL belt, we're in for some LOLs.
  31. Re:Not quite... by jmorris42 · · Score: 2

    > No, because they looked at Windows 8.

    Except that they didn't. They looked at a random build. Remember that Sagans of KLoCs were written for Longhorn and then abandoned. That wasn't the first time and it won't be the last. People wrote articles based on those leaked copies too, because they were intentionally leaked for just that purpose. It has always been thus, everyone else's shipping products are compared to what Microsoft says it will ship 'RSN.' Then it eventually ships and isn't anything like what was promised. Rinse and repeat every couple of years.

    About all that can be stated with any certainty is that Windows 8 will probably ship sometime between 12 and 24 months from now and will add support for ARM and a tabletish touch interface. The tablets are a done deal because they would totally piss off OEMs who are already putting product into the pipeline that they would ship Android or Meego if Microsoft changed course on em.

    Windows 7 is the only product that resembled the prerelease hype and that was because the goals were so minimal, Make a Windows Vista that doesn't suck donkey balls. Since they had eliminated most of the worst suckage by Vista SP1 (and people generally were buying it on new hardware instead of upgrading by then) about all that was left was to reskin it so people who had heard that "Vista Sucks" wouldn't look at 7 and instantly associate it with Vista.

    --
    Democrat delenda est
  32. MSDN Licenses by nzNick · · Score: 2

    Keep in mind, MSDN licenses are annual subscriptions - so MS developers pay for the dev tools EVERY YEAR, and they keep on paying .......

    1. Re:MSDN Licenses by godefroi · · Score: 1

      Purchasing an MSDN subscription is not the only way to acquire a license to the development tools. You can straight-up purchase Visual Studio in any one of several editions.

      Getting it with the subscription, however, guarantees you access to EVERYTHING ELSE Microsoft produces, in perpetuity (meaning, you can still use your copies of Windows, Visual Studio, and MS SQL Server for development/test/demonstration purposes after your subscription expires). If you go for the "ultimate" or "premium" subscription, you additionally get to use Office, Project, and Visio for "production" (real-world use, not just development) purposes.

      --
      Karma: Poor (Mostly affected by lame karma-joke sigs)
    2. Re:MSDN Licenses by Richard_at_work · · Score: 1

      Wrong - MSDN licenses are subscription based for continuous updates, but contain perpetual licenses for all software (production use for some, like the dev tools, and other software such as Office, Project, Windows 7 depending on the MSDN subscription level you went with, and development or testing only for the rest of the software base such as Windows Server, SQL Server, SharePoint etc etc), which means that when your 1 year or 3 year subscription expires, your copy of VS2010 is still validly licensed.

      If the next version of Visual Studio is released during your subscription, you gain that license as well.

      Try actually reading the licenses some time, rather than going with the FUD.

  33. Re:Not quite... by gr8_phk · · Score: 1

    The way I see it is that MS is trying to push toward an easy interface for creating apps

    So they're switching to Qt or GTK? Probably Qt but it doesn't really matter because they'll also provide wx so you can use the language of your choice and the UI details will be transparent. So what that means is dumping a bunch of legacy code and providing wx.net. Sounds good to me, I won't have to change a thing to remain cross-platform.

  34. Re:Not quite... by cob666 · · Score: 1

    I work at a pretty large multi national manufacturing company that is primarily a windows shop but also has a pretty large Citrix user base. Citrix is primarily used by users on the shop floor that require basic functionality (although we have several custom applications that are run under Citrix). While I agree with you that maintenance can be very easy in a Citrix environment, the company I work at has a pretty good handle on how to leverage AD, GPO and Windows Update Server to ensure that all machines connected to the network are updated properly and are always configured properly. I don't work in the networking group but I think it's pretty impressive how simple it is to manage such a large number of Windows workstations pretty much 'hands off' if the domain servers (login scripts and GPO rules) are configured properly.

    I'm looking forward to seeing how Microsoft is going to implement a new core set of APIs without shitting on the current developer base.

    --
    Do what thou wilt shall be the whole of the Law - Aleister Crowley
  35. Fire and Motion by gr8_phk · · Score: 1

    This is all what Joel said in his blog about Fire and Motion. Every second you have to think about platform changes, you're wasting time that would be better spent building your product or even making it platform independent or even competing with MS - hey, you're both writing software. Windows developers are on a treadmill and think that's a normal condition. There are mature ways to write mostly platform independent code these days. This entire discussion is for people who are not using them - the rest honestly don't care and will not be wasting time thinking about it.

    1. Re:Fire and Motion by weicco · · Score: 1

      I don't get it. Why should I write platform independent software? If I'm writing stuff at home I write it for myself. I have only Windows boxes at home so why should I bother making software portable? And when I'm writing stuff at work it's the customer that defines the requirements. In my 10+ year career I've never seen a requirement that the software must be (easily) portable to another platform. So why should I bother when customer doesn't pay for portability?

      --
      You don't know what you don't know.
  36. Re:Not quite... by c0lo · · Score: 1

    Anyhow, when you need to perform maintenance or upgrades, you have to touch hundreds of workstations. Yes, there are ways to do this more easily, but it's easier with Citrix. And it's most easy if you just have web server software to upgrade.

    You can have both of the world with REST (no session logic on the server) and a framework that accepts plugin-updates (e.g. Eclipse framework).
    I heard cases in which stock trading apps were crafted this way - can't respond fast enough in a simple page in browser (mainly because of the server overload), can't afford not to update them, can't imagine a way in which the deployment a new version can be achieved by "download the installer and run it" means.

    --
    Questions raise, answers kill. Raise questions to stay alive.
  37. Re:So then, by Anonymous Coward · · Score: 1

    They are NOT dropping .Net ... Do you seriously think that MS is going to make people write enterprise applications and server processes in HTML and Javascript??? Why are so many people incapable of applying a little critical thinking after reading/hearing something? Here's a test: go try writing a service in html & javascript. Do it. Go now, I'll wait. K, how well did that work out? Still think they're dropping .Net?

    The GUI will be based in html & Javascript ... which potentially means an end to winforms & WPF. POTENTIALLY. There's a lot more to .Net than GUIs.

    On a side note, the sky is falling, and oh, WOLF!

  38. Re:Not quite... by CapOblivious2010 · · Score: 1

    ...can't imagine a way in which the deployment a new version can be achieved by "download the installer and run it" means.

    These people have a serious lack of imagination. You install the app once, via whatever mechanism you choose, then it "self-heals" by downloading updates and replacing itself on disk. It's not that hard, and (assuming you never screw up the upgrade process ;-) it works great.

  39. Re:So then, by WNight · · Score: 1

    They're always looking for new ones who don't know how the last ones got screwed.

  40. Re:So then, by c0lo · · Score: 3, Funny

    what happened to "developers developers developers" ?

    They moved into the "O-cloud-O cloud-O cloud"

    --
    Questions raise, answers kill. Raise questions to stay alive.
  41. There is a brilliance here... by trippyd · · Score: 2

    Maybe the response from .net developers is more rooted in the fact that a JS/HTML5 based application development language brings a whole lot more developers to the party with less of a learning curve.

    1. Re:There is a brilliance here... by FrootLoops · · Score: 1

      No, I'm pretty sure the (erroneous) reaction is just "I'm getting paid because .NET development works on Windows, and you're dropping support?!!!!". It's unclear how much web developer experience with JS/HTML5 will translate to whatever desktop app system Microsoft cooks up. You bring up a good point, but I doubt it's the root of any reaction.

  42. Re:So then, by Anonymous Coward · · Score: 1

    You mean that rumor I heard about Steve Ballmer turning tricks in Bellingham are false?

    Having visited Bellingham, all I can say is he'd fit right in

  43. Re:So then, by Anonymous Coward · · Score: 1

    Wow, APK? You actually follow this guy around? You have *serious* mental health issues, mate and I say that with all sincerity. You have spent a good 10 years carrying on in the same way - abusing everyone online, shouting about your l33tness and generally just coming across like a tool. Have you truly never wondered why every single person you speak to online thinks you're an idiot? Is every single person on the planet wrong, except you?

  44. Re:Not quite... by Anonymous Coward · · Score: 0

    Yeah.

    i don't think you do.

  45. Re:So then, by DarkOx · · Score: 1

    You missed out on hta applications then... Ok Microsoft absolutely has tried to get people to develop application in HTML/vbscript/javascipt in the past/

    --
    Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
  46. yeaaa by unity100 · · Score: 1

    they do. good luck finding such streams in the world of dynamic range boosted audio recordings.

    there is no crystalizer support for x fi under linux, but audacious media player does that perfectly well (even better) with its crystalizer plugin.

    1. Re:yeaaa by Anonymous Coward · · Score: 0

      dynamic range boosted audio recordings

      off topic, but it's "dynamic range compressed"

  47. Re:Not quite... by Gadget_Guy · · Score: 1

    The difference is that Longhorn's projected API's were advanced API's built on existing languages, tools, and frameworks, whereas the JavaScript switch is an attempt to move developers to a totally different (and arguably inferior) system.

    But this is not a radical switch to Javascript designed to eliminate all other development systems any more than when Microsoft used HTML and Javascript to implement the Windows Sidebar, or when they used HTML and Javascript to implement HTML Applications (HTAs), or when they used HTML and Javascript to implement Active Desktop gadgets.

    This is just a continuation of their development strategy that dates back to 1997. The controversy surrounding the use of HTML5 for the interface is just stupid and unjustified angst that ignores nearly 15 years of API precedent.

  48. Unix or Linux is no different by caseih · · Score: 1

    Comparing posix read() and write() to the shifting sands of MS APIs is pretty silly. If you're going to make a comparison to Unix, at least compare apples to apples. So once upon a time I wrote code in C++ with Qt 1.0. Then Qt 2.0 came along, which was mostly compatible, but introduced new features. Then Qt 3, then Qt 4. Some things were deprecated, some things added. Developers had to adapt. Same with Gtk+ 1 to Gtk+ 2. That was a pretty painful leap for developers with several important (but understandably obsolete) widgets were deprecated. A few vertical apps out there probably never have moved from Gtk+ 1.

    Anyway the point is things on Unix, as nice as they are, are not static, or even stable. The real world APIs that are necessary for developing real applications are in constant flux, and many fade away (like Motif). New languages come along that get popular for a time, like Python. Will we be using python in 10 years? hopefully. But maybe something else will come along.

    So is learning python and it's current standard library of APIs, and the various current GUI apis a waste of time? I mean if the Gtk+ developers are going to pull the rug out from under me every couple of years, what's the point, right?

  49. Re:So then, by Anonymous Coward · · Score: 0

    Can you show us any work you've done in .NET? Somehow I don't think you can. That'd make you a bullshitter.

  50. Seems erroneus likes making threats on slashdot by Anonymous Coward · · Score: 0

    http://slashdot.org/comments.pl?sid=2261720&cid=36545928 Did something you did (like run after having your behind handed to you 10 times in a row, lol, upset you? You did that to yourself).

  51. Re:Not quite... by RightSaidFred99 · · Score: 1

    Hundreds of users? Lol. No, I'm talking thousands. You develop web apps. You use a Java or .NET backend, and something like JSF, ASP.NET, MVC, or Silverlight for the front-end. Unless you're a glutton for punishment you don't write a lot of raw HTML/Javascript, though Jquery seems to have its place.

  52. You defeated your own argument by gottabeme · · Score: 1

    So your argument is that Microsoft intentionally periodically obsoletes languages in order to make money? Am I reading this correctly?

    You do understand that:

            Pretty much every commercial MS developer already has an MSDN license, which (minimally) gives them access to the latest development languages, SDKs, and tools.

    You do understand that:

    MSDN licenses cost a lot of money. Were it not for the constant churn, developers wouldn't need MSDN subscriptions, and could save a a lot of money.

    --
    "Those who consume the bulk of goods are those who make them. We must never forget this secret of our prosperity."
    1. Re:You defeated your own argument by Jahava · · Score: 1

      So your argument is that Microsoft intentionally periodically obsoletes languages in order to make money? Am I reading this correctly?

      You do understand that:

      Pretty much every commercial MS developer already has an MSDN license, which (minimally) gives them access to the latest development languages, SDKs, and tools.

      You do understand that:

      MSDN licenses cost a lot of money. Were it not for the constant churn, developers wouldn't need MSDN subscriptions, and could save a a lot of money.

      Companies pay for MSDN licenses for a lot more than the latest language. They provide the latest SDKs, documentation, tons of tools, exemplar operating systems, future betas and product (to test and build against), and, of course, a gigantic repository of forum knowledge and a means of engaging Microsoft. Obviously the MSDN / developer model that Microsoft has established is for profit and cash. No shit.

      The point I was making is that they don't have to phase out .NET to keep that stream going. Sure, you may have the latest Visual Studio, but without the rest you're still a second-rate developer with poor access to resources. Almost every single Microsoft development company maintains some form of MSDN subscription; Microsoft choosing one language or another will not affect that. The OP alleged that they will abandon .NET solely to make money off licenses, while I believe the current ecosystem quite thoroughly abolishes that idea.

    2. Re:You defeated your own argument by gottabeme · · Score: 1

      Hm. Well, .NET isn't a language, of course.

      I think the basic point is that Microsoft is constantly obsoleting development tools, requiring upgrades to remain relevant, just like they obsolete software like Office and Windows itself, requiring upgrades, all of which forces the purchasing of new licenses for minor upgrades and changes--some of which aren't even improvements.

      Compared to FOSS, which, by and large, doesn't force costly upgrades to remain useful and relevant and secure, and is much more self-sustainable, Microsoft software and tools are a treadmill leading to a giant money pit. What's so sad is how many developers and businesses hop on the treadmill and jump in willingly, like mindless Lemmings who can only comprehend the status quo--or are bribed into keeping it.

      --
      "Those who consume the bulk of goods are those who make them. We must never forget this secret of our prosperity."
    3. Re:You defeated your own argument by Anonymous Coward · · Score: 0

      You can use all the core features of Visual Studio and .NET for free using Visual Studio Express and it's related software. IME you only need MSDN if you are developing for Microsoft applications (like Exchange or Dynamics CRM or something similar). There are also a few free or low-cost packages that give you access to a ton of Microsoft software to develop your heart out.

    4. Re:You defeated your own argument by godefroi · · Score: 1

      Compared to FOSS, which, by and large, doesn't force costly upgrades to remain useful and relevant and secure, and is much more self-sustainable, Microsoft software and tools are a treadmill leading to a giant money pit.

      ... but .NET is free?

      --
      Karma: Poor (Mostly affected by lame karma-joke sigs)
  53. Re:Not quite... by Xtravar · · Score: 1

    OP made it sound like you doubt the transition to web apps. Apparently I'm arguing for nothing. Good night!

    --
    Buckle your ROFL belt, we're in for some LOLs.
  54. Re:erroneus makes blackmail threat on slashdot? by Anonymous Coward · · Score: 1

    No, seriously. You've been making comments like this for at least 10 years. Dodging the issue and just plain being a nutcase. No one is talking about whether or not you "won" some round. You've never whipped anyone like a dog. for TEN YEARS every single forum you show up on has people saying "go away, you're an idiot" and you STILL maintain you're some sort of God.

    Time to grow up. No one likes you. Stop acting like a tool and start actually reading the feedback you get EVERYWHERE and you might have a hope of understanding what you've become.

    And no, I am not Erroneus.

  55. Erroneus makes blackmail threat on slashdot? by Anonymous Coward · · Score: 0

    http://slashdot.org/comments.pl?sid=2261720&cid=36545928 Is it because you trolled someone http://slashdot.org/comments.pl?sid=2253808&threshold=-1&commentsort=0&mode=thread&pid=36521452 and they shot you down on every so called point you tried to make and they did it with documented facts anyone could see? I saw you run like a whipped dog 10 times there in fact, and for your starting trouble with others you threaten to blackmail? Very intelligent (not).

  56. Arm support by Wattos · · Score: 1

    The reason to move to a js based system should be quite obvious. The only reason winodws is still the most used Desktop Os is because of the ton of applications which were developed over time. If all of these worked on linux, who knows if windows would be that widespread as it is now. Anyway, the reason i can imagine ms pushes a js system is to ensure crossplatformness in their apps. Windows 8 will be the first time they will support a different architecture on windows (arm). It will be easier to ensure a unified look and feel (as well as compatibility) if the thing is written in js. Suffice to say, you would have to be mad to develop anything big with js as your main language.

  57. erroneus makes blackmail threat on slashdot? by Anonymous Coward · · Score: 0

    http://slashdot.org/comments.pl?sid=2261720&cid=36545928 Is it because you trolled someone http://slashdot.org/comments.pl?sid=2253808&threshold=-1&commentsort=0&mode=thread&pid=36521452 and they shot you down on every so called point you tried to make and they did it with documented facts anyone could see? I saw you run like a whipped dog 10 times there in fact, and for your starting trouble with others you threaten to blackmail? Very intelligent (not).

  58. Re:erroneus makes blackmail threat on slashdot? by Anonymous Coward · · Score: 0

    ROTFLMAO - sure you're not erroneus

    And no, I am not Erroneus.by Anonymous Coward on Thursday June 23, @11:56PM (#36551186)

    Are you going to blackmail me too?

  59. Re:So then, by Anonymous Coward · · Score: 0

    It's the blackmailer erroneus posting as ac now. How clever!

  60. erroneus did try you blackmail someone here? by Anonymous Coward · · Score: 0
  61. Re:So then, by Anonymous Coward · · Score: 0

    Erroneus you blackmail & others have mental issues?

  62. Re:Not quite... by man_of_mr_e · · Score: 1

    This is basically the problem the One-Click is designed to solve. It deploys apps by web and is very easy to use.

  63. Yeah right. by Arancaytar · · Score: 1

    The last time they promised that, Vista.

  64. Re:Not quite... by mwvdlee · · Score: 1

    I have a little difficulty believing that Microsoft, a company that has - since the inception of Windows - sacrificed functionality, security and stability for the sake of backwards compatibility is now all of a sudden forcing developers to switch to an entirely new language and development model.

    --
    Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
  65. Re:So then, by Anonymous Coward · · Score: 0

    Nobody sane wants to develop large applications in fucking native JS and HTML5, and Microsoft knows that.

    If they can make them fast enough and add a layer of XUL like markup, I don't see any problems ...

  66. Re:Not quite... by DrXym · · Score: 1
    Assuming there were a HTML5 + Javascript option, it would be more akin to programming XUL on Firefox than it would be a website. It would have to provide access to a wider range of APIs than a browser provides to a website, the security model would be different and it's likely there would be extra markup for Windows elements like common controls, media players etc. If MS were really super clever they'd even let people code away in Silverlight or .NET and then run the app through something analogous to GWT where the code is compiled into the equivalent JS & HTML.

    I really don't see what the fuss is about. Microsoft aren't going to shitcan .NET or COM any time soon unless they want to break every app in existence. However their imperative is probably to give tablet based devices, especially those running ARM the best chance possible and that means facilitating development which is not tied to the old Win32 API or native instructions. And that means providing an API for developers to use to do it. It would be nice to know how they expect native C++ apps to migrate though - seems like Windows 8 would be screaming for a LLVM like solution where a single binary could target multiple architectures without especially caring what architecture it was running on for the most part.

  67. Re:Not quite... by hairyfeet · · Score: 1

    Yep it seems like yet again MSFT is ripping off Apple, even the bad parts. I don't know which is worse, MSFT screwing their developers with "me too! Web 3.0 bling bling yee haw" bullshit, or Apple boning the creative industry by putting out an upgraded iMovie and calling it Final Cut Pro while yanking the rug out by refusing to sell new licenses to the previous version.

    And just to show some love and keep them from feeling left out this would be a GREAT time for Linux to offer people a "third way" since both Apple and MSFT are burning their hardcore markets to chase the retarded consumer market, but sadly they won't pull their heads out of their collective asses, send Torvalds off on an ice flow or whatever it is you do with a Finn that is past his prime, and finally join the rest of the planet in the 21st century by having a stable ABI like EVERYONE else (Solaris, BSD, OSX, Windows, OS/2) has had for fricking ages so that "update foo broke my driver" could finally be laid to rest and updating wouldn't be a "break Linux NOW" button.

    Sometimes I swear it is like the whole world just decides to become ca ca flinging monkeys every so often, just for shits and giggles. How two of the biggest companies could be so fricking stupid and burn so many of the ones that make them money is beyond me, nor can I understand why everyone thinks having drivers shit themselves and die when you update the thing is a good idea in Linux. It is like when Alice says in Wonderland "But I don't want to go around any mad people!" and the cat says "Sorry but we're all mad here dear" as it seems like the whole tech world is off its nut ATM.

    The only saving grace for us Windows users is that Windows 7 is supported until 2020, which hopefully by that time Ballmer will be given a mock turtleneck and a pink slip and we can get the office guys to make Windows 9 a decent OS. Of course by then maybe Torvalds will retire and with him his religious hatred of having an ABI, that or Google will just fork the thing away from him and we'll all be using Android/Chrome/whatever they call it this week on everything mobile so it won't matter anyway.

    Oh one last thing, don't bother posting that link to the one kernel dev that rails against ABIs as I don't listen to religious nutjobs, and that is EXACTLY what he is. If you bother to read that post he goes so far as to call all like Nvidia who don't hand every scrap of driver code to the devs so that may bless it with their divine hand "leeches" and hopes that Torvalds trashes their driver the next time he goes Goatse on the kernel. Say what you want about MSFT, but my Win2K drivers work in XP SP3, that is 14 YEARS of driver support, and I have no doubt I'll see the same with Vista/7 drivers. In fact I'm using 5 year old Vista cap card drivers in Win 7 SP1, that is 5 years of support. Man if I could get that many years of driver support in Linux my shelves would be full of Linux machines right now.

    --
    ACs don't waste your time replying, your posts are never seen by me.
  68. Re:erroneus makes blackmail threat on slashdot? by erroneus · · Score: 1

    I don't post anonymous coward. And it is not blackmail. It's a simple fact. If you don't think that human resources and other decision makers don't google your name before deciding to give you money for your work, you must have missed quite a few stories on the subject of this thing call "the internet" and the things like "social networks." And when you google yourself, you get a lot of things about APK and Alexander Peter Kowalski.

    Slashdot and other forums are public and indexed extensively. With every single additional taunt, assault and claim of triumph you make, you are adding to the pile of crap for anyone to find. It was a single search on google which caught me up on your long history of this impressive behavior.

    I don't expect you to read this and suddenly realize what you have done to yourself. You have demonstrated the inability to see anything resembling reality for a very long time. But I am always open to surprises. So if you decide to suddenly get sane, I'll be very surprised.

  69. Re:Not quite... by arose · · Score: 1

    The main concern is Trident's performance compared to V8 or TraceMonkey.

    I can't help thinking that sponsoring a node.js port to Windows is part of the solution. It's V8 and has threading, if they can hook it into IE for the rendering it might make for a decent platform.

    --
    Analogies don't equal equalities, they are merely somewhat analogous.
  70. Re:So then, by erroneus · · Score: 1

    Microsoft has an established history of pushing things like this and then dropping them after creating a new bandwagon for everyone to jump on. If they let their stuff go stale, the competition will pass them by and push them from their own playground. And so what do they do? They create new product cycles just like hundreds of other businesses out there do. And it's not just developer tools, it's Windows and their Office suites too. They do everything they can to create new sales. Back in 2007, Microsoft realized they could double their sales for licensing Windows by making their volume license agreements "upgrade only" meaning before you can use it, you had to have a qualifying product which would be either OEM or retail Windows. (Ok, Mac OS is also a qualifying product I hear...) So practically speaking, you now have to buy Windows twice if you wish to use it in an enterprise setting. And in 2007, they saw a spike in sales... go figure!

    So when you apply critical thinking as well as Microsoft's history, you will see how it works quite clearly. So even if they aren't dropping it immediately, it will definitely go away in favor of something else. And at the moment, this push for HTML5 and related things has Microsoft pretty busily working in that direction.

  71. Re:So then, by Anonymous Coward · · Score: 0

    I guess like monitor tosser Steve they do notlike developers as well.

  72. Re:Not quite... by Anonymous Coward · · Score: 0

    Well ain't that cute...

    I don't listen to religious nutjobs

    That's ok, no one listens to you either.

    Say what you want about MSFT, but my Win2K drivers work in XP SP3, that is 14 YEARS of driver support

    ... huh? XP and 2k were released a little more than 14 months from each other. I still have a working HP Vectra N2, does that count as 22 years of Linux driver support?

  73. Blackmail's against the law erroneus by Anonymous Coward · · Score: 0

    No employer's going to hire you for blackmailing people on forums with threats like this http://slashdot.org/comments.pl?sid=2261720&cid=36545928

    1. Re:Blackmail's against the law erroneus by Anonymous Coward · · Score: 0

      I don't see a threat there. I see an indication that this forum is available to public scrutiny. I don't see "I'm going to contact all of your employers and tell them what you are doing" and frankly, I don't see how that is even remotely possible to do without knowing precisely who you are, where you live, and where you work. None of that information seems to be available so it seem unreasonable that the statement could be considered a threat of blackmail or of any kind.

  74. Re:Not quite... by gbjbaanb · · Score: 1

    yeah, but C# is. I guess that 'promise not to fork it'' line already got broken :)

  75. Re:So then, by gbjbaanb · · Score: 1

    Nobody sane wants to develop large applications in fucking native JS and HTML5

    this is the bit I don't get. Nobody woudl write any system in HTML5+js. It would be the presentation layer only, and be accessed via nice, easy-to-use APIs that bring the barrier of GUI development down. The meat of the app would be written in C++ or C#.

    The only reason I can think of that people think that HTML+js is the language to use for the entire system is because that's the way they code everything else - traditional Windows developers in other words, who create huge, bloated, monolithic desktop apps. the kind of guys who'd write everything in VB rather than write the GUI in one system and the rest of the business-layer code in another, more suitable one.

    Microsoft knows people want much easier GUI development systems, that non-developers can write. So far that's HTML5+js, and perhaps that's what's scaring the .NET devs - they see their 'tech expert' position being undermined as it is opened up and made easier.

  76. Re:So then, by ultranova · · Score: 1

    Nobody sane wants to develop large applications in fucking native JS and HTML5, and Microsoft knows that.

    Why not? Most "large applications" simply have lots and lots and lots of features. They are not processor-intensive; the code paths aren't long, but there are a lot of them. You'd think that a high-level managed language coupled with a layout engine would be exactly the right tool for writing them.

    --

    Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

  77. Re:So then, by Anonymous Coward · · Score: 0

    I think the server processes will be in HTML and Javascript, and the frontend GUI will be done in SQL.

  78. Summary is Incorrect by djowatts · · Score: 1

    If you actually read the article, you will see that .NET isn't being dropped. It is proposed that there will be three ways to develop, first with the native C++ using and updated form of the Win32 API, .NET development, with some access to this variation on Win32 and a combination of HTML5 and Javascript. Nowhere does it say that .NET is being dropped.

  79. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  80. Re:So then, by Dog-Cow · · Score: 1

    You are ignoring the fact that the Win32 API started life in the early nineties (Win32s and Windows NT 3.x), and has been maintained and updated ever since. And Win32 itself is just an extension of Win16, dating back to at least Windows 3.0 (I don't know whether the API for 1.x and 2.x were the same). The products are updated and support is dropped. The development environments, not so much. Witness the continued support for Windows XP, the extended support FoxPro and the like. Microsoft provides support for well over a decade, if such is mandated by its customers.

  81. erroneus does blackmail attempt on slashdot? by Anonymous Coward · · Score: 0

    http://slashdot.org/comments.pl?sid=2261720&cid=36545928 Is it because you trolled someone http://slashdot.org/comments.pl?sid=2253808&threshold=-1&commentsort=0&mode=thread&pid=36521452 and they shot you down on every so called point you tried to make and they did it with documented facts anyone could see? I saw you run like a whipped dog 10 times there in fact, and for your starting trouble with others you threaten to blackmail? Very intelligent (not).

  82. Applying critical thinking to Microsoft here by Anonymous Coward · · Score: 0

    I see they are the #1 most used computing platform on earth. If they do what you said erroneus, it must be a formula for success then. Argue with the numbers and reality.

  83. On PC's and Servers that is by Anonymous Coward · · Score: 0

    See subject above, small edit/correction for clarity/accuracy.

  84. Re:Not quite... by dzfoo · · Score: 1

    Java is related Javascript, as much related is.

    --
    Carol vs. Ghost
    ...Can you save Christmas?
  85. Erroneus' anti-MS rants FAILS history by Anonymous Coward · · Score: 0

    Of getting his ass kicked about Microsoft when he rants vs. they:

    E.G. #1: http://slashdot.org/comments.pl?sid=1681772&cid=32556164

    On Windows Server & SQLServer Uptime ( @ NASDAQ 24x7 too, with Windows working as the "official trade data dissemination system" where it's been up, solid, 24x7 for YEARS now (almost a decade via clustering))

    (Which ErroneOus couldn't disprove!)

    ---

    E.G. #2 - http://it.slashdot.org/comments.pl?sid=1681772&cid=32525656

    On Windows 7 having less known unpatched bugs than Linux kernel 2.6x AND, your inability to show workarounds as apk had, for Windows 7 2 bugs @ that time no less vs. more in Linux again, kernel only, NOT AN ENTIRE DISTRO EVEN (vs. Windows 7, a complete OS 'distro').

    ---

    I wouldn't use history were I you, erroneOus, yours in your rants about Microsoft don't look very successful up there...

  86. Re:Not quite... by hairyfeet · · Score: 1

    Does it still get UPDATES, you know, those things Linux users are afraid to implement for fear Linus' latest Goatse on the kernel will cause their installation to fall like a house of cards? if so then it counts but I doubt it.

    Meanwhile you get on average a DECADE of updates with Windows, which means the machine will be practically ancient before you go out of support which in a dead economy is a GOOD thing people!

    The sad part is I'm looking at 4 1.4GHz PCs that would be just perfect for Linux, yet I'm gonna have to use the XP Home key on the sides and reinstall Windows even though it will be slow as shit with just 1.4GHz of CPU and 512Mb of SDRAM, why?

    Because in this age of zero days having an unpatched OS is frankly insane, yet that is EXACTLY what I was told to do, time and time again, even here on /. if I want to run Linux on them, why? Because unless you are a geek and have time to waste on "forum hunts" Linux distros (So far I've tried Ubuntu, PCLOS, and Mepis, the results are the same) will shit themselves when you update them!

    There is NO easy way that I've found to apply JUST the security updates, and since third party software is often tied to which kernel you run LTS is a codeword for "really old outdated software" that may/may not have exploits out.

    Don't you just find it damned sad, doesn't it bother anyone here, just a little, that there is NO reason why Linux couldn't be on these PCs and on store shelves on nice new boxes, if it weren't for the incredible ego of just one man? In 1993 Torlvalds decided he don't like ABIs, since he couldn't just take a dump on the kernel structure if there was an ABI since he would totally break it. This was in 1993, times were different then, and maybe the memory saved was worth it. BUT IT AIN'T 1993 ANYMORE!

    IS there anyone, anyone at all, that truly believes that Torvalds is smarter than the ENTIRE computer industry? Because everyone, and I do mean everyone, has an ABI EXCEPT Linux. OSX, BSD, Solaris, Windows, OS/2, and you know what they have in common? They can apply updates without drivers shitting themselves! Now I have had people here tell me with a straight face I should tell Joe average to learn to do forum hunts, or even learn to recompile fricking drivers, but you know what? he shouldn't have to!

    Call me crazy but I still hope that one day I'll be able to walk into Walmart and see Linux laptops right next to Windows, and buying devices will be as simple as "look for the penguin on the box". it COULD be that way you know, if it weren't for a single douchebag, one single asshole holding back the entire ecosystem...Linus Torvalds. So maybe one day we'll get lucky and he'll retire, after which an ABI will quietly be added and people will go "Wow, everything just works!" and shelves will have Linux and all will be good. But as long as pouring a bunch of Bash commands after a multi-hour forum hunt is still considered an acceptable way to deal with drivers? Well that day will never come.

    --
    ACs don't waste your time replying, your posts are never seen by me.
  87. Re:So then, by erroneus · · Score: 1

    Am I ignoring it? Can you really run things written for Windows NT 3.5 on a Windows 2008 box? Perhaps some, but I'll bet the apps written for NT 3.5 will refuse to run on 2008 and if they did run, it wouldn't likely run well or 100%. Likewise, apps written for a 2008 environment isn't likely to work for NT 3.5. There is certainly a progression, but what you confuse as being a stable and consistent platform, I see as a developing and changing migration path... migration path... hrm... sounds familiar. I think I heard some Microsoft people describe upgrading from one version of Windows to the next as just that. They encourage and eventually require moving to new versions of Windows just as they do everything else.

    In any case, you can't seriously be suggesting that the Win32 of the 1990s is 100% compatible with the Win32 of today can you? I know Microsoft does maintain a lot of backward compatible code in their kernels but it is my understanding that they have rightfully been cleaning a lot of that out which has resulted in faster and more efficient kernels. And besides that, it's more than the core kernel API we are talking about... in fact, that's what this discussion is about -- Microsoft dropping an API for which developers have been trained and encouraged to write.

    So let's ask some true or false questions:

    1. Microsoft pushed a programming technology only to have it discontinued later.
    2. Microsoft's business model is about selling the same "new thing" with changes and updates to the same customers repeatedly.
    3. Microsoft discourages the use of older products in favor of their newer products.
    4. VB6 still encouraged and supported for developing applications for current generations of Windows.
    5. Microsoft has supported and encouraged 64bit computing while refusing to support a 64bit version of Silverlight.

    (Yes, I know Microsoft has recently changed this position, but what does that say about their commitment history with regards to silverlight?)

  88. Re:So then, by gabebear · · Score: 1

    this is the bit I don't get. Nobody would write any system in HTML5+js. It would be the presentation layer only, and be accessed via nice, easy-to-use APIs that bring the barrier of GUI development down. The meat of the app would be written in C++ or C#.

    For apps that have very little meat you can. There seem to be a lot of apps like this in business(glorified spreadsheets and specialized calculators).

  89. Re:Not quite... by pnutjam · · Score: 1

    I'm always amazed by how many companies don't leverage these free (included w/ windows) tools. And pay someone to run around like a chicken with their head cut off, fixing symptoms here and there.

  90. Re:Not quite... by pnutjam · · Score: 1

    I have tried Ubuntu, but none of the others you mentioned. I switched to OpenSUSE because they have the best hardware support. For an old machine like that you should look at Linux mint xfce edition, or possbily something like puppy linux, run it off a CD to test.

  91. Publicly available FALSE & disproven informati by Anonymous Coward · · Score: 0

    Which U ran from in subsequent posts beneath yours here:

    http://slashdot.org/comments.pl?sid=2253808&threshold=-1&commentsort=0&mode=thread&pid=36521452

    As well as your blackmail threat here http://slashdot.org/comments.pl?sid=2261720&cid=36545928

    are both libel and blackmail. Threats to someone's employment possibilities definitely is. No questions asked. Defamation of character as well.

    Then, since it's false, it is blackmail AND libel.

    (And, that 2nd link is a clear threat to someone, no questions asked).

    You started it, and you can't handle it and try BLACKMAIL?

    Clue/new NEWS/NewsFlash: Attempted threats to people regarding their livelyhood IS BLACKMAIL!

    You are a very foolish person!

    (You start trouble, & you choose to troll others and lie about them as well as try to blackmail them after you had every falsehood you post about others disproven (and you could not argue vs. documented proofs in links which you ran from)).

  92. Re:Not quite... by ckaminski · · Score: 1

    No shit. For fucks sake, how hard is it to make a stable driver interface? We've invented pretty much every stream and message-driven class of hardware imaginable...

    No, it's the damn architecture wonks who want purity of essence. If the GCC and libc guys can get it straight, why not the kernel devs?

  93. Re:Not quite... by hairyfeet · · Score: 1

    The problem is NOT getting it to work initially, that part is fine. Sure I often have to "tweak" or play forum hunts but you know what? I've been building PCs since the early 90s so that isn't a problem FOR ME.

    What IS a problem, and which makes me want to fly all the way to Finland to shake that little twerp Linus until he makes sounds like the Swedish chef, is that I can't give Linux to a customer because my choices are 1.-Disable ALL updates and hope they NEVER need any software that I didn't already install (because many apps are tied to which kernel you are using) and worse leave them with outdated flash and hope some zero day doesn't bite them in the ass, or 2.- take a fricking bath on the machine as I will have to provide lifetime support as the first time they allow it to update it WILL shit itself and die with regards to at LEAST one driver if not more.

    Now that is just completely unacceptable. I have Windows boxes in the field for over 8 years now, fully patched, with NO problems (because honestly keeping a Windows box clean only takes a teeny amount of common sense which isn't hard for me to teach) and which will continue to run right up to the XP EOL.

    Now so far I've tried Ubuntu (both regular AND Mint) PCLinuxOS, and Simply Mepis and ALL OF THEM have yet to survive a single update with 100% working hardware. Not a single one. it is ALWAYS something, sound, graphics, wireless, NIC, it is always something. What am I supposed to tell my customers? Tough shit I hope you don't need sound? You better learn the make/model/rev of EVERY piece of hardware in this box and become a wizard at forum hunts and tweaking bash commands? Tell them to learn to rebuild and recompile drivers? I expect a machine to last at LEAST 7 years, so if OpenSUSE has good support try this: download the version from 7 years ago (or the oldest version there is, whichever is newer) and then try to update it to current. i bet at least one if not several drivers WILL break!

    The problem with the community is this: Linux is built BY geeks FOR geeks and geeks think anything that is easy FOR THEM must be easy for everyone else, and honestly nothing could be further from the truth. Hell my clueless dad installed Windows 7 when he got impatient and wouldn't wait for me to come do it. Know how many things were broken? NONE. Zip zero zilch nada squat. hell it downloaded all the drivers, did all the work, even pointed him to a free AV at first boot. The only thing I had to do was show him how to get Firefox and later how to get Comodo Dragon. that's it.

    And THAT my friend is what Linux is competing against. Folks aren't gonna go from 'clicky clicky" to learning bash, or memorizing hardware lists, and they sure as hell aren't gonna learn how to rebuild drivers! No my friend the problem isn't the initial install, it is the fact that in a year or less when the latest updates roll around the machine will either be an unpatched zombie waiting to get pwned or it will shit itself and die. And it takes just three hours of my time for the cost of a forum hunt to be greater than the cost of a Windows license, and that is of course if there is even a fix out there! Some things I've seen not get fixed for weeks, weeks I tell you!

    So I'm glad it works for you, I'm glad you are able to waste time with forum hunts and fixing broken drivers, or have the brass balls to run all over the net with a badly out of date pile of software. But I deal with normal folks 6 days a week, the average Joe that you see in line at the bank. And he isn't gonna jump through those hoops or take CS courses just to run Linux. When I can take Linux OS 12 and update it to Linux OS 13 and NOT have a single broken driver? Then and ONLY then will it be ready for my customers. But sadly as long as Linus is there to Goatse the kernel I doubt that day will ever come, sorry.

    --
    ACs don't waste your time replying, your posts are never seen by me.
  94. Re:So then, by gbjbaanb · · Score: 1

    for all apps, I worked at a company (a few years back) that embraced the HTA technology MS touted. That was basically web client to back-end processes. It was sold for millions to banks and mortgage brokers and the like, and was scalable and fast. You can't describe it as a 'little meat' product.

    I think the most likely candidates not to use this approach are the tiny ones where the overhead in developing a gui and a back-end process shows up, for all others its not a problem.

  95. Re:So then, by LO0G · · Score: 1

    Actually many (most?) applications written for NT 3.5 will still run on Windows 7. Some set of applications need to have compatibility shims added (most of which come with the OS) but yes, they'll still run.

    There's certainly a set of applications written for NT 3.5 that won't work on Win7. But that set is vanishingly small.

  96. Re:Not quite... by pnutjam · · Score: 1

    Every distribution you list is based on debian or worse (ubuntu). I have OpenSUSE machines that have run for 5 years with no problems, I update them and they work. My time is also pretty valuable, and not only my paid time. I have 3 children under the age of 9 on Linux, plus my wife. It just works for them and they don't get viruses. Any problems I have ever encountered ar during the initial build. Once it works, it works.

    Ubunti is know for screwing things up with updates. There are plenty of more conservative distributions. OpenSUSE and Fedora are more cutting edge, but OpenSUSE provides a reasonable support timeframe for their releases. Puppy linux is a great one for long term support of older hardware.