|
I'm not really interested. There are conversion jobs out there, but I'm plenty busy doing .Net
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
I started with VFP and VB6 back in the day. Wow!! I feel so old.
|
|
|
|
|
Slacker007 wrote: I feel so old.
Tell me about it. I started with FoxPro before it was "Visual".
v2.0 I think... 
The Beer Prayer - Our lager, which art in barrels, hallowed be thy drink. Thy will be drunk, I will be drunk, at home as it is in the tavern. Give us this day our foamy head, and forgive us our spillage as we forgive those who spill against us. And lead us not to incarceration, but deliver us from hangovers. For thine is the beer, the bitter and the lager, for ever and ever. Barmen.
|
|
|
|
|
I wrote a Foxpro for DOS service application - not an app kiddies, for the computer service company I worked for in 1990 ish When Windows 3.0 was hot.
I don't just feel old but am.
|
|
|
|
|
Mike Mullikin wrote: v2.0 I think
Me too!
I started with FoxPro 2.0 and my first computer job was maintaining the Lawn Doctor Business System written in that language in 1994. It was the system that Lawn Doctor franchisees used to run their businesses.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Me too, started with the DOS version of FoxPro and the fun began when the first Windows version came out, my god what a load of crap !
|
|
|
|
|
The largest liquidation in the world so far used Foxpro for its claim and payments systems. I wrote some of them and maintained existing ones. Used properly it was a great little language. Visual Foxpro was even better but short lived due to DOTNET. Rick Strahl once commented , if someone says it can't be done in Foxpro, there's a good chance he doesn't know what he's talking about.
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
There is still a demand for Cobol Developers[^] - and I had hoped that died in the early eighties ...
Well, if I'm honest, I'd hoped it had died before they taught it to us right at the beginning of my CS degree course in 1977.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I must be weird , I enjoyed my COBOL days. 
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
So did I - until I met a different language (FORTRAN, but anything would have done I suspect) and realised how bad it actually was ... 
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Bad as in ?
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
It's wordy, very wordy. IIRC "Hello World" was about 40 punched cards...
It lacks everything a "modern" language needs: user defined functions for a start!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Ah the joyous
IDENTIFICATION DIVISION.
PROGRAM-ID. HELLO-WORLD.
* simple hello world program
PROCEDURE DIVISION.
DISPLAY 'Hello world!'.
STOP RUN.
You could remove the PROGRAM-ID. HELLO-WORLD. line and shrink it to 39 cards
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
From the little I remember...wasn’t it column based too? Like commands had to start in specific columns or the compiler didn’t even see them?
It was so non-REPL too. You had to write an entire program, ship it off to the mainframe, wait and then check the green-lined paper to determine what even went on.
|
|
|
|
|
Ah yes the error report ( regardless of whether there were any errors )
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
A friend of mine recently landed a new gig, so I asked about it.
First question, what technologies do they use?
His answer was rather unexpected... "Mainly COBOL.NET[^]" 
Apparently, you can compile COBOL to MSIL and even run it in Azure, but why anyone would ever want that is beyond me
In their case they sort of "upgraded" (if you can call it that) some old COBOL applications.
Their new services were all Java (no, not Java.NET or COBOL.jar  )
|
|
|
|
|
|
I'm afraid COBOL programmers will roam the earth longer than dinosaurs have, or at least COBOL will 
|
|
|
|
|
When I was working on my CS degree (never completed) in 1991 I had to take COBOL I, II (finished) and III (still haven’t completed). The language was basically dead then (except for knowing it so you could do maintenance and conversion.). Of course that is still going on.
I still need to finish Management 205, COBOL III and Accounting II to obtain my degree.
|
|
|
|
|
Well, maybe if you decide to study software archeology
|
|
|
|
|
|
The boss announced that we will be rewriting our flagship app *from scratch*, but starting with the template I developed. That makes two apps being developed that use my new template.
I'm gonna call this a win. 
I also figured out how to create/use a local offline VS extension gallery (because our dev boxes aren't connecte to the internet).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Congrats on the win win!
Technician
1. A person that fixes stuff you can't.
2. One who does precision guesswork based on unreliable data provided by those of questionable knowledge.
JaxCoder.com
|
|
|
|
|
Johoho and a bottle of rum !
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
