Personally I don''t have anything against XP and .NET. I think its going to be the next best thing since the DOS days. I think they''re doing a good job in merging the two OSes and I think consumers are going to benefit from it. Although I''m not a huge proponent of mandatory registration, I think that it just a matter of what the consumer wants. I bet if M$ gets backlash from alot of consumers about it, they''ll stay on top by reevaluating strategies. Remember, their "monopoly" is based on consumers choices, which are usually carried out through computer maker''s choices. With the competition that goes on between the computer makers, I think that if the consumer doesn''t like the product they''re given, it won''t be too long until an alternative is used.

quote:

---

Original post by Xargon

Sounds like VS.NET is shaping up nicely... for VB programmers. I use C++ and only C++ myself so is there anything in it for me? What I care about is fast execution for my games and I don''t know anyone who programms VB so I can''t see any use of the language compatability. Well anyway, one last question for today: is Visual Studio.NET run over the internet in an asp page or is an actual bit of physical software that I can buy and install? If it still runs from my PC and not over the internet then why on earth did MS call it .NET? I thought .NET is all that internet app stuff. This is confusing me.



-Xargon, Master of the Infinite Void.

---

Relax, It will still be sold on cd''s to be installed on your machine - the reason why it''s called .Net it more because it''s supposed to make it easier to develop applications for the internet

You know, I never wanted to be a programmer...

Alexandre Moura

Realize that C# and C++ are different tools. If you''re out to make the next Quake, stick with C++. It has much better floating point optimizations.

From what I''ve seen, the performance of C# is very close to C++, but not quite there. It''s designed to come close, but they are sacrificing speed so you can go into an app and debug it. You can connect to running services debug/explore them, then disconnect without stoping the service, rebuild on the fly when new Components come out, etc.

If you''re not doing a floating-point game (2d?), C# may work for you, or any other .NET language -- they all get reduced to the same code and use the same objects. Anybody want to do a Cobol.NET RPG?

I've liked what I've seen of the 'managed extentions' to C++ for .NET so far... nested name-spaces, #using directive, access to the same RAD objects of VB, and C code still compiles

.NET kinda sucks VB/C#(~Java)/C++ into one language. VB has the power of C++, C++ has the easy-of-use VB does, and C# is a blend to the latest trend.

All the code gets compiled by the same back-end compiler. Let me say that again: All the code gets compiled by the same back-end compiler. The documentation for .NET says that the only difference between the languages is the syntax.

.NET is geared towards the 'emerging middle-tier' of client/server database programs. You'd do up the client using frontpage or the like (make an .asp) that accesses an MS-SQL/Oracle/Jet/Access/text-file database via a thrid application (the middle tier) programed using VB/C#/C+++ using ADO objects resting on the OLE DB drivers. The middle tier does all the logic of the transaction, the database does what it's suppose to do (store data), and the user only needs to know how to use IE to do anything.

IE->GameSpy->DoomIII->master0.id.com->ID SQL


$$$$$$$$$$$$$$$$$$$$$
XP -> eXtreme Pricing

Magmai Kai Holmlor
- The disgruntled & disillusioned


Edited by - Magmai Kai Holmlor on May 22, 2001 12:07:19 AM

Edited by - Magmai Kai Holmlor on May 22, 2001 12:09:11 AM