Quote:
Originally Posted by ChingChong23
VB6 is single threaded, you'd be an idiot to make a server in that.
VB.net is going to be slow as hell, and assuming if someone creates a server using vb, they are most likely to be low level programmers, therefore using shitty code, poor debugging and very unsecure.
The language (usually) tells it all.
|
What's wrong with a single thread? It's perfectly fine to make a server using just one thread. Acutally, every thread you add puts additional overhead on your application. Of course, you can gain advantage by threading on multi-core hardware, but there's no performance advantage on single processors.
Anyway, VB6 in a general purpose language. You can thread in it, just as you would in C++, pascal or other languages. It can interface directly to system DLLs, and thus, can do everything C can.
VB.net is not slow. You can't notice a difference to that of C# unless you're trying to. VB.net produces a few extra redundant opcodes in CLR, but the time taken to execute these is but a fraction more than without (they're mostly nops).
Language says nothing about the programmer. I mean, look at most of this forum, coding in C#, but very few of them have a real talent for it. The existing C# sources have their share of bugs, and I'm sure someone could easily crash/exploit a server if they have the patience. The sources I've glanced at are far from perfect.
Anyway, I see no point of making a server in VB.net when there's already a bunch of avaliable code in C#. You could convert most of it just be decompiling the C# app from CLR and just fix up the broken parts if you wanted. There's no advantage in doing so though, you're not going to get performance increases or anything. You could just write some modules in VB.net and then interface to them from the existing C# server instead.
)
