Microsoft technologies Simplicity && illiteracy VS complication && professionalism [modified]
-
An oversimplification, I admit. No I wouldn't write anything quick in C# - I use assembler for interrupt routines, or vanilla C. Though I have used C++ for embedded applications, with a little assembler at startup and for interrupts, I would not consider C# because of the memory requirements. But equally, I wouldn't want to write .NET applications in assembler (or C again)!
No trees were harmed in the sending of this message; however, a significant number of electrons were slightly inconvenienced. This message is made of fully recyclable Zeros and Ones
OriginalGriff wrote:
No I wouldn't write anything quick in C#
We've benchmarked C# versus C++, and found that well written C# is just as fast in all but a few specialised areas. It's worth knowing a bit about the CLI / JIT and which features to avoid unless absolutely necessary (dictionaries, interfaces & properties to name a few) if you want the best performance.
OriginalGriff wrote:
I would not consider C# because of the memory requirements.
Again, a knowledge of what's going on under the hood, and a bit of care in managing things, will give you assemblies that don't use any more memory than their C++ equivalents.
There are three kinds of people in the world - those who can count and those who can't...
-
OriginalGriff wrote:
No I wouldn't write anything quick in C#
We've benchmarked C# versus C++, and found that well written C# is just as fast in all but a few specialised areas. It's worth knowing a bit about the CLI / JIT and which features to avoid unless absolutely necessary (dictionaries, interfaces & properties to name a few) if you want the best performance.
OriginalGriff wrote:
I would not consider C# because of the memory requirements.
Again, a knowledge of what's going on under the hood, and a bit of care in managing things, will give you assemblies that don't use any more memory than their C++ equivalents.
There are three kinds of people in the world - those who can count and those who can't...
It's not the amount of memory that's the problem with embedded, it's the fragmentation! The last thing you need is a forced garbage collection under interrupt (Shudder).
No trees were harmed in the sending of this message; however, a significant number of electrons were slightly inconvenienced. This message is made of fully recyclable Zeros and Ones
-
It's not the amount of memory that's the problem with embedded, it's the fragmentation! The last thing you need is a forced garbage collection under interrupt (Shudder).
No trees were harmed in the sending of this message; however, a significant number of electrons were slightly inconvenienced. This message is made of fully recyclable Zeros and Ones
OriginalGriff wrote:
It's not the amount of memory that's the problem with embedded, it's the fragmentation! The last thing you need is a forced garbage collection under interrupt (Shudder).
True - that's why I added the "except in special cases" clause :) There are some things that you would never want to do in C#...
There are three kinds of people in the world - those who can count and those who can't...
-
And the perpendicular pronoun is supposed to a majuscule!
------------------------------------ "Children today are tyrants. They contradict their parents, gobble their food and tyrannize their teachers. I despair for the future." Socrates 400BC
And there's supposed to be a "be" in that bee-in-the-bonnet statement.
I wanna be a eunuchs developer! Pass me a bread knife!
-
I used to working on a big project, with lots of code and with a lot of customizable GUI, the name of the platform i was using was "wxwidgets" and it was a platform that is based on C++ ,I was learning lots of things especially in visual programming and i could do whatever i wanted because of strength of c++ and the platform itself and it had got a handy dandy (and simple) help , it was just a chm file that i could find all i wanted simply there but i migrated to C#, (and i used to be familiar with the technology of .NET especially C#) but now i feel that C# say nothing about anything , it stay you away of the real knowledge of visual programming (especially and other base concept in general term) and i feel if you want to learn c# especially by the means of books and videos you will just learn a shell of all is happening under the hood and you still can not find exactly what you want or maybe somethings doesn't exist to be found I want to know if you all programmers agree with me or you are not thank you all especially some of you that tell me about your idea about the issue thank you'all and i am talking about the technology of Microsoft Co. why all are talking about my style of writing or literature ?
modified on Wednesday, May 6, 2009 7:04 AM
cppwxwidgetsss wrote:
I want to know if you all programmers agree with me
With you? No. With the concept that I was barely able to determine within the horrible spelling and grammar? Yes. Of course .net and C# etc. hide a lot of stuff, that's the whole point. I've worked with both C# and C and there wasn't anything I did in C that couldn't have been done in C#. Others (including you) have had different experiences than I. "Use the right tool for the right job!" -- Scotty et al
cppwxwidgetsss wrote:
why all are talking about my style of writing or literature ?
Because you need to communicate clearly first and foremost. What idea you have doesn't matter if you can't communicate it. Einstein could come to me in a dream and tell me how to achieve useful time travel, but if he's speaking German he's wasting his breath.
