Printable View
So I guess that it's safe to say that if we get into .NET, we can forget about pointers, we'll use the "references".
Plus, correct me if I'm wrong, but Linux is taking quite the jump lately, alot of companies(IBM) and governments(Germany, China, etc.) are into Linux. I'm quite confident that Linux will be the next big thing in business, just like Windows was.
I'll go with the late 80's/early 90's model, with SCO (and various other UN*X vendors), OS/2, NeXt...catch me in 10-15 years if linux makes strides in the desktop market, I'll buy you a beer if yer right ;)Quote:
Originally posted by YourSurrogateGod
Plus, correct me if I'm wrong, but Linux is taking quite the jump lately, alot of companies(IBM) and governments(Germany, China, etc.) are into Linux. I'm quite confident that Linux will be the next big thing in business, just like Windows was.
Buisness server side, yes...I will give you that. Personal desktop market...that's where I do not see much market gain.
Unless the U.S and MS suffer an economic catastrophe, Windows will be dominating the desktop OS market
I always find the slow performance in the languages which doesnot have pointers. Thanks DMR for providing pointers in C.Quote:
Originally posted by Latem
I share the same concerns. It just doesnt make sense, how even if .NET is the "native" api for Longhrn, it will solve this issue. whenever you have intermediate code and garbage collection, you lose performace, and there is no way around it. I guess everything will be slower? and MS just doesnt care cuz we will all have good computers anyway. Or am I wrong about this?
Latem
I don't have any special interest in any of the OS we have at present but I love C/C++ always.
regards,
collin.
IMHO, C++ is the best all-around programming language.
Today I was writing some GDI+ apps in C++/.NET. Microsoft must speed up the IDE in Visual Studio for .NET development. Terrible slowdowns are common when working with a form with just three or four controls... and my machine is pretty fast, XP2600/512k, 1GB RAM.
So,.NET is slower not only in terms of runtime performance developing with WinAPI or MFC (or WTL), but also in the speed of the IDE.
Ok, ok, I give up, you guys chased me into a corner on this. God it's going to be painful to get used to .NET now. Probably the only thing that I'll use Longhorn in the future is to play games on and .NET, but I'll definitely have Linux.
Hi
no dought .NET performence is not really good on WIN32 OS , that is why i dont like it at all.
But as i was seeing the longhorn beta 2 or 3 days before , I found that longhorn is quite fast i did not find any perfromence dif as compared to my WINXP.
I was really expecting that due to completely based upon .NET it would be quite slow as my managed C++ program when i run them on my WIN32 OS.
So now my point is if longhorn perfromence is quite OK , why cant MS Make .NET perfromence better in WIN32 OS.
Is it due to routing of .NET calls to win32API.
Now my second point is about the individual specialities of dif langauges
Such as VB for Business App , C++ for Scientific and Perfromence Critical App etc.
With .NET , languages are no more than syntax , to access same .NET libraries.
wont it effect the productivity of future softwares market.
SO Why a programmer would learn new lanaguges , if i have to do programming in .NET i would learn say C# and good byes to all other languages.
I think .NET performance will be much faster when developing under Longhorn.
.NET learning curve is steep... from time to time I try to program something and I can't become comfortable with it ... I think I've developed a good affinity with WinAPI.
Yes. As winapi on win2k now.Quote:
Originally posted by indiocolifa
I think .NET performance will be much faster when developing under Longhorn.
Also winapi calls need a translation.
I'm worried about the winapi in longhorn. Will C/C++ be the same powerful language as it is now in win2k?
regards
collin.
that's for a 2600/512k, 1GB RAM machine..Quote:
Originally posted by indiocolifa
IMHO, C++ is the best all-around programming language.
Today I was writing some GDI+ apps in C++/.NET. Microsoft must speed up the IDE in Visual Studio for .NET development. Terrible slowdowns are common when working with a form with just three or four controls... and my machine is pretty fast, XP2600/512k, 1GB RAM.
remember that many clients don't have such (fat) computers.
I can't dare to ship a .NET App. to a 500MHz/128MB RAM Client... :)
So what wold be the overall concensus on whether to embrace the new .NET(even though I still have reservations about it) or just jump the Windows bandwagon and get on the Linux train?
/*just currious*/
for me I want to catch the linux (open source in general) train to feel myselft a (free) programmer,, not a MS products user..Quote:
Originally posted by YourSurrogateGod
So what wold be the overall concensus on whether to embrace the new .NET(even though I still have reservations about it) or just jump the Windows bandwagon and get on the Linux train?
/*just currious*/
but I must still improve my .NET skills because the market in Egypt is too much MS oriented :(
Your poor guy.Quote:
Originally posted by hspc
for me I want to catch the linux (open source in general) train to feel myselft a (free) programmer,, not a MS products user..
but I must still improve my .NET skills because the market in Egypt is too much MS oriented :(
.NET will probably become the standard (for Windows) eventually, so it cant really heart to learn it. You never know what your next job may require.Quote:
So what wold be the overall concensus on whether to embrace the new .NET(even though I still have reservations about it) or just jump the Windows bandwagon and get on the Linux train?
Latem
Oh well, I guess I should learn how to do that. I just hope that I can make some of the things that I did in WinAPI and that it could work draw just as well and quick. The bezier exercise for example.