Printable View
hello,
first i know that my question may look silly and repeated. and i realize that i may c replies like "look at documents of C# at microsoft.com"..........
but in fact im looking for answers for my question , which are featured by programmers who tried to use c# actually and therefor they discovered the advantages and disadvantages of it.
especially compared to c++
thanks in advance
Compared to C++ it features a RAD environment that cuts your GUI envelopment time by half. Compared to VB it has a nicer language in the background. Compared to Java it has a better privilege management ( though that goes for the whole .NET framework).
This was very short, but C# has many features and the best way of learning about them is to read up on them in a non-biased way. Not Microsoft, not slashdot, not JavaHome. Probably a book might be the best way, it comes with the compiler if it's a good one.
C# does not exist outside of something called middleware. A more specific term is 'framework'. The framework is a library of classes that form a class hierarchy. The purpose of a framework is to enable reusable design. A framework is a good idea, it is the natural progression knowledge born out of object oriented programming and it is not limited to acting as environments for development tools, but frameworks can be built to support various enterprise applications. I would not be surprised if many office suite applications are frameworks.
It is true that the .net framework is more productive than Java on the Microsoft operating system, however .net is non existant on a Solaris or Unix or Linux operating system. There are some paid efforts to build a framework for at least Linux, however it may not become accepted by the users.
C++ is used to write all of these frameworks. There is no need for languages like Java and C#, etc. People want money and since they don't own C++ they create a lesser language. These languages do sell, just like the Microsoft operating system sells. It has to do with advertising, and is the way large business deal with small businesses and everyone in between.
It has to do with development speed and the fact that in the business world, time is money. Less time for the same application = less money paid = more money made. Easy calculation. C++ is better than C# in the same way ASM is better than C++.
There is a tool for each job, and for application development without the need for batch-processing speed, C# is better suited than C++, while for speed critical applications C++ is better.
I think it depends on the way u c programming for urself, if u c it as a hobby or a nice time, then u may like to make a real hard programming (just like ppl prefer the harder game to the easier one).
while if u r taking it seriously as a career and job , u shouldnt get away from the demands of the mareket....after all its business
and as nvoigt said "time is money" in buisness.
for me , I like C++ very much , ASM too , and Im going to try Linux OS. as i c its good for try.and I like to learn hardcore programming , encryption and decryption,.........etc
but in the place I live "Egypt" windows is almost the only choice for PC .and none is trying to go beyond . its still under development market. so as I work for money (in-home programming buisness) I have to deal with microsoft as the main source for my actions. VB is great for example to develop many programs especially that high speed isnt a demand for most of ppl
C# may be the same. as u c I ve to follow the market demands , while Im learning the better for myself and for the future
thanks for ur patience :)
No it doesn't. It has to do with Microsoft being envious of Java's success. Microsoft wants a piece of that market. It has to do with control over people who don't know any better and advertising new languages that are nothing more than language elements taken from many different sources, but very little new material. The name for it is the assembly line or mass production. The quality goes way down. This is a massive waist of time because in six or seven years you have not gotten anywhere. This is not the road to money. I know about money.Quote:
It has to do with development speed and the fact that in the business world, time is money. Less time for the same application = less money paid = more money made. Easy calculation. C++ is better than C# in the same way ASM is better than C++.
I like framework development however not Microsofts work in this area. I think that generic libraries are also great areas to invest your time in, however to just work out of a prefabricated framework does nothing for learning how to program, and will not produce efficient software. Don't be fooled, Microsoft is using more C and C++ than ever, but they are not selling that image.
>This is not the road to money.
What ? It's not ? Don't tell my boss, they still pay me :p
Your not studying programming for academic purposes. You had a couple years of training and you went to work. That is the end of your training except for using already made vendor programming environments. It's not the same as research.
Yes. But I get paid for it, so I guess it is the road to money. By the way, research isn't exactly crawling in ASM all day either. Who made the calculator you are working with ? Did you produce it yourself or is it a vendor-made calculating environment ? You need tools, and .NET/C# is a tool. From my perspective it has more advantages than disadvanteges, and that's all that counts.
Oh, and just because formal education stops when you start working doesn't mean you stop learning. You only stop learning when you die. If you start earlier, you are on the road to unemployment. It's just that there is no more set rules when you have to learn and what you have to learn. You have to do it on your own and probably in your spare time.
Well, this is sort of out of topic, but I have .NET for FreeBSD downloaded ( the framework ). Works good here.
.NET is for creating teepees. You can build a bunch of teepees faster than ever before, but building actual homes or sky scrapers is off limits except for Microsoft. Surely they know better and we should never learn about anything that does not have the Microsoft stamp of approval on it. Forget about the original source, forget about knowledge, it's all magic.Quote:
Originally posted by nvoigt
Yes. But I get paid for it, so I guess it is the road to money. By the way, research isn't exactly crawling in ASM all day either. Who made the calculator you are working with ? Did you produce it yourself or is it a vendor-made calculating environment ? You need tools, and .NET/C# is a tool. From my perspective it has more advantages than disadvanteges, and that's all that counts.
Oh, and just because formal education stops when you start working doesn't mean you stop learning. You only stop learning when you die. If you start earlier, you are on the road to unemployment. It's just that there is no more set rules when you have to learn and what you have to learn. You have to do it on your own and probably in your spare time.
>but building actual homes or sky scrapers is off limits
Well depends on how you see it. You will never be able to write an OS in .NET, but why would you want to ? It's not the right tool for the job. .NET is probably not the second coming, but it is a tool well suited for a job at hand. If you need another tool for another job, no one hinders you to get one. Maybe not from Microsoft, but they aren't a welfare organization, they are selling tools. Ferrari wouldn't give you a blueprint of their cars for research either. You buy a car as is, or you don't.
I wouldn't use the RAD thing as an important part in your desicion b/c you can easily make a dialog app in C++ with little code the most code you will type are: #define and for things like buttons
case IDBUTTON1:
{
//whatever you want to happen
}
Oh, and can you now make the button have a 12p italic green Lucida text in VC ? There you go... no RAD in VC.
C# purpose is not to replace C or C++. Not even MS is claiming that. It is a crisp and nice language to interact with the .NET frame work. I worked 3 days with C# and I can already do as good GUI's as I can do in VC. And how many apps are you runing where speed is of utmost importance?. I can see myself using C# for the front and C++ for the backend if I need speed or low level stuff.
OK, here's what I think. C# programming for WIndows is MUCH better than C++ on the GUI scale. Very fast, and the object-oriented aspect of C# is just wonderful. I am an OOP fan by the way. For speed, graphics, or anything that gets "nitty-gritty" so to speak, ya gotta have C++.
Another aspect that you have to realize is ability to distribute. C++ is VERY portable. Most machines can run it without any modification. C#, on the otherhand, isn't very easy to distribute...yet. The target machine has to have .NET installed and most likely has to be Win98, WinXP, Win2000 to run (people are saying that they are getting it run on other OS's too). I've also heard (again, not sure that its true) that you can only develop for C# in WinXPPro (please don't jump on me if i'm wrong!).
ANyways, that's my opinion.
The .NET Framework runs on anything Windows, except for 95, which is triple outdated anyway. You can develop on any of those, though Visual Studio will only run on 2K or XP ( any version I guess ).
>C++ is VERY portable. Most machines can run it without any modification.
This is the theory. As soon as you get into the world of windows, be it MS Windows, X or Mac stuff, C++ isn't portable at all. You either have to use another kind of framework, like qt, or you have to develop for one OS only.
I read somewhere that Microsoft was attempting to preserve Win32 interfaces in the .net base class library. That would mean that you could learn Win32 API function names and .net BCL methods, at the same time. I'm not sure how true it is, but it would be a good idea if it were true. Since Win32 is just an interface I'm not sure if it would be important to learn so long as .net BCL provides all of the functionality that you need. Apparently is does not accomplish this yet, however it will be updated again this year and following. A framework is indepentend of Microsoft, you can be sure of that. It is actually a good thing and it is heavily related to OOP design. I am starting to believe that when you use the Microsoft OS it isn't a bad idea to go with whatever they are selling and supporting.
Standard C++ is a totally different subject than what we are talking about here.