Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««23456»»»

Early Software Expand / Collapse
Author
Message
Posted Friday, February 22, 2013 10:54 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 3:00 PM
Points: 1,061, Visits: 2,572
pdanes (2/22/2013)
Bill Wehnert - The Tom Swift books (I had a set, too) weren't written by Asimov. http://en.wikipedia.org/wiki/Tom_Swift

I've been a gadget-geek all my life, since I was a little kid, dismantling mom's vacuum cleaner to see what made all the noise (and then getting in trouble for not putting it back together - once I learned what was inside, I was no longer interested). My first experience with computing hardware was mechanical Marchant calculators, in the university physics labs where my father taught. Then came an electronic calculator with a CRT display a couple of inches square, about the size of a large typewriter and weighing considerably more. It could add, subtract, multiply, divide and remember one number. No square root. The first experience with real programming was a beginning Fortran course, at the university again, after a Vietnam-era tour in the Marine Corps. Univac 9300, 32KB of magnetic core memory, punched 80-column card input - the university's sole computer. Everything in the school ran on it, and students were given one run per day, in the evening, to hand in their deck of cards. Next morning, you could pick up your card deck and however many sheets of paper your job had generated, and go troubleshoot it. That evening, you could try again. If there was too much stuff for the operator to fit it all in, you had to wait until the next day. Sometimes, if the operator was feeling generous and the workload was light, you could persuade him to run a few things during lunch hour.

Even under such primitive conditions, once I discovered what those machines could do, I was hooked and have been at it ever since.


As a young child, I liked to play with my dad's old punch cards from the grad school courses he was taking at the time. Student access to the mainframe worked the same way as pdanes described - turn in your cards for your once-daily run, check back the next day for results. My dad got about as emotional as he ever gets describing the frustration of working for hours on a program, picking up "error" results, then spending hours more poring over the cards to find the one errant punch.


Jason Wolfkill
Blog: SQLSouth
Twitter: @SQLSouth
Post #1423168
Posted Friday, February 22, 2013 11:02 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 9:38 AM
Points: 1,907, Visits: 2,056
Rod Early (2/22/2013)
I got a TI-99/4A computer in 1982 when I was a sophomore in high school...

I also started with the TI-99/4A, I was in 7th grade at the time though. Lots of memories writing BASIC on that. I don't envy you reprogramming the ASCII characters for Greek, I remember I had tried to make real lowwer case letters instead of just small capitals amongst other things, and had the Hex to bits conversions memorized.

The software though that got me interested more in the database side of things was in my first real job when I started using FoxPro for DOS. Yes I had database classes in college that worked with Sybase but those didn't quite grab my imagination the way FoxPro did because we didn't build any front end for the database in college. FoxPro allowed access to the data by SQL or by lowwer level commands. I learned alot about databases from utilizing both, including my preferred way of "pivoting" data using the IIF() function of FoxPro in a SQL query, which I translated to DECODE() function when I learned Oracle, which I translated to CASE in SQL Server.
Post #1423172
Posted Friday, February 22, 2013 11:07 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Today @ 11:42 AM
Points: 755, Visits: 1,927
pdanes (2/22/2013)
Bill Wehnert - The Tom Swift books (I had a set, too) weren't written by Asimov. http://en.wikipedia.org/wiki/Tom_Swift

... My first experience with computing hardware was mechanical Marchant calculators, in the university physics labs where my father taught. ...


Which reminds me, I have one of these, which my dad (a machine designer) purchased new when I was a child in the 60s. It's a wondrous piece of machinery

http://www.vcalc.net/cu.htm


...

-- FORTRAN manual for Xerox Computers --
Post #1423176
Posted Friday, February 22, 2013 11:34 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 11:46 AM
Points: 1,703, Visits: 4,844
Michael Valentine Jones (2/22/2013)
I don’t see how this list could be complete without mentioning COBOL.

From the 1960s until about 1990 it was the language of choice for business programming with implementations on every major OS.

There are tremendous number of applications written in COBOL still running.

It might not be flashy, sexy, object-oriented, etc. but it continues to be a workhorse.


COBOL can use indexed sequential files, but it still only does row by row cursor style batch processing. I guess it's a work horse on a big mainframe. When I attended university back in late 80's and early 90's, the database related courses were centered around COBOL. However, since then I've never been exposed to COBOL professionally except as part of a Y2K conversion where I had to port an AS400 based inventory system to SQL Server, copying tables and re-writing COBOL procedures as T-SQL. So I know how to read COBOL, but fortunately never had to develop with it.
Post #1423188
Posted Friday, February 22, 2013 12:11 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Friday, October 3, 2014 2:23 AM
Points: 3,108, Visits: 11,503
Eric M Russell (2/22/2013)
Michael Valentine Jones (2/22/2013)
I don’t see how this list could be complete without mentioning COBOL.

From the 1960s until about 1990 it was the language of choice for business programming with implementations on every major OS.

There are tremendous number of applications written in COBOL still running.

