BorlandTalk.com Borland discussion newsgroups   Archives   FAQ   Search   Memberlist   Usergroups   Register   Profile   Log in to check your private messages   Log in  Woe is me. Goto page 1, 2, 3  Next          BorlandTalk.com Forum Index -> C++ Builder (Non-Technical) View previous topic :: View next topic   Author Message Lew Guest Posted: Mon Nov 03, 2003 7:37 pm    Post subject: Woe is me. Hi, What to do? I have been programming in VB(6) for the past umteen years. Due to there being no further development in VB, as well as the ongoing saga of applications that don't work on clients PC's due to incompatibility issues between MS operation systems, and the gi-normous file size of the distribution applications, I thought it best to move to another programming language. I thought BCB would possibly be the answer, as I have BCB3 which I had purchased in 1998 and stored away without use, due to time restraints. After "playing" with it I quite liked it, and started looking about to purchase the latest release - until alas I read articles on this NG. Now I am most concerned - where does one go? Stay with MS's latest VB.NET/VS.NET and continue with the same old problems in a modern stetting? - or just carry on pursuing BCB in the hope that it will remain compatible with the many MS operating systems existing and yet to come? Wasting money is one thing, but time I cannot afford! Would it be worth my while putting a lot of effort into learning C++ ? Will C++ be a good ongoing grounding for the future? So many questions - which way to go? Is the answer is to stay with MS products after all - and just keep on changing/upskilling throught the years ahead (every year or so?!). Or does one just jump off the software merry-go-round and turn to a more stable vocation? Any ideas based on experience appreciated. Lew. Back to top Shane Stump Guest Posted: Mon Nov 03, 2003 8:16 pm    Post subject: Re: Woe is me. Borland has NOT been clear on their direction (NO ROADMAP). Micro$oft has a very committed / aggressive road map with .NET. Your choice. Regards, Shane P.S. I just started a new project in .NET (my first of hopefully many). I decided early last month I wasn't going to get "Borlanded" again. Back to top Ken Halliwell Guest Posted: Mon Nov 03, 2003 8:21 pm    Post subject: Re: Woe is me. "Lew" <lew (AT) businet (DOT) co.nz> wrote: Quote: What to do? Assumptions: - You are concerned only with building applications for Microsoft's platforms. - You would like a reliable and stable alternative to VB that's similar to VB; and if it worked for both win32 and dotNet development, that would be nice too. - You are willing to use a Borland product. Answer: Delphi kjh Back to top Gillmer J. Derge (TeamB) Guest Posted: Mon Nov 03, 2003 8:23 pm    Post subject: Re: Woe is me. "Lew" <lew (AT) businet (DOT) co.nz> wrote Quote: Now I am most concerned - where does one go? Stay with MS's latest VB.NET/VS.NET and continue with the same old problems in a modern stetting? - or just carry on pursuing BCB in the hope that it will remain compatible with the many MS operating systems existing and yet to come? I think you're misinterpreting the problems. There is little question that C++BuilderX will be compatible with future versions of Windows. What isn't clear is whether it will be compatible with Borland's Visual Component Library (VCL). Since you aren't familiar with VCL and don't have a lot of existing code that relies on it, that's a non-issue for you. This open letter makes it clear that Borland intents to keep up with changes like .NET and to support it in their future C++ products. http://bdn.borland.com/article/0,1410,31277,00.html -- Gillmer J. Derge (TeamB) Back to top Sten Larsson Guest Posted: Mon Nov 03, 2003 8:43 pm    Post subject: Re: Woe is me. "Gillmer J. Derge (TeamB)" <spam (AT) gillmerderge (DOT) com> wrote Quote: I think you're misinterpreting the problems. There is little question that C++BuilderX will be compatible with future versions of Windows. What isn't clear is whether it will be compatible with Borland's Visual Component Library (VCL). Since you aren't familiar with VCL and don't have a lot of existing code that relies on it, that's a non-issue for you. But it is not clear that BuilderX will be a worthwile product... since most people seems to recognize the the strength of BCB is the VCL, and BuilderX does not have it, and may never get anything like it. /sten Back to top Randall Parker Guest Posted: Mon Nov 03, 2003 9:29 pm    Post subject: Re: Woe is me. Lew, If Borland decides to continue supporting VCL in BCBX then go with BCB v6 for now and eventually go to BCBX. If they don't then you could try wxWindows on BCBX or .NET. I agree about the MS issue with different OSs and the file sizes and all that. You need to wait a few weeks to see what Borland announces. I'm cautiously optimistic that VCL will continue to be viable. The cool thing about VCL at this point is that there are really good commercial controls libraries and open source ones too: http://jvcl.sourceforge.net/ and go here and search on Turbopower: http://sourceforge.net/search/ I like C++! Lew wrote: Quote: I have been programming in VB(6) for the past umteen years. Due to there being no further development in VB, as well as the ongoing saga of applications that don't work on clients PC's due to incompatibility issues between MS operation systems, and the gi-normous file size of the distribution applications, I thought it best to move to another programming language. I thought BCB would possibly be the answer, as I have BCB3 which I had purchased in 1998 and stored away without use, due to time restraints. After "playing" with it I quite liked it, and started looking about to purchase the latest release - until alas I read articles on this NG. Back to top Chris Uzdavinis (TeamB) Guest Posted: Mon Nov 03, 2003 10:21 pm    Post subject: Re: Woe is me. "Sten Larsson" <s_t_enX (AT) Xs_ten_l (DOT) com> writes: Quote: But it is not clear that BuilderX will be a worthwile product... since most people seems to recognize the the strength of BCB is the VCL, and BuilderX does not have it, and may never get anything like it. I'm sure it'll have something like it. The real question that people are concerned about is how much compatibility there will be between today's VCL code and tomorrow's CBX code. The answer is not yet clear, unfortunately. -- Chris (TeamB); Back to top Leroy Casterline Guest Posted: Mon Nov 03, 2003 11:20 pm    Post subject: Re: Woe is me. "Lew" <lew (AT) businet (DOT) co.nz> wrote: Quote: Hi, What to do? You might take a look at Delphi. It's not C++, but it's every bit as powerful and of course is based on the VCL. Borland has committed to a Delphi VCL for .NET as well. Back to top Chuck44 Guest Posted: Tue Nov 04, 2003 12:05 am    Post subject: Re: Woe is me. If you're going .Net, then it won't matter much which language you use. They use the same CLR and will perform approximately the same. Since you come from a VB background, I'd suggest C#. That is the language MS has positioned for your needs. A few posters mentioned Delphi. I like Delphi and made quite a nice living from it over the years. But I've noticed the market for Delphi skills is drying-up. There are still a some Delphi legacy systems lying around but I expect they will be all but gone within in a few years as ..Net continues to penetrate. On an aside: I think Borland decision to abandon VCL/CLX and chase Microsoft in .Net-land is pretty much corporate suicide. Not that Borland was healthy anyway. I mean, what MIS (or Software Engineering) department in their right mind is going to choose shaky-company Borland over rock-solid Microsoft? Ok. That is only my opinion. Lew wrote: Quote: Hi, What to do? I have been programming in VB(6) for the past umteen years. Due to there being no further development in VB, as well as the ongoing saga of applications that don't work on clients PC's due to incompatibility issues between MS operation systems, and the gi-normous file size of the distribution applications, I thought it best to move to another programming language. I thought BCB would possibly be the answer, as I have BCB3 which I had purchased in 1998 and stored away without use, due to time restraints. After "playing" with it I quite liked it, and started looking about to purchase the latest release - until alas I read articles on this NG. Now I am most concerned - where does one go? Stay with MS's latest VB.NET/VS.NET and continue with the same old problems in a modern stetting? - or just carry on pursuing BCB in the hope that it will remain compatible with the many MS operating systems existing and yet to come? Wasting money is one thing, but time I cannot afford! Would it be worth my while putting a lot of effort into learning C++ ? Will C++ be a good ongoing grounding for the future? So many questions - which way to go? Is the answer is to stay with MS products after all - and just keep on changing/upskilling throught the years ahead (every year or so?!). Or does one just jump off the software merry-go-round and turn to a more stable vocation? Any ideas based on experience appreciated. Lew. Back to top OBones Guest Posted: Tue Nov 04, 2003 1:58 am    Post subject: Re: Woe is me. Ken Halliwell wrote: Quote: Answer: Delphi Exactly, it would be much easier to learn it coming from a VB background. Back to top Fernando Guest Posted: Tue Nov 04, 2003 9:58 am    Post subject: Re: Woe is me. On Mon, 3 Nov 2003 14:16:00 -0600, "Shane Stump" <ShaneStump (AT) TanstaaflSoftwaer (DOT) com> wrote: Quote: P.S. I just started a new project in .NET (my first of hopefully many). I decided early last month I wasn't going to get "Borlanded" again. That's OK, but beware you might get microshat, as all VB developers have been... I'm getting more and more convinced that I should always have my feet on firm standard (or at least open sourced) ground. The more propietary stuff you use, the sooner you'll get screwed. BTW, using C# means propietary os, propietary frmaework and propietary language. You've been warned. Back to top Mike Margerum Guest Posted: Tue Nov 04, 2003 4:27 pm    Post subject: Re: Woe is me. Quote: That's OK, but beware you might get microshat, as all VB developers have been... I think they did the right thing. Trying to jury rig that mess into the CLI was an impossible task. VB.net is a very nice development environment. Back to top Mike Margerum Guest Posted: Tue Nov 04, 2003 4:28 pm    Post subject: Re: Woe is me. Quote: Answer: Delphi Ok and where am I going to work in the U.S. on delphi? There is almost not delphi work in the philadelphia area. Lew. Learn VB.net and dont look back. Back to top Peter Agricola Guest Posted: Tue Nov 04, 2003 4:40 pm    Post subject: Re: Woe is me. "Mike Margerum" wrote: Quote: That's OK, but beware you might get microshat, as all VB developers have been... I think they did the right thing. Trying to jury rig that mess into the CLI was an impossible task. VB.net is a very nice development environment. How does this help all those abandoned VB developers? Peter Back to top Mike Margerum Guest Posted: Tue Nov 04, 2003 4:43 pm    Post subject: Re: Woe is me. Quote: How does this help all those abandoned VB developers? It doesnt. But I understand why m$ did what they did. Sometimes you have to learn from your (really bad) mistakes and cut your losses. Most of these abandoned developers will move to vb.net and finally learn what a kuldge vb6 was. Whats so hard about migrating to vb.net? Back to top Display posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Months6 Months1 Year Oldest FirstNewest First         BorlandTalk.com Forum Index -> C++ Builder (Non-Technical) All times are GMT Goto page 1, 2, 3  Next Page 1 of 3   Jump to: Select a forum C++ Builder Newsgroups----------------C++ BuilderC++ Builder (ActiveX)C++ Builder (Announcements)C++ Builder (Command Line Tools)C++ Builder DatabasesC++ Builder Databases (ADO)C++ Builder Databases (Desktop)C++ Builder Databases (InterBase Express)C++ Builder Databases (Multi-Tier)C++ Builder Databases (SQL Servers)C++ Builder (Graphics)C++ Builder (IDE)C++ Builder (Internet)C++ Builder (Internet Socket)C++ Builder (Internet Web)C++ Builder (Jobs)C++ Builder (Language)C++ Builder (Language C++)C++ Builder (Compatibility with MFC)C++ Builder (Native API)C++ Builder (Non-Technical)C++ Builder (Students)C++ Builder (Third Party Tools)C++ Builder (Upgrade)C++ Builder (VCL)C++ Builder (VCL Components Usage)C++ Builder (VCL Components Development)C++ Builder (VCL Usage)C++ Builder (WinAPI)C++ Builder Installation Delphi Newsgroups----------------Delphi (General)Delphi ActiveX Controls UsageDelphi ActiveX Controls DevelopmentDelphi As400Delphi DatabasesDelphi Databases (ADO)Delphi Databases (dbExpress)Delphi Databases (Desktop)Delphi Databases (InterBase Express)Delphi Databases (Multi-Tier)Delphi Databases (SQL Servers)Delphi DeploymentDelphi GraphicsDelphi IDEDelphi InternationalizationDelphi InternetDelphi Internet Isapi-WebBrokerDelphi Internet WebSnapDelphi Internet WinsockDelphi JobsDelphi Language BASMDelphi Language ObjectPascalDelphi Model Driven Architecture (General)Delphi Model Driven Architecture (Third Party)Delphi MultimediaDelphi Native APIDelphi Non-TechnicalDelphi ObjectPascalDelphi OLE AutomationDelphi OO designDelphi OpenToolsAPIDelphi Reporting-ChartingDelphi RTLDelphi StudentsDelphi TeamSourceDelphi Thirdparty ToolsDelphi Thirdparty Tools (General)Delphi Thirdparty Tools (IntraWeb)Delphi Thirdparty Tools (RaveReports)Delphi UpgradeDelphi VCLDelphi VCL ComponentsDelphi VCL Components UsingDelphi VCL Components WritingDelphi WebServices SOAPDelphi WinAPIDelphi XMLDelphi Installationcomp.lang.pascal.delphi.components.misccomp.lang.pascal.delphi.components.usagecomp.lang.pascal.delphi.components.writingcomp.lang.pascal.delphi.databasescomp.lang.pascal.delphi.misccomp.sources.delphi JBuilder Newsgroups----------------JBuilderJBuilder AnnouncementsJBuilder Applet IssuesJBuilder As400JBuilder CompilerJBuilder CORBA/RMIJBuilder DatabasesJBuilder DB SwingJBuilder DebuggerJBuilder DeploymentJBuilder DocumentationJBuilder EnterpriseJBuilder HandheldJBuilder IDEJBuilder JavaJBuilder JavaAPIJBuilder Java LanguageJBuilder Java SwingJBuilder Java BeansJBuilder Java Beans UsageJBuilder Java Beans DevelopmentJBuilder JBCLJBuilder JDataStoreJBuilder JobsJBuilder LinuxJBuilder MacintoshJBuilder & MobileSetJBuilder MultiLingual AppsJBuilder Non-TechnicalJBuilder OpenToolsJBuilder Servlets (JSP)JBuilder StudentsJBuilder Team DevelopmentJBuilder Thirdparty ToolsJBuilder UpgradeJBuilder Installation InterBase Newsgroups----------------InterBaseInterBase Bug DiscussionInterBase GeneralInterBase IBConsoleInterBase OpenSourceInterBase ReplicationInterBase SQLInterBase ThirdpartyInterBase Installation Miscellaneous Borland Newsgroups----------------AppCenterAppServerEnteraVisiBroker  You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum Powered by phpBB © 2001, 2006 phpBB Group SEO toolkit © 2004-2006 webmedic.