What was the "Next Big Thing" when you started programming?
-
They were something out of Dick Tracy. The very idea that computers were small enough and affordable enough for home and desk was incredibly futuristic. And, of course, I wanted in. My first computer was a Commodore 64. I loved the thing: the 6510 processor had an versatile and easy to learn assembly code, and its sound chips, built-in sprite graphics capability and RS-232 ports made it an amazing hobby computer. I wrote games, a voice synthesizer and even a programmable robotic arm for that thing. And it plugged into a television set and had full CGA graphics: no boring monochrome for me! I don't think there's been a personal computer with as much potential as the Commodore.
The C=64 was my first computer as well. Didn't do a lot of programming with it (some BASIC do-dads and stuff entered from Compute's Gazette), but I loved it for games. It was a huge step up from my Atari 2600, heh. I also got in to playing music on it. My second computer was a C=128. By this time, I had the max four disk drives -- 2 1541 5-1/4" drives and 2 1581 3-1/2" drives -- chained together. Made running GEOS so much easier. I had the C=1702 monitor by then instead of a TV (in fact, I used it as a TV by using a VCR as the tuner). Shortly after getting out of high school, I sold the system and software (kept the monitor -- still have it) and bought an Amiga 500. Sadly, that was the last Commodore computer I owned. I still wish I had it. *sigh* Flynn
-
I've still got mine. I wonder what it would look like on the wide-screen TV? :rolleyes:
Software Zen:
delete this;Probably the same as it did on a 14" portable B&W TV - shocking :D
-
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himangoand Java
The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word. Advertise here – minimum three posts per day are guaranteed.
-
Hahah. I never owned any 5 1/4 floppies, but I did get my hands on one recently. Funny things. I can claim to still owning the whole set of Windows 95 installation 3 1/2 floppies. Comes on 13 floppy disks, heheh.
-
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoWell started programming, or started programming for a living? for the first that was the zx81 (Z80 assembly and Basic) for the second part, C++, MFC, Visual C++ 1.52, and most of all the then upcoming win32 API, and eventually OLE, and COM.
You can't turn lead into gold, unless you've built yourself a nuclear plant.
modified on Friday, February 26, 2010 12:42 PM
-
Punch cards was just a rumor when I started programming...
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001Yeah! But Chuck Norris already had it for a long time, and he was kind of a puncher!! ;P
You can't turn lead into gold, unless you've built yourself a nuclear plant.
-
Yes, there this big promise about "open" systems!!
You can't turn lead into gold, unless you've built yourself a nuclear plant.
-
Getting a RAM pack for my spectrum! Oh, and hacking free willy programs. After that I left it alone for quite a few years, came back to it in the 90s. Java was geting serious hype back then. COM was also coming on scene. And seems to be going off scene pretty quick. What an absoloute waste of time COM is.
Morality is indistinguishable from social proscription
fat_boy wrote:
Oh, and hacking free willy programs.
POKE 35899,0 was giving infinite lives :)
You can't turn lead into gold, unless you've built yourself a nuclear plant.
-
We'll we called them pebbles, but they were really just little grains of sand. But they were pubbles to us! We was reet proud in those days.
Panic, Chaos, Destruction. My work here is done. or "Drink. Get drunk. Fall over." - P O'H
Nagy Vilmos wrote:
they were really just little grains of sand
You had silicon?!? You lucky b*stards...we had to make do with wood.
You should never use standby on an elephant. It always crashes when you lift the ears. - Mark Wallace C/C++ (I dont see a huge difference between them, and the 'benefits' of C++ are questionable, who needs inheritance when you have copy and paste) - fat_boy
-
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoAlgol was cool and sort of nerdy. Bubble memory was going to save the world. minicomputers with switches to boot up were the cats meow.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoWindows, graphical UI. Something that didn't store your code on a tape.
Never underestimate the power of human stupidity RAH
-
and then SVGA, how about the ... 286, with a coprocessor. Ah those were the days...
Never underestimate the power of human stupidity RAH
-
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoWhen I started (in 1971) there was a rumor going arond the office that the next computer would have multiple terminals all running different tasks!
-
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoJudah Himango wrote:
What was "the next big thing"
CP/M.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
Inspired by this SO thread, What was "the next big thing" when you guys started programming? I remember a couple things in college: -Java was big. Write once, run anywhere...people believed it. -There was some interest in, and lots of articles about, Microsoft's new version of COM+, which they named DotNet. Oh, and some interest in the Java copycat they called C#. -I distinctly remember my college textbooks claiming "natural languages" would be the future of programming. -To prepare me for the future, my college taught us Fortran and C. The closest thing I've come to utilizing either of these is the rare piece of C++ code I have to deal with on contracting gigs.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoMain memory above 3.5K ;) Floppy disk instead of datacassette (recording to cassette tapes) 3.5 inch floppies
Rocky <>< Recent Blog Post: CubeTube – Power work are from ambient light!
-
Yes, there this big promise about "open" systems!!
You can't turn lead into gold, unless you've built yourself a nuclear plant.
Pierre Leclercq wrote:
open" systems
yeah, thank god windows came along.
