|
It is the first time I interfere in such a debate. You made me excited to reply back.
"no portable code"
Portability is not as important as Sun is trying to market for, did you see how would a Java app look on Windows? or how slow it is?
"attached to it's 'new' operating system"
I would like to have access to every tiny feature of the operating system, I like cool GUIs and I like fast apps. What I don't like is writing a generic slow code that will cost me more time and run slower (not to mention unhappy boss).
MFC is better than VB! It produces fast code, but did you notice that its code is UNPORTABLE? Did you notice that it would take double the time VB would take? Did you notice that the world doesn't rotate arround developers and there are other parties that requires your project to finish fast even on the expense of the performance (today performance between MFC and .NET application is negligible)?
"And that's it, ms will eventually discontinue C# and the like some few years from now"
This would happen with any programming language, who is now programming business apps in Pascal? ASM? Fortran? BASIC? COBOL? console C++? SmallTalk?
Maybe the world will abandon the OO languages the same way it abandoned the procedural languages and move to a new progamming style, I think this would be the only way that C# will be replaced. And if this happens then you can update your knowledge and follow the new trend the same way I moved from MFC to VB then to C# Isn't this why developers are highly paid?
Cheers
Make it simple, as simple as possible, but not simpler.
|
|
|
|
|
Forgive me sir, i was pointing my opinion. But look, i'm one of those crazy guys who is amazed by the WTL. I'm a multiple-inheritance-class yunkie freak, with some nasty experiences on trusting bussines-focused people. I build my own libraries (one work that never ends), i like using raw operating system access, i like it low, and i like it as high as c++ can be. The needs are always the same, what i don't understand is why people uses more and more bigger dependencies, feeding lots of somehow unnecessary code to the processor, yes, machines are pretty fast now, is that a valid excuse to make commands take double to process?
Well, you see? what doing things the WTL way makes of some programmers...
Regards.
|
|
|
|
|
Jan Rodriguez wrote: what i don't understand is why people uses more and more bigger dependencies
and yet:
Jan Rodriguez wrote: I build my own libraries (one work that never ends)
so, your frameworks are not dependencies? I seriously dont get that reasoning.
Jan Rodriguez wrote: i like using raw operating system access
kernel32 not raw enough for you?
in .net you can use system drivers, so I still dont understand your reasoning.
|
|
|
|
|
...so I voted generics and nullable types.
However, there are much more things in .NET 2.0 I'm using which are not listed in the poll, such as anonymous delegates, return yield, and lots of new WinForm controls such as TableLayoutPanel, SplitContainer, ToolStrips, MenuStrips, DataGridView, etc.
Regards
Thomas
Disclaimer: Because of heavy processing requirements, we are currently using some of your unused brain capacity for backup processing. Please ignore any hallucinations, voices or unusual dreams you may experience. Please avoid concentration-intensive tasks until further notice. Thank you.
|
|
|
|
|
I've migrated a few things over to 2.0 (a major pain in the arse). most of our stuff here at work is asp.net so seeing as how they re-invented asp.net for 2.0, the cost of migration on that is too high.
and just when you get comfortable with a nice looking programming language, they come out w/ 3.0 (looks pretty darn cool IMO).
I cant wait to annoy the world w/ method extentions!!!!
|
|
|
|
|
MadHatter ¢ wrote: they re-invented asp.net for 2.0, the cost of migration on that is too high.
I agree on that. I have a (not much) old ASP.NET 1.1 application. The migration would require rewriting a lot of stuff, so it stays 1.1.
But for new applications, I really like ASP.NET 2.0, especially Master Pages.
|
|
|
|
|
non-asp migration is a pretty arduous task, but I'd say asp conversion is a total waste of time (may as well re-write it).
it seems like they looked at "what would be the hardest thing for people to change?" then they depricated it.
|
|
|
|
|
Dario Solera wrote: migration would require rewriting a lot of stuff, so it stays 1.1.
Well, I've migrated some ASP.NET 1.1 apps to 2.0.
The migration wizard ran smoothly, and the only problem were with special characters I've had with files that wasn't UTF8. However, that took notime to fix, and I gain access to the (a-lot) better tools that 2.0 languages has (Generics, anonymous delegates, ?? operator, etc.), the 2.0 Framework (Membership, ASP.NET Controls, better System.Xml, Dynamic Methods) and the VS2005 which is a lot better than VS2003.
|
|
|
|
|
our asp.net apps contain hundreds of thousands of lines of code, and there are 4 or 5 of them. We did an initial migration and after a couple of weeks dropped it.
there is the physical migration that vs.net does, but after that there are a ton of logical, and api level modifications that have to be done, and the logical ones create huge potential breaking changes to our apps, that again will cost too much to 1. implement 2. debug and 3. migrate to production.
|
|
|
|
|
I hear great thing's about 3.5 ohh wait 4.0 it much better, and 5.0.........
|
|
|
|
|
|
Generics
Master Pages
Kevin
|
|
|
|
|
Generics, is obviously the most used and useful on the list but Master Pages are a godsend when having to write websites.
|
|
|
|
|