Who plans on using .NET?
-
I can't imagine ever using it. MS's whole strategy on this seems to be that their/our current business model (selling softwae for use on personal computers) is flawed, so we've all got to move to a model where everything runs on a server. A new OS, a new language.. out with the old, in with the new. They do this every few years: they decide that current technology has flaws, so they throw everything out and start over. (DOes anyone remember the claim that COM was going to replace all of the other Windows APIs?) But users don't want to do that - that was proven by IBM as early as the PS/2 - OS/2 days - so we'll be left once again with systems that have a hodgepodge of competing libraries, partial OS's, and hybrid applications. Another maintenance nightmare, in other words.
I wouldn't say that Microsoft is solely responsible for the shift from client side to server side applications (ASP model and Sun's Java for instance). What Microsoft is bringing to the table is what the Fortune 500 companies are asking for. I can see your point on the consumer side, but unfortunately most of the money is made on the business side, and it usually wins. It is true that things usually don't get better... just different. But isn't that why we are in this business; to learn something new everyday, and to figure out how to plug the wholes in the new systems, its the challenge that drives us. Be careful what you ask for ... If it actually did become easy and straight forward, many of us would be out of work, or extremely bored :)
-
I can't imagine ever using it. MS's whole strategy on this seems to be that their/our current business model (selling softwae for use on personal computers) is flawed, so we've all got to move to a model where everything runs on a server. A new OS, a new language.. out with the old, in with the new. They do this every few years: they decide that current technology has flaws, so they throw everything out and start over. (DOes anyone remember the claim that COM was going to replace all of the other Windows APIs?) But users don't want to do that - that was proven by IBM as early as the PS/2 - OS/2 days - so we'll be left once again with systems that have a hodgepodge of competing libraries, partial OS's, and hybrid applications. Another maintenance nightmare, in other words.
Oh yeah... And Microsoft recently took over most of the Pizza home order services, and now secretly adds drugs to make all developers addicted to the Microsoft logo. "Software as a service" has been requested by many companies - since software development is expensive, and revenues are low due to heavy piracy (No, it's not the success of OpenSource). And MS is not the only major company that pushes SaaS forward. As for COM, Microsoft did go a painful way to make all new API's COM based, but it simply didn't work out. Now, should they go on if they see they were wrong, or should they stop? For .NET, It is great for creating "good old" Desktop Applications as well. As for now, you cannot redistribute them - remember it's a Beta 1, and not production code. A Beta 1 usually would go only to a few selected beta testers (and warez sites). MS released this to the public under intense pressure of developers. Now, one runtime for all Windows development languages doesn't sound like a maintenance nightmare to me. I remember, only five years ago, almost everybody complained about MS' tendency for "backward compatibility". Throw away DOS, throw away Win3.x support... but now when they move forward, it's wrong again.
-
I was just wondering how much .NET has caught developer's interests: - How many devs. have written more than 'Hello World' with it? - How many devs. have development plans in the works? - How many devs. are excited and how many don't care? Since I am in the process of writing several components and applications in .NET, I would like to know if others are "going boldly where no man has gone before." :)
- I started to do more than "Hello World", a real life tutorial, and I'm thinking about a *real*project. Currently, nothing, but looks like I find some time to work on it in Feb/March. - Our current development will go on MFC/ATL based, I see no sense in completely rewriting. If the smoke settles on .NET I would see if it payss to move the UI to .NET, and allow additional PlugIn's to be written as .NET code (C#, most likely). - I'm excited
-
I was just wondering how much .NET has caught developer's interests: - How many devs. have written more than 'Hello World' with it? - How many devs. have development plans in the works? - How many devs. are excited and how many don't care? Since I am in the process of writing several components and applications in .NET, I would like to know if others are "going boldly where no man has gone before." :)
I think .NET is the best development platform out there. Microsoft has proven that they are listening to their customer needs, and are responding aggresivly to requests. Troy, I think it would be a wise investment for you to have extensive knowledge on .NET, b/c I'm sure that .NET will truly become the Next Generation platform, and I know I wouldn't want to be left out. :)
-
I think .NET is the best development platform out there. Microsoft has proven that they are listening to their customer needs, and are responding aggresivly to requests. Troy, I think it would be a wise investment for you to have extensive knowledge on .NET, b/c I'm sure that .NET will truly become the Next Generation platform, and I know I wouldn't want to be left out. :)
I was slightly confused when reading the second half of your reply, then I realized that I left a couple words out of my original posting.... which by the way is now updated :). Actually I am currently in the process of designing applications and components for .NET, I just wanted to see if I was alone.
-
I was just wondering how much .NET has caught developer's interests: - How many devs. have written more than 'Hello World' with it? - How many devs. have development plans in the works? - How many devs. are excited and how many don't care? Since I am in the process of writing several components and applications in .NET, I would like to know if others are "going boldly where no man has gone before." :)
I am doing a lot of processor-intensive numerical work (mostly medical image-processing) and haven't gotten a straight answer from anyone on how much of a performance hit .NET will inflict on my code. I can't afford to spend any time investigating .NET until I know how it will handle intensive floating point calculations on large data sets. I gave up quickly on Java several years ago because it's not at all suited for numerical work. I anticipate that .NET will have the same problem: if you're taking FFTs and Wavelet transforms of video streams, you can't afford many of the niceties that .NET offers, even if you're running a 1 GHz machine with 1 GB RAM. He was allying himself to science, for what was science but the absence of prejudice backed by the presence of money? --- Henry James, The Golden Bowl
-
I was just wondering how much .NET has caught developer's interests: - How many devs. have written more than 'Hello World' with it? - How many devs. have development plans in the works? - How many devs. are excited and how many don't care? Since I am in the process of writing several components and applications in .NET, I would like to know if others are "going boldly where no man has gone before." :)
I will! <jumps up and down waving arms> In terms of Windows apps I still like MFC, but for Web apps ASP.NET is just so nice. Whole chunks of code simply fall away when you port to ASP.NET, and writing ASP components using C# is a doddle. It's so easy that you wonder how much plumbing must be underneath to make it work so smoothly - but I guess this is Somebody Else's Problem. Besides, precompilation, JITing, cacheing, ADO.NET, XCOPY installation, process recycling, no downtime when installing new components or changing settings, config.web, no more resource leaks and excellent performance makes it a no-brainer. cheers, Chris Maunder
-
I am doing a lot of processor-intensive numerical work (mostly medical image-processing) and haven't gotten a straight answer from anyone on how much of a performance hit .NET will inflict on my code. I can't afford to spend any time investigating .NET until I know how it will handle intensive floating point calculations on large data sets. I gave up quickly on Java several years ago because it's not at all suited for numerical work. I anticipate that .NET will have the same problem: if you're taking FFTs and Wavelet transforms of video streams, you can't afford many of the niceties that .NET offers, even if you're running a 1 GHz machine with 1 GB RAM. He was allying himself to science, for what was science but the absence of prejudice backed by the presence of money? --- Henry James, The Golden Bowl
you just can't beat plain C for zipping across a huge BYTE array (unless you write you own hand tooled assembly, in which case you wouldn't be reading this anyway). -c
-
you just can't beat plain C for zipping across a huge BYTE array (unless you write you own hand tooled assembly, in which case you wouldn't be reading this anyway). -c
There are indications that good use of partial template specialization in C++ can beat C, and even FORTRAN, for matrix computations (unless you hand code each loop in C). This is one cause for frustration in MS's lack of support for PTS. See Todd Veldhuizen's articles in DDJ over the past several years, or visit the Blitz++ web page. He was allying himself to science, for what was science but the absence of prejudice backed by the presence of money? --- Henry James, The Golden Bowl
-
I was just wondering how much .NET has caught developer's interests: - How many devs. have written more than 'Hello World' with it? - How many devs. have development plans in the works? - How many devs. are excited and how many don't care? Since I am in the process of writing several components and applications in .NET, I would like to know if others are "going boldly where no man has gone before." :)
I haven't yet written a single line of code with it; my ideas are too large to just implement. A good design and architecture comes before. I will be using primarily C#/C++ development with it. VB in my opinion is for test jigs. -Erik
-
I can't imagine ever using it. MS's whole strategy on this seems to be that their/our current business model (selling softwae for use on personal computers) is flawed, so we've all got to move to a model where everything runs on a server. A new OS, a new language.. out with the old, in with the new. They do this every few years: they decide that current technology has flaws, so they throw everything out and start over. (DOes anyone remember the claim that COM was going to replace all of the other Windows APIs?) But users don't want to do that - that was proven by IBM as early as the PS/2 - OS/2 days - so we'll be left once again with systems that have a hodgepodge of competing libraries, partial OS's, and hybrid applications. Another maintenance nightmare, in other words.
I don't think you actually understand much about .NET. The software service aspects of .NET are only one portion of it, and a small portion at that. You don't have to use them, and very few companies will IMO. The real benefits of .NET are the ability to run your apps on CE/MacOS X/Itanium, etc.. unmodified. MS has learned that people won't create versions of their software for other architectures (such as what happened with PPC, MIPS and Alpha), so you have to bring the applications to the architecture, not the other way around.
-
I am doing a lot of processor-intensive numerical work (mostly medical image-processing) and haven't gotten a straight answer from anyone on how much of a performance hit .NET will inflict on my code. I can't afford to spend any time investigating .NET until I know how it will handle intensive floating point calculations on large data sets. I gave up quickly on Java several years ago because it's not at all suited for numerical work. I anticipate that .NET will have the same problem: if you're taking FFTs and Wavelet transforms of video streams, you can't afford many of the niceties that .NET offers, even if you're running a 1 GHz machine with 1 GB RAM. He was allying himself to science, for what was science but the absence of prejudice backed by the presence of money? --- Henry James, The Golden Bowl
Well, clearly there will be a performance hit for .NET. How much, remains to be seen. It should be noted though that the performance benchmarking i've done so far has shown (even at this early beta with lots of debug and unoptimized code) that .NET is already significantly faster than Java, even with HotSpot.