|
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 !
|
|
|
|
|
|
See Trump is improving things.
Ducks and runs.
|
|
|
|
|
|
#realJSOP wrote: because our dev boxes aren't connecte to the internet How the hell do you get any work done without Google/CP/SO?
|
|
|
|
|
We have a 2nd machine. If we want to add/update a Nuget Package or VS extension, or even just find a code snippet that's fairly long, we have to burn it to a cd from our internet machine, and transfer it to the dev box, and copy it.
On the bright side, we have a KVM that supports dual monitors, so switching back and forth is easy.
".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
|
|
|
|
|
I guess productivity is an afterthought
|
|
|
|
|
USAF - The IT guys go by the slogan "Security above productivity.
".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
|
|
|
|
|
If there's no productivity there's nothing to secure, smart move
Seriously though, sounds like both a very interesting and an infuriatingly annoying workplace.
|
|
|
|
|
There's nothing unusual about JSOP's working environment. The only certain way to avoid hacking from the Internet is not to connect to it, and therefore high-security environments simply don't allow it.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Daniel Pfeffer wrote: There's nothing unusual about JSOP's working environment It's pretty unusual...
I get the security issue, but few environments need to be SO secure they don't allow internet.
In fact, I think most businesses couldn't even function properly without internet.
Calling the USAF "nothing unusual" is a bit of an understatement
|
|
|
|
|
Air-gapped systems are used even in commercial environments, for example on the production line. The last place you want a hacker (or a competitor...) messing with is your production, so you simply keep it off the net.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Yeah, I once had a customer like that.
The entire office didn't have internet, except the manager.
It was impossible to get anything done there
It was a good hour drive and we had to go there for every little bug fix...
And once there you'd had to call back to the office like "can you just Google that for me real quick" (it was before the time of 4G).
If we were talking about Shell or Unilever or whatnot I'd understand, but this was a small starting butchery no one ever heard of...
The manager was also the IT guy and compared everything to cars, so that may explain a thing or two
I think those guys lasted one or two months before closing down (but they did pay their bill).
I guess you really don't need internet on most production sites so no one would miss it there.
Unless, of course, you're sending your data off to the cloud
|
|
|
|
|
#realJSOP wrote: we have to burn it to a cd from our internet machine
Yikes.
And I'll bet you do mean CD, as opposed to DVD, which means they probably pay about 4x as much for the blank media (which is going to end up being trashed anyway).
|
|
|
|