Which platform?
-
Nishant Sivakumar wrote:
Well pre-2003 would be 10 years and not 5.
like many people who aren't doing web stuff, i'm still writing native apps *. the world didn't switch to .Net when VS03 came out. * in fact, i'm still writing apps using a 16-bit IDE. (Clarion)
image processing toolkits | batch image processing | blogging
No way! I'm using Clarion too. We are just now transitioning to C#/.NET and we are calling things back and forth between Clarion and C#. Jim
-
Ahh well, to be honest I always thought the voting system was silly anyway and I thrive on obscurity! :)
John Cardinal wrote:
and I thrive on obscurity!
Fnord.
This statement was never false.
-
Nishant Sivakumar wrote:
Limitations like lack of compile-time templates and inline assembly would be your fault then?
:laugh::laugh:.. come on!! be fair to C#, unless you prefer to code in VB X| :laugh:
Smile: A curve that can set a lot of things straight! (\ /) (O.o) (><)
What? C++ isn't an option? Its C# or VB? :confused:
This statement was never false.
-
Shog9 wrote:
That said, C++ still wins out if you're looking to go cross-platform.
Not true at all, MONO is just about complete for .net 2 and will be soon for .net "3" and it's supported on many different platforms including windows, linux, mac, bsd etc: http://www.mono-project.com/Supported_Platforms[^] And even better you don't even need to recompile your assemblies, you just copy them over and run the program. Can't beat that.
How's the performance? Last I looked the metrics were way out on Mono in comparison to Window's implementation.
This statement was never false.
-
No way! I'm using Clarion too. We are just now transitioning to C#/.NET and we are calling things back and forth between Clarion and C#. Jim
JimAtImpac wrote:
calling things back and forth between Clarion and C#.
that can't be any fun :)
image processing toolkits | batch image processing | blogging
-
So, we are just about to begin a new project. We're now deciding which platform should be used. The bosses asked me about this, and I replied that my bet was on C++ and Win32, as usual. A colleague voted for Java ( X| ) and someone there even dared to suggest VB ( X| X| ). At any rate, the bosses are worried about the future of C++ and Win32. They read somewhere that Microsoft's next OS won't be supporting anything but .NET Framework, so they are not convinced that C++ with Win32 should be the best option. So I'd like to ask for your opinion about this... C++ still has a future? Should we choose C# and .NET over good old C++ and Win32? Thanks.
A polar bear is a bear whose coordinates has been changed in terms of sine and cosine. Personal Site
I think your question needs to be divided into two, i.e. should I use C++ or C# and, win32 or .NET. Remember C++ (or more correctly C++/CLI) is a full .NET language. Although most examples on the net are now C#, MS has never said C++ is on the way out. However that can't be said for win32 (over .NET), so may be you should also consider C++ and .NET.
-
Nishant Sivakumar wrote:
Well pre-2003 would be 10 years and not 5.
like many people who aren't doing web stuff, i'm still writing native apps *. the world didn't switch to .Net when VS03 came out. * in fact, i'm still writing apps using a 16-bit IDE. (Clarion)
image processing toolkits | batch image processing | blogging
re:* my condolences.
-
Chris Losinger wrote:
then i suggest MS start telling people about this plan. 5 years is pretty tight, when you're talking about rewriting 99% of all Windows applications, especially if they have to target a moving-target framework like .Net.
Well pre-2003 would be 10 years and not 5. And ever since .NET was out around 2000-2001, it was evident that, that'd be the future of writing apps on Microsoft OSes. People were given adequate time to move on to newer technologies.
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. (*Sample chapter available online*)Nishant Sivakumar wrote:
Well pre-2003 would be 10 years and not 5. And ever since .NET was out around 2000-2001, it was evident that, that'd be the future of writing apps on Microsoft OSes. People were given adequate time to move on to newer technologies.
Speak for yourself. Since when is newer necessarily better for everyone? By that logic, you would automatically embrace the newest language that came out whether it was a waste of space or not. Personally, I see .NET as Microsoft's version of Java. I'm happy enough with Java when I feel a need for it, and I'm happier again working with C++ which is also cross-platform, and compiles to native code easily. Just because you're a fan doesn't mean it's the best thing around.
-
What? C++ isn't an option? Its C# or VB? :confused:
This statement was never false.
-
So, we are just about to begin a new project. We're now deciding which platform should be used. The bosses asked me about this, and I replied that my bet was on C++ and Win32, as usual. A colleague voted for Java ( X| ) and someone there even dared to suggest VB ( X| X| ). At any rate, the bosses are worried about the future of C++ and Win32. They read somewhere that Microsoft's next OS won't be supporting anything but .NET Framework, so they are not convinced that C++ with Win32 should be the best option. So I'd like to ask for your opinion about this... C++ still has a future? Should we choose C# and .NET over good old C++ and Win32? Thanks.
A polar bear is a bear whose coordinates has been changed in terms of sine and cosine. Personal Site
-
So, we are just about to begin a new project. We're now deciding which platform should be used. The bosses asked me about this, and I replied that my bet was on C++ and Win32, as usual. A colleague voted for Java ( X| ) and someone there even dared to suggest VB ( X| X| ). At any rate, the bosses are worried about the future of C++ and Win32. They read somewhere that Microsoft's next OS won't be supporting anything but .NET Framework, so they are not convinced that C++ with Win32 should be the best option. So I'd like to ask for your opinion about this... C++ still has a future? Should we choose C# and .NET over good old C++ and Win32? Thanks.
A polar bear is a bear whose coordinates has been changed in terms of sine and cosine. Personal Site
MS is working on a os based puerly on C#, I've seen it on channel 9(msdn). It's in it's infancy, it barely had a small kernel and a couple commands. It will be the future. I used to prefer native apps but with mono you also get cross-platform apps and that's a big plus for me; .net will advance alot in the next years as well as C# as the main .net language. I'd say go for C#.