It might not be flashy, sexy, object-oriented, etc. but it continues to be a workhorse.


COBOL can use indexed sequential files, but it still only does row by row cursor style batch processing. I guess it's a work horse on a big mainframe. When I attended university back in late 80's and early 90's, the database related courses were centered around COBOL. However, since then I've never been exposed to COBOL professionally except as part of a Y2K conversion where I had to port an AS400 based inventory system to SQL Server, copying tables and re-writing COBOL procedures as T-SQL. So I know how to read COBOL, but fortunately never had to develop with it.


COBOL can use SQL calls to various RDMS, depending on the environment, COBOL version, RDMS API, etc.

I am not sure if I know of any procedural language that does anything except row by row processing. Are there any set based languages besides SQL?





Post #1423209
Posted Friday, February 22, 2013 12:32 PM


SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, March 4, 2014 2:10 PM
Points: 35, Visits: 151
My 1st was also a VIC-20 -- which is nothing like the C=64 I eventually upgraded to, Eric! A BASIC manual and then a 6502 Assembler manual was what I lived on, writing animated musical (erm, "beeping") birthday cards for my family in the former and a disk directory prorgam that fit in the 1541 floppy drive's 2K of RAM in the latter. When I could get a hold of a BYTE magazine, I would spend hours typing in the hex code programs to play the half-way decent game it generated.

After turning "pro" with the COBOL programming thing, I was able to afford an Amiga 500 and I moved from programming my computers to integrating software and hardware on them. I still have one of my A500s and the 1200 that followed. The way they managed libraries and devices dynamically should make any Windows programmer jealous. I need to fire up my WinUAE before going back to my databases now...

Man, that was back when this stuff was fun. I think the Arduino is as close as I've gotten to that same feeling in today's computing.

Rich
Post #1423217
Posted Friday, February 22, 2013 12:32 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Monday, October 6, 2014 11:39 AM
Points: 408, Visits: 1,029
First computer I wanted was a SOL. It was a blue box with a keyboard. I seem to recall it had a wood sides. My parents wouldn't let me get it so the next year I snuck out and bought a TRS-80 Model 1 at 15. I remember upgrading it to a floppy then a double sided floppy (76k of storage). Old shugard drive. They offered a computer class in high school but they wouldn't let me take it. I also spent lots of time programming TI calculators until I found out the math teacher was tricking me into learning math at the same time! Loads of fun. I used to try and disassemble the games when I couldn't solve them, everyonce in while I got lucky.
Post #1423218
Posted Friday, February 22, 2013 12:34 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 11:46 AM
Points: 1,703, Visits: 4,844
Michael Valentine Jones (2/22/2013)
Eric M Russell (2/22/2013)
Michael Valentine Jones (2/22/2013)
I don’t see how this list could be complete without mentioning COBOL.

From the 1960s until about 1990 it was the language of choice for business programming with implementations on every major OS.

There are tremendous number of applications written in COBOL still running.

It might not be flashy, sexy, object-oriented, etc. but it continues to be a workhorse.


COBOL can use indexed sequential files, but it still only does row by row cursor style batch processing. I guess it's a work horse on a big mainframe. When I attended university back in late 80's and early 90's, the database related courses were centered around COBOL. However, since then I've never been exposed to COBOL professionally except as part of a Y2K conversion where I had to port an AS400 based inventory system to SQL Server, copying tables and re-writing COBOL procedures as T-SQL. So I know how to read COBOL, but fortunately never had to develop with it.


COBOL can use SQL calls to various RDMS, depending on the environment, COBOL version, RDMS API, etc.

I am not sure if I know of any procedural language that does anything except row by row processing. Are there any set based languages besides SQL?

That's right, RDMS and SQL made ISAM and COBOL obsolete 20 years ago.
Post #1423220
Posted Friday, February 22, 2013 2:31 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 12:23 PM
Points: 2,395, Visits: 1,478
Eric M Russell (2/22/2013)That's right, RDMS and SQL made ISAM and COBOL obsolete 20 years ago.


Problem is that it might take another few decades to replace all the COBOL code. It really was the workhorse of the industry for a long time and we wrote a ton of it.



Not all gray hairs are Dinosaurs!
Post #1423271
Posted Friday, February 22, 2013 2:48 PM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, October 14, 2014 11:19 AM
Points: 340, Visits: 954
It's not obsolete if it still does the job it was designed to do. I've written my share of FORTRAN, RPG, COBOL and who knows what else over the years. No idea if any of it is still running somewhere, but if so, great! There are plenty of tasks that need attention, without inventing silly make-work like replacing fully functional existing code.

Things are only obsolete if they can no longer perform their assigned function. COBOL does not fit that definition by any stretch of the imagination.

There are shops that develop new applications in COBOL today, and do an enormous amount of useful work. Just because it doesn't fit someone's idea of 'the latest and greatest' doesn't mean it's a bad idea to use it.
Post #1423273
« Prev Topic | Next Topic »

Add to briefcase «««23456»»»

Permissions Expand / Collapse