Just imagine if we had a forum dedicated to each one.... :eek::eek::eek::eek::eek:
And 5087 cases (24 bottle to a case) of beer to test each one!!!
Printable View
VB (from DOS to version 6) is the only programming language available in our office. As a result that's the only language I learned and used. If it's my favorite, I don't know exactly.
I tried learning C++ and Turbo Pascal in the past, just enough for me to print "hello world" in any part of the screen I like -- and a little 'beyond'.
The choosing of favorites could have been a little easier if I have used C++ and Pascal so much where I have substantial points of comparison.
So, do you like go on doing analysis of the project considering those 150+ languages every time you start a project. And how much time does that take? :)
Or may be even after analyzing those 150+ languages, some may feel that a new language needs to be developed in this case which will make it a great success. And then one is created. Of course, now you would need to analyze how much cost does it have comparatively. :)
I don't think language choice is that much of a cause of a failure. In fact, my career has been as short as 5 years, but I haven't seen a project fail due to that reason. Mostly they fail due to bad project managers, bad business analysts and requirement gathering, and sometimes poor knowledge of programmers (due to their inexperience or otherwise).
Mostly I have seen language choice as a organization standard, or atleast very quick selection based on other constraints or due to mandates.
Erlang + F#
[QUOTE=exterminator;1782471]So, do you like go on doing analysis of the project considering those 150+ languages every time you start a project.
[quote]
Not all of them..many of them are "obsolete" and I do alot of migration of legacy systems [3 COBOL conversions in 2007]..
But I DO consider alternatives (often 3-5 different approaches). Some of the common ones:
Functional vs. Declarative vs. Imperitive
Custom ASP.NET vs. SharePoint
"Straight ASP.NET" vs. AJAX vs. Silverlight
BizTalk vs. WorkFlow vs. Discrete Programming
Windows Application vs. Service vs. Dedicated Processor (and that is a whole process in itself)
Managed vs. Native
Typically only a few hours, but there are cases where the choice can involve a specific funded allocation.Quote:
And how much time does that take? :)
That is definately true, a DSL (Domain Specific Language) can often be worth the investment. I have done these for Audio Processing, Pharmecutical, Legal and a few other projectsQuote:
Or may be even after analyzing those 150+ languages, some may feel that a new language needs to be developed in this case which will make it a great success. And then one is created. Of course, now you would need to analyze how much cost does it have comparatively. :)
Much depends on what you consider a "failure". If an enterprise project costs $5 million to develop and support (this is fairly low) to provide an increase of $20 million (4x ROI) in bottom line, BUT could have been done for $4M or provided $24M (6x ROI if both) in benefits, I (and most corporate executives I have talks with at many companies) definately consider the project a failure to achieve optimal goals..Quote:
I don't think language choice is that much of a cause of a failure....Mostly I have seen language choice as a organization standard, or atleast very quick selection based on other constraints or due to mandates.
my vote goes to C++
and LUA as a scripting Language
//also hints from TheCPUWizard are instructive.