Subj : Re: Question To : Crash From : Tracker1 Date : Sun Feb 20 2005 09:31 am Crash wrote: > As someone that understands the basics of programming I have always been > able to look @ exsisting code and figure problems to make it compile and fix > memory leaks etc. This was many many years ago with no formal training or > anything like that just books and reference cards. > I am wanting to re write a software that we use @ work, it is currently > written in Visual basic . NET and it SUCKS ! Its been my experience that VB > just plain sucks period. Okay, could you elaborate on the "it SUCKS" how does it suck? slow? poorly written code? etc.. Though not fond of the syntax myself, VB.Net is quite capable of performing well, and depending on the author/developer of the program, there could be other issues beyond the platform. > I am looking for suggestions from people who currently are able to write > code on what I should re write it in. > As someone who has debugged and wrote mods for a-lot of C++ code my first > instinct is to use Visual C# .NET however someone told me they both use the > exact same interp. If this is true then I would probably want to run like > hell from that as well. All .Net software will use the runtime installed on the machine, it works similar to, but generally much better than java... I prefer C# over VB.Net myself, also, you don't *NEED* visual C# to use .net, there are a number of other options from #develop to using the command line compilers (with sdk/runtime) directly. > Does anyone out there have any suggestions on what I should re write this > interface in ? It uses TCP/IP on a very regular basis so thats something to > consider. It also deals with images ( low grade basic stuff ) all the time. > Any suggestions on books to read would also be appreciated, once I know what > language I am going to use I will need a really good book that will take me > from ground 0 to pro asap. To be honest, .Net is probably the best option, as the imaging support is probably more complete, and easier to make use of than other libraries, for the tcp/ip if it isn't multithreaded, to run the socket handling out of the main thread, or using asynchronous sockets, that is probably the main reason it sucks.. especially if it is gui based. Another issue is the percieved performance if you aren't locking the output, doing gui changes, then processing those changes, it gets ugly, this is irregardless of the gui you chose to use... Beyond this, if you wanted to rewrite the gui (you didn't say if this was a gui app, or a winforms app), you *could* use the wx.Net wrapper, then your app could be deployable on windows, linux, and osx under ms.net, mono or portable.net ... I would simply suggest that you don't take this single app as representative of more than the developer's abilities. -- Michael J. Ryan - tracker1(at)theroughnecks(dot)net - www.theroughnecks.net icq: 4935386 - AIM/AOL: azTracker1 - Y!: azTracker1 - MSN/Win: (email) --- þ Synchronet þ theroughnecks.net - you know you want it .