Ah, but C# was never meant as a better C++, just as C++ was meant to be a better C. It would have been in fact incredibly offensive to have named it (C++)++. Or anything similar.Originally Posted by Decrypt
Regardless, there was never the intention of using this particular naming convention to compare it to C++ in terms of being better or worse. It's just a name. Lets pound on the pretentious use of Objective C or D for instance, if that is really what we want to do.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
I realize now that it's not supposed to be a "better" C++, but that's what I thought when I first saw the name of the language.
There is a difference between tedious and difficult.
I too, thought the '#' in 'C#' was meant to look like 4 pluses put together.
M.Eng Computer Engineering CandidateB.Sc Computer Science
Robotics and graphics enthusiast.
CLI = Command Line Interface
that's my opinion and I'm sticking to it.
*Note: I normally use my linux box in CLI only.
There's way too much agreement in this thread. Here, I'll be contrary.Personally, I think this is a terrible idea. Why do we have Windows Programming, Linux Programming, Game Programming, and Networking/Device Programming boards? Possibly to reduce the noise from real C++ or C questions. Someone recognized that these questions were coming up often and that the questions didn't really add anything to the language discussion. These questions are now filtered away in their own little boards. Note that four subject-specific boards were created from only two language boards.
Having an "Other Programming Languages" board would just be asking for noise. Sure, I might subscribe to such a board and answer some VB, C#, or Lisp questions, but how will I find them among all the other questions about Java, Cobol, or (insert your other favorite language here) questions? How will I find the questions about the languages I'm interested in instead of implementation-specific questions that just happen to be written in one of my languages of choice?
That being said, I have to grudgingly agree that the C# board probably doesn't have much of a place here. C# is a pretty long stretch from C++; the kinds of language issues that are common in C# are probably not the same issues you'd have in C++. Personally, I enjoy the C# board because it's in a good controlled community, but it seems like the only two members that post in there are GanglyLamb and me (and some one-post Charlies every once in a while).
Instead of the "Other Programming Languages" board, if we plan on supporting any other programming languages other than C or C++, we should give each programming language its own board. Apparently it's not a problem if some boards rarely get any posts; consider the frequency of posts on the AI board or the Linux board. Giving each language its own board increases the signal-to-noise ratio on each board. I fail to see any downsides.
If I did your homework for you, then you might pass your class without learning how to write a program like this. Then you might graduate and get your degree without learning how to write a program like this. You might become a professional programmer without knowing how to write a program like this. Someday you might work on a project with me without knowing how to write a program like this. Then I would have to do you serious bodily harm. - Jack Klein
However extra boards will increase the maintance cost for moderators. The average number of cross-posts and off-topic posts is certainly tied to the number of forums and is bound to increase with an increase in number of forums.
But I do agree that putting all together in the same bag (forum) seems excessive.
I say, get rid of them.
C and C++ only... and maybe C++/CLI since this one, whether one may like it or not, is about C++ programming.
What I am missing really is a math forum and a libraries forum.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
A libraries forum sounds great.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
So that MS can confuse everybody. I agree with Perspective; I don't think C# has any business being here. Especially because it only runs on VS.NET.I'm being honest here, I don't know anything about C#, so this is new(s) to me. Why does it have the 'C' if it's not a Cprogramming language?
A side thought: You have a Linux programming board and a Windows programming board. I think you should also implement a Mac programming board. It would make sense, considering that you have boards for those *other* operating systems.
>> A libraries forum sounds great.
I agree, but would they have to be sub-divided into different kinds? It could/would get kinda messy.
One forum only, would be enough, I reckon.
With stickies with install procedures for some of the most commonly used, perhaps, as they are made available by the posters. It would probably also promote people to write tutorials for some of these. Also a sticky for us to post our own personal (aka written by us) libs.
The forum would, of course, be aimed at non standard libraries... boost, pdcurses, blitz++, ncurses, SDL, wxWidgets, etc, etc, etc....
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
I think an "Other Languages" forum is an excellent idea--with the number of users this forum has (even taking inactive users into account) the number of new threads I come across per day are minimal (implying a new area won't spawn a landfill). I have seen a number of java and assembly questions in the tech boards (and whatnot)--enough to warrant their own area, but not individual areas; it just seems like a handy resource.
I pronounce C# C-octothorpe because it's much more impressive sounding.
C# runs on any platform that has a .NET implementation. Linux, Mac, and Windows can all run programs written in C# assuming they are compiled on those platforms.
To code is divine
I both agree and disagree with you. I agree that we should have a Mac board to filter out all of those Mac OS specific questions that we get. I disagree with you because we just don't get that many Mac questions.
If I did your homework for you, then you might pass your class without learning how to write a program like this. Then you might graduate and get your degree without learning how to write a program like this. You might become a professional programmer without knowing how to write a program like this. Someday you might work on a project with me without knowing how to write a program like this. Then I would have to do you serious bodily harm. - Jack Klein
They don't even need to be. They just need to be compiled in a form that Mono can read. Since it can read even MS.Net-produced assemblies, as long as they don't use P/Invoke or a similar mechanism, that means pretty much everything.
The trouble is library support; Mono's framework is still incomplete.
All the buzzt!
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
> we just don't get that many Mac questions.
Thats because development on a mac is just so easy and intuitive
