This blog has personalition features for you, the reader. Below is a key of what all the icons mean and which aspects of the layout they change.
Close Window
Thursday, April 02, 2009 2:30 PM
Specifically, C# 4.0.
You missed of the world most widely used business program language "COBOL" !!
Also missing are SQL, C and Delphi
Wots Wong Wiv LISP
Specifically Visual Basic V6.0
Scala is one of the most interesting languages out there at the minute and missing from the poll... Also why I chose "other".
Ahhh man - can't I do F# AND bbc basic - I still have a mission to do on the disk version of Elite, (aka -> hack the commander file)
Now I'd have to use LOLCODE
There is lots wrong with LISP - such as... I have never been able to read anyone elses LISP code :-) (I used to a Unix EMACS dev and all our dev was supported by LISP extensions to EMACS))Apologies I forgot C and Delphi - I should have put them in.
Add Visual FoxPro and/or Visual Studio 6.0! You should ask the question how many developers would like to use something other then visual studio and .bloat.
Visual Foxpro would be my first choice.The correct tool for the correct task.I don't ever remember database support being native to VB, C, etc.
Visual FoxPro just don't integrate .NET and bloat it up.A question to ask is how many people hate using Visual Studio to the point they would perfer dragging a dull razor across their wrist instead of typing another line of freaking VS plumbing code.
Ouch Mark - can see you are no fan of .NET. But seriously - there is no .bloat. Sure the framework is large - but thats because of the breadth of problems it can solve. You typically use a small subset on any piece of work. Doesn't feel like bloat to me.Paul - I haven't included VB6 as the dev environment is no longer supported.Keep the comments coming though - great stuff.
By Bloat what I'm getting at is; Let's take data for example why should VS have numerous ways to get at data which each paradigm having different limitations. Wouldn't it be far better to have one all encompassing way that just works? This was done in FoxPro so it is possible. How many failed data access technologies has Microsoft introduced since VS was released?The same thought process hold true for MVC/SILVERLIGHT/MVC/WEBFORMS and to some extent AJAX .... So much redundancy and learning curve. Each has it's own set of benefits and limitations. The goal is to pick which one sucks less which is a lousey approach to software development if you ask me.Referring the .NET as a framework is a stretch isn't this really OS API wrappers?Sure the approach I'm talking about is challenging but isn't it better for a single company to correctly implement a solution then forcing each of their customers to write a ton of BS plumbing code and hurdle the learning curve?With VS being so bad I have a new found appreciation for "legacy" technologies such as VFP/VB and the VS 6.0 suite.
Specifically, C#, SQL, F#
What makes you think that I'll be writing any new apps by April 2010?We'll just be maintaining the current app forever.
I used to think like Mark Gordon, but about VB6 instead of FoxPro. I have not used Fox since 2000.I can't believe FoxPro has someone left to defend it. I would like to see performance test(s) that include FoxPro as a contender. I don't think it is a realistic choice anymore with the strides mySQL has made. If your company refuses to spend money on new software, it would be better to use Visual Studio Express with mySQL than to use Fox. At the least, write a quick app to see some comparison. Then again maybe Fox is your job security. :)
Hey John G., I'm willing to bet that there are a lot of VB6 apps out there (just like VFP), but, how many here are defending VB6?
Fields denoted with a "*" are required.
Subscribe in a reader