Search Engine

[Software2007]

I need to write a web related search Engine in C++ or C#. I am more comfortable in C++, but I would also like to master C#. My question, is there any clear advantage of doing in one than the other? Thanks

[jschell]

One obvious advantage of course is that you will not learn C# if you do it in C++. Of course there is also a difference between C++ and managed C++. But if you use the former then you are more likely to learn about nitty gritty details of network details.

[Software2007]

Are you saying learning C# is a disadvantage?

[Alan Balkany]

C# is a more modern language, which produces more reliable code. It has a vast class library which reduces the amount of code you have to write. Development is faster in C#, and it will be a requirement for many jobs for the foreseeable future. You should take an opportunity to learn it.

[jschell]

Alan Balkany wrote:

C# is a more modern language

Based on that everyone should immediately move to F#.

Alan Balkany wrote:

which produces more reliable code.

Only way to produced significantly more reliable code is to actually write code that is reliable. Language choice doesn't lead to success at that. People make the difference.

Alan Balkany wrote:

It has a vast class library which reduces the amount of code you have to write

Pretty sure C++ has a vast number of libraries to access. They just don't come with the language.

Alan Balkany wrote:

Development is faster in C#,

Again people make the difference.

Alan Balkany wrote:

and it will be a requirement for many jobs for the foreseeable future.

Which is true for C++. In terms of employability if one knows C++ or C# and then learns SQL is probably going to have more opportunities, overall, than if one just learns another OO language.

[jschell]

Software2007 wrote:

Are you saying learning C# is a disadvantage?

Could be. For example - Using TCP in C++ will require learning more about that versus C#. - One is more likely to learn about how the OS manages memory if one uses C++. - One is more likely to learn about how the OS manages other types of resources if one uses C++. Doesn't mean that one will not learn those with C# but rather that it is more likely that with C++ will need to learn about those in detail.

[Alan Balkany]

"Based on that everyone should immediately move to F#." Its a factor; not an absolute. You don't drive a Model T, do you? "Only way to produced significantly more reliable code is to actually write code that is reliable. Language choice doesn't lead to success at that. People make the difference." Have to disagree here; it's much less likely to have certain types of errors in C#, such as undetected buffer overruns. If the only factor is people, why is development in assembly language so slow? The tools you use make a big difference. "Pretty sure C++ has a vast number of libraries to access. They just don't come with the language." Locating and integrating them increases the amount of work you have to do to get a solution. There's no guarantee of mutual compatibility or any minimum level of reliability with a library from an unknown source. Then there's the versioning problem that's greatly reduced when all the libraries are integrated with the language release. I think use of C# will increase, while use of C++ will decrease in the coming years. C# is a better bet at this point, in my opinion.

[jschell]

Alan Balkany wrote:

Its a factor; not an absolute. You don't drive a Model T, do you?

Got to love those analogies... Exactly how many deliveries on a daily basis do you see via Model T? What percentage from all mechanics will work on them? How many auto parts stores sell parts for them? In comparison the following study, which has been going on for years, and of which has the best methodology that I have ever seen demonstrates that C# certainly isn't one that you want to bet on for being the most popular in the near future. http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html[^]

Alan Balkany wrote:

Have to disagree here; it's much less likely to have certain types of errors in C#, such as undetected buffer overruns. If the only factor is people, why is development in assembly language so slow? The tools you use make a big difference.

Are you claiming that Assembly is comparable to C++? And having programmed in C++ for many years the last time I had a pointer error was before there was an ANSI standard. You are aware that there are now and have been for many years (again before ANSI C++) tools which are very effective at discovering pointer errors?

Alan Balkany wrote:

Locating and integrating them increases the amount of work you have to do to get a solution.

Huh? Are you suggesting that C++ programmers don't know how to use google? Or that there are not libraries that are very effective which do not come with the standard .Net API? As an example do you use a logging library? For that matter have you ever used the Enterprise library or any of number of other libraries from Microsoft which do not come with the .Net API?

Alan Balkany wrote:

There's no guarantee of mutual compatibility or any minimum level of reliability with a library from an unknown source.

Presumably you mean in comparison with .Net API? Are you claiming you haven't found bugs in that? Or at least very odd things? I certainly have. One advantage to other solutions is that there is at least a chance that I some how I can get a solution in the near future. For ex