Slashdot Mirror


Born To RUN: Dartmouth Throwing BASIC a 50th B-Day Party

theodp writes: "Still hanging on to a dog-eared copy of BASIC Computer Games? Back issues of Creative Computing? Well then, Bunky, mark your calendar for April 30th, because Dartmouth College is throwing BASIC a 50th birthday party that you won't want to miss! From the 'invite' to BASIC at 50: 'At 4 a.m. on May 1, 1964, in the basement of College Hall, Professor John Kemeny and a student programmer simultaneously typed RUN on neighboring terminals. When they both got back correct answers to their simple programs, time-sharing and BASIC were born. Kemeny, who later became Dartmouth's 13th president, Professor Tom Kurtz, and a number of undergraduate students worked together to revolutionize computing with the introduction of time-sharing and the BASIC programming language. Their innovations made computing accessible to all Dartmouth students and faculty, and soon after, to people across the nation and the world [video — young Bill Gates cameo @2:18]. This year, Dartmouth is celebrating 50 years of BASIC with a day of events on Wednesday, April 30. Please join us as we recognize the enduring impact of BASIC, showcase innovation in computing at Dartmouth today, and imagine what the next 50 years may hold.' Be sure to check out the vintage photos on Flickr to see what real cloud computing looks like, kids!"

146 comments

  1. We've come a long way by Chrisq · · Score: 4, Funny

    We've come a long way from the original BASIC to VisualBasic.NET, which is basically C# with a BASIC type syntax.

    1. Re:We've come a long way by CastrTroy · · Score: 3, Informative

      Yes very much so. And VB.Net still puts people off because of that long history. Even though it's pretty much exactly the same functionality as C#. Last I checked, it has some features C# didn't have, the biggest of which is better background compiling. You can add entire classes with actually compiling your project, and Intellisense will work. Maybe C# will do that now, but VB.Net has basically always had this feature.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    2. Re:We've come a long way by Chrisq · · Score: 4, Informative

      Yes very much so. And VB.Net still puts people off because of that long history. Even though it's pretty much exactly the same functionality as C#. Last I checked, it has some features C# didn't have, the biggest of which is better background compiling. You can add entire classes with actually compiling your project, and Intellisense will work. Maybe C# will do that now, but VB.Net has basically always had this feature.

      A developer who converted a lot of VB code from VB7 to .NET said that one difference with C# is that typing is more strictly enforced at compile time. After testing on a sample he discovered that porting to VB.NET was quicker, but converting to C# discovered some obscure bugs in the original code - some of which had work-arounds applied as they had ever been fully understood. We went for the port to C# with the result that the ported application was more stable than the original.

    3. Re:We've come a long way by Anonymous Coward · · Score: 0

      Option Strict is your friend.

    4. Re:We've come a long way by Chrisq · · Score: 1

      Option Strict is your friend.

      I'm not a .net developer but from what i was told C# was stricter than "Option Strict" in VB.Net

    5. Re:We've come a long way by luis_a_espinal · · Score: 2

      Option Strict is your friend.

      In addition to Option Explicit. Friends indeed. But to the OP's behalf, Option Explicit is relatively new (2005 I think). There is still a lot of VB code out there that predates that feature.

      But even then I think one should not need to rely on such things.

      I used to be a QuickBasic and VB programmer back in Pre-(Internet)-Cambian times (and, oh, the horrror, PickBasic with numeric goto statements). We guarded ourselves (or I least I did) by using strict coding conventions and Hungarian notation on variable names and function names indicating the return values.

      To a similar degree I did the same when I shifted from VB to FoxBase/FoxPro/VFP (what a nice product it was for its time). Anyways, it was obviously impossible to guarantee a type-mixing mistake would not occur, but software written this way tended to be very reliable and sufficiently type-safe.

      Done this way, type mistakes were easy to spot by just looking at the code. At the end of the day, as Joel Spolsky once wrote, it is about making wrong code look wrong.

    6. Re:We've come a long way by Anonymous Coward · · Score: 2, Insightful

      I think it would be more accurate to say that C# is Visual Basic with a C-like syntax so programmers no longer have to feel ashamed of using Basic.
      Let's face it: no matter whether you're using Java, C#, Python or C++ with a modern toolkit, we're all programming in Visual Basic now.

    7. Re:We've come a long way by K.+S.+Kyosuke · · Score: 1

      Well, they have about as much common with each other as FORTRAN I has with Fortran 2008. ;-)

      --
      Ezekiel 23:20
    8. Re:We've come a long way by Anonymous Coward · · Score: 0

      No, VB.NET puts people off because it's a bad language. It's clumsy and verbose. I don't understand anyone who enjoys working in such a language. For the most part, VB.NET lets you keep all the bad practices you don't wish to unlearn. It's so sad that so many point to this language as the legacy of BASIC.

    9. Re:We've come a long way by Anonymous Coward · · Score: 0

      Yes very much so. And VB.Net still puts people off because of that long history. Even though it's pretty much exactly the same functionality as C#. Last I checked, it has some features C# didn't have, the biggest of which is better background compiling. You can add entire classes with actually compiling your project, and Intellisense will work. Maybe C# will do that now, but VB.Net has basically always had this feature.

      A developer who converted a lot of VB code from VB7 to .NET said that one difference with C# is that typing is more strictly enforced at compile time. After testing on a sample he discovered that porting to VB.NET was quicker, but converting to C# discovered some obscure bugs in the original code - some of which had work-arounds applied as they had ever been fully understood. We went for the port to C# with the result that the ported application was more stable than the original.

      I thought type safety was only something old timers worried about? None of the cool new languages think it is important...

    10. Re:We've come a long way by maz2331 · · Score: 1

      Case sensitivity is the one big turn-off to using C-syntax to me. If I am going to deal with it, then I want my damn pointers back, so I'd just as soon work in C++ and have some actual power to go with the inconvenience. Otherwise, for just business-logic and general DB stuff, VB.NET is quite nice to work in.

    11. Re:We've come a long way by BasilBrush · · Score: 1

      Why do you want case insensitivity in a language?

    12. Re:We've come a long way by Anonymous Coward · · Score: 1

      Why do you want case insensitivity in a language?

      Because people lazy and stupid.

      Case-insensitivity is a terrible idea in a programming language.

    13. Re:We've come a long way by Anonymous Coward · · Score: 0

      Same AC as above: Option Strict was part of VB.Net since at least VS2003 (.Net 1.1)

    14. Re:We've come a long way by CastrTroy · · Score: 1

      What use case is there for having two variables with the same name that only differ by case? In VB.Net, you declare a variable using the desired case, and then when you use the variable, you can just type it completely in lower case (or upper case if you prefer) and it fixes the case to what was in the variable declaration. So the variables always end up with the same original case, and you don't end up with problem where 2 variables have been defined, with the only difference being capitalization of the first letter.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    15. Re:We've come a long way by Anonymous Coward · · Score: 0

      Started programming for a living in the late 80s and to me:
      - Clarion first impression was like Modula2 meets Clipper
      - VB first impression was like QuickBasic PDS meets HyperCard
      - PowerBuilder first impression was like Cougar meets Access
      - Java fist impression was like Strongtalk meets Modula3 libraries
      - dotNet first impression was like Java runtime meets Delphi libraries

      I loved TurboPascal for Windows to learn Win16 nuts and bolds,
      modern rad cant help but obscure the os architecture striving to
      increase productivity... there was better options that didn't survive
      like Dolphin Smalltalk or the now open source BlackBox Oberon2

      Multi-platform native generators like Haxe or Vala seems to me like
      a better compromise between productivity and unconstrained by
      framework or runtime access to the os/hardware

    16. Re:We've come a long way by Anonymous Coward · · Score: 0

      The same could be said of C# in relation to Cobra,
      for dotNet Cobra is the cleaner and less convoluted language,
      but working with ms office objects... vbNet ends being simpler,
      the most redeeming aspect of java and dotnet is the
      ability to mix and match modules in several languages in
      the same project, to use the better tool to solve the problem
      most of the time Cobra/C#/vbNet and some times F#, Mercury, etc

    17. Re:We've come a long way by BasilBrush · · Score: 1

      Well that sounds good, or at least not bad, in that it eliminates potential case typos, and may reduce the need for the shift key for those who don't use it automatically anyway.

      But it's neither case sensitivity, nor case insensitivity, but IDE case fixup.

      For a language itself, I still can't see an argument for it not being case sensitive.

    18. Re:We've come a long way by mlw4428 · · Score: 1

      Verbosity isn't necessarily a bad thing. I was (am?) a VB .NET programmer who turned C#. C# has a lot of little shortcuts because if its roots in C++ -- however these shortcuts can cause debugging to be painful, especially if one isn't familiar with them. Furthermore I'd rather, 1000% of the time, have a variable or function named something like databaseQueryForUser than dbqfusr with another DBQFUSR and another DbQFuSR. And I love C# if nothing else because of the extra love Microsoft and Mono give it. Quit telling people VB is a bad language, it's a language that is designed to be easy to read and understand. That's a good thing as far as debugging goes.

    19. Re:We've come a long way by mlw4428 · · Score: 1

      What argument do you have for a case sensitive language? It just seems like a REALLY easy way to introduce bugs into your code.

    20. Re:We've come a long way by BasilBrush · · Score: 1

      In general for a similar reason that VB.Net IDE corrects case. Because you don't want different parts of a program using STATUS, Status and status for the same variable.

      But there are also use cases for identifiers only varying by case. e.g. Many coding standards say that classes start with a capital, and objects with a lowercase. So:
      TextView is a class.
      textView is an object of the type TextView.

      Then there's indicating word divisions by case:
      "mId" may be a member variable identifier.
      "mid" is a local variable, perhaps indicating the centre of something.

    21. Re:We've come a long way by jellomizer · · Score: 1

      The real issue about VB.NET is the .NET added technical complexity to the language.

      BASIC then Visual Basic was intended to be a language that anyone can code without a strong Computer Science foundation.

      Great for Engineers who need to do some complicated calculations or create some simulations. Or for Business folks who need to get these early computers to do things with it, as we didn't have Spreadsheets ready yet.

      Visual Basic was still easy for these groups too. It did a better job of organizing stuff into a better model. But because it was point and click people still liked it and used it.

      However VB.NET those Computer Scientists got to it and tried to make it a "Respectable" programming language, with classes and abstraction and a lot of stuff while useful if you know what you are doing, has in essence became too complex for generally smart people who do not code all the time, and just wants to get something quick and dirty out.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    22. Re:We've come a long way by mlw4428 · · Score: 1

      That's the thing -- the IDE tends to fix the casing. I'd also be wary of coding standards that allows classes, methods, and fields to be the same name. There is literally no good reason to have something like StupidIdea.stupididea().ToList(stupidIdea);.Case insensitivity promotes STUPID, BAD coding practices and no matter how much you argue otherwise, case insensitivity forces you to use different names for DIFFERENT things.

    23. Re:We've come a long way by slapout · · Score: 1

      You see it used a lot for objects and an instance of the object. For example, in C# you might have a class named Person and create an instance of it like this:

      Person person = new Person();

      --
      Coder's Stone: The programming language quick ref for iPad
    24. Re:We've come a long way by slapout · · Score: 1

      If you want verbose, look at Java or even worse, COBOL.

      --
      Coder's Stone: The programming language quick ref for iPad
    25. Re:We've come a long way by fafalone · · Score: 1

      It's a real shame that the original Visual Basic lineage was dumped in favor of .NET. It's like Windows XP... there's still plenty of people using VB6 to this day. I'm one of them. People never fail to underestimate the power of that language. The last version was released in 1998; yet I'm here on 64-bit Windows 7 and finding not only does the original stuff still work, but I have no trouble using API and Type Libraries to access all sorts of new Win7 things like libraries (music, docs, etc), damn near any other interface, and the latest common controls. Hell there's even a way to include straight assembly code if there was no other way for something. And adapting this ancient language to work with modern features is still light years easier than learning .NET.

    26. Re:We've come a long way by spitzak · · Score: 1

      So you can declare a variable of type MyClass called myClass, or a method that returns a MyClass called myClass().

      In most languages this would be impossible if case was not preserved by lexical scanning (there are a few languages where the intention can be distinguished by syntax, which would allow the class name and method to be exactly the same, and then case sensitivity may be less of a problem).

      Another huge problem with case insensitivity is that the rules get really complex once you get out of ASCII-only, and different interpretations of the rules in effect mean you have literally thousands of actually different syntaxes.

    27. Re:We've come a long way by BasilBrush · · Score: 1

      I'd also be wary of coding standards that allows classes, methods, and fields to be the same name. There is literally no good reason to have something like StupidIdea.stupididea().ToList(stupidIdea);.

      My example, which is a common one, is classes and objects which might have the same name. Which would never result in any line of code like that. You'd only get something like this:

      TextView *textView;

      Which is not at all confusing.

      If you can guarantee that all IDEs for a language will fix the case, then it makes no difference whether the language is case sensitive/insensitive.

      But if you can't, case sensitivity is better. If you get the case wrong with a case sensitive language, then you'll usually get a compiler error. The case insensitive language will ignore the inconsistency. If there are two deliberately different by case identifiers, the case sensitive language will allow it. The case insensitive language won't allow it.

      case insensitivity forces you to use different names for DIFFERENT things

      They both do that. It simply depends what your human mind considers different.

    28. Re:We've come a long way by Anonymous Coward · · Score: 0

      And VB6 has just risen to #6 in the Tiobe list of most popular programming languages (April 2014).

  2. Memories by kria · · Score: 4, Interesting

    I remember as a child reading BASIC programs out of Compute Magazine for my dad to type in on our TI computer. That likely means I was reading code before I read my first real novel, which is amusing.

    I try not to admit at work that I've had to learn VBA for Excel for a tool we use.

    1. Re:Memories by postbigbang · · Score: 5, Funny

      Maybe you should GOTO the event.

      --
      ---- Teach Peace. It's Cheaper Than War.
    2. Re:Memories by invictusvoyd · · Score: 4, Funny

      And have spaghetti for breakfast

    3. Re:Memories by SigmundFloyd · · Score: 4, Funny

      Maybe you should GOTO the event.

      But then he can't RETURN...

      --
      Knowledge is power; knowledge shared is power lost.
    4. Re:Memories by Mr+D+from+63 · · Score: 2

      As a teen I remember writing a small game program in BASIC on a sheet of "programming pad'. Then calling my friend and reading it over the phone while he entered it on his TRS-80. The game was called Catch. A little man got fired out and you had to catch him with the curser before he hit the ground. It worked first time no flaws. I didn't get to see it for over a week. We played that game quite often.

      Then it was on to FORTRAN punch cards.

      NOT the good old days.

    5. Re:Memories by Anonymous Coward · · Score: 0

      He could just have a PEEK, no?

    6. Re:Memories by Virtucon · · Score: 2

      POKE a hole in it, it's done.

      --
      Harrison's Postulate - "For every action there is an equal and opposite criticism"
    7. Re:Memories by k6mfw · · Score: 1

      for me in college I would see a BASIC program (this was in pre-internet days when magazine articles listed programs) I'd type it in and run the program to see what it does. Of course I have to go back and read the article to better understand what I just entered into the computer. Not the best way to learn but had fun with it. Regarding pre-internet, I did have a Compuserve electronic mail account but far from going to article online and do copy/paste.

      --
      mfwright@batnet.com
    8. Re:Memories by operagost · · Score: 0

      Sounds harmful.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    9. Re:Memories by mlw4428 · · Score: 1

      Let's END these bad puns.

    10. Re:Memories by Darinbob · · Score: 1

      I was reading BASIC programs even though I had never seen or used a computer.

    11. Re:Memories by datavirtue · · Score: 1

      There is no shame in VBA. If you use object oriented programming and comments it is maintainable. I have a fairly complex application that I built to automate statistical assessments using VBA in Excel. I initially wrote it as a big blob and it proved to be such a nightmare that the first time I had to modify it for changing requirements I had to rewrite it. After rebuilding it with objects I have had to modify it several times and it has proven clean and easy to do so.

      --
      I object to power without constructive purpose. --Spock
  3. I still program in BASIC. (Sometimes) by MooseDontBounce · · Score: 3, Interesting

    My companies MRP is the (very) old CA-Maxcim written in BASIC. About every other year some change needs to be made to the code. I grab my old BASIC manual and CA-Maxcim API guide and go to work. We use SQL Server, C#, etc. for all new work and have a 3rd party product to access the CA-Maxcim files but it's funny to think of a $80 million+ company core application is written in BASIC. It just works with no problems.

    1. Re:I still program in BASIC. (Sometimes) by Anonymous Coward · · Score: 0

      I still use PureBASIC or PowerBASIC for certain things-- sometimes it's much quicker and easier to whip up a solution in either of those than to futz around with Visual Studio, and even things like PERL. And my little utility is really little- far more compact and efficient than what's typically spit out by VS.

    2. Re:I still program in BASIC. (Sometimes) by Anonymous Coward · · Score: 0

      Amen, PowerBasic is a god send, and followed by Delphi, is
      was? the less bloated commercial supported option on windows.

       

    3. Re:I still program in BASIC. (Sometimes) by MXB2001 · · Score: 0

      Yup and why wouldn't it work still. Nothing really goes obsolete. We just use some older things less because new things have joined them (not replaced... that's a businessman gimmick to try and sell something!).

      --
      01/01/01
  4. BASIC is where M$ got its start by tepples · · Score: 4, Interesting
    If you wonder why people abbreviate Microsoft as M$ in articles, consider that Microsoft got its start as a developer of BASIC for 8-bit home computers, including every Apple II computer from the Apple II Plus through the IIGS, IIc Plus, and Macintosh LC with IIe Card. The FAT file system also started with a Microsoft BASIC; Tim Paterson incorporated it into the 86-DOS that he would later sell to Microsoft. And in this early era, before DEFSTR and DIM ... AS, all string variable names ended with a $, just as names of scalar variables in Perl would later start with $. The following is a BASIC program:

    10 LET M$ = "Microsoft"
    20 PRINT M$;" introduces BASIC"
    30 END

    (That and the $ helps to distinguish Microsoft from multiple sclerosis.)

    1. Re:BASIC is where M$ got its start by colfer · · Score: 1

      Line numbers were great. You could add line 15 at any time!

      But M$ gave us BAT files, which are terrible.

    2. Re:BASIC is where M$ got its start by colfer · · Score: 1

      And if you haven't seen ASCII-art porn images come clacking out of a teletype with a phone-cradle modem to a time-sharing computer, then you weren't there (thankfully perhaps). http://en.wikipedia.org/wiki/T...

      Briefly I had to deal with compiled programs on decks of IBM cards. BASIC was much nicer for a student doing small programs because it was interpreted and you could fix it as you went along (in memory). Those card decks looked cool on Hawaii Five-0, but one syntax mistake in a cobol or fortran program and you had to wait another two hours to get your homework done.

    3. Re:BASIC is where M$ got its start by swb · · Score: 1

      I used to have the astronaut on the moon ASCII poster in my bedroom in high school.

      We used to print them on the DECwriter instead of the TTY33 because they were faster and looked better. The lab nazis would get pissed if they caught you running posters, but it was easier to get away with if it took less time. The TTYs were only viable if you snuck into one of the non-CompSci labs, like in the psychology building, after hours.

    4. Re:BASIC is where M$ got its start by Old+Aylesburian · · Score: 1

      WAIT 6502,1

    5. Re:BASIC is where M$ got its start by argStyopa · · Score: 1

      I'm sure it's coincidental that "M$" likewise suggests Microsoft's financial rapacity, of course.

      --
      -Styopa
    6. Re:BASIC is where M$ got its start by gstoddart · · Score: 2, Informative

      What you say is interesting, but I disagree.

      People use M$ in the same way they use Di$ney ... to connote money grubbing corporations.

      I have never understood that to have anything to do with variables in BASIC.

      Though, for all I know, you could be correct. But I've never used it that way.

      --
      Lost at C:>. Found at C.
    7. Re:BASIC is where M$ got its start by GodfatherofSoul · · Score: 2

      I assumed that it was a reference to their relentless pursuit of cash at all costs (including quality).

      --
      I swear to God...I swear to God! That is NOT how you treat your human!
    8. Re:BASIC is where M$ got its start by markhb · · Score: 1

      The first Microsoft BASIC I ever ran was on the TRS-80 in my high school; I ran something like
      10 FOR A = 0 TO 1024
      20 PRINT CHR$(PEEK(A));
      30 NEXT A

      and somewhere along the way it came out with "M I C R O S O F T"

      --
      Save Maine's economy: write stuff down. All comments are exclusively my own, not my employer.
    9. Re:BASIC is where M$ got its start by mbstone · · Score: 1

      Mod parent -1 Complete And Utter Bullshit.

    10. Re:BASIC is where M$ got its start by Patent+Lover · · Score: 1

      Microsoft BASIC for Atari was awesome. Only superceded by BASTIC XL. But Microsoft was not always evil. I agree that Windows 8 sucks, of course.

  5. Celebrate by just_another_sean · · Score: 1

    I'm going to celebrate by making each of my kids write a simple program in BASIC. They can start on 4/20 and have to be complete by 4/30.

    It's how I got started by gum and if it was good enough for me, and it was, than it's good enough for them!

    http://www.freebasic.net/

    --
    Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
    1. Re:Celebrate by just_another_sean · · Score: 1

      Nice, love the second link/picture. It's nice to know that despite some differences (cloths, equipment) some things never change! :-)

      --
      Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
    2. Re:Celebrate by psergiu · · Score: 1

      Get your kids a Maximite.

      80Mhz, 128Kb RAM, 8 colour, Stereo Amiga-MOD playing, very hackable BASIC computer.

      Just add a VGA monitor, PS/2 keyboard and SD card for storage.

      --
      1% APY, No fees, Online Bank https://captl1.co/2uIErYq Don't let your $$$ sit in a no-interest acct.
  6. Re:Posts like these by dcw3 · · Score: 4, Funny

    Funny. You care enough to post. Maybe, unlike many of us here, you didn't cut your teeth on it, and it's not of interest to you. But, unlike you, I had my first programming class in high school in the early 70s, and have fond memories of acoustic modems, hooked to teletypes, and punching out our programs on the paper tape unit attached to them. Maybe you'd consider those of us from that era to be dinosaurs. I have one thing to say to that...get the fuck off my lawn whippersnapper!

    --
    Just another day in Paradise
  7. Command.com by tepples · · Score: 2

    But M$ gave us BAT files, which are terrible.

    In principle, BAT files are shell scripts. But in practice, I agree that Command.com remained underpowered as a shell. In fact, it was so underpowered that the maker of Scotch tape bought the name to use it for adhesive hanging hooks. Cmd.exe in Windows NT family fixed this somewhat, but as I understand it, Microsoft's command prompt didn't fully meet the power of UNIX shells until PowerShell.

    1. Re:Command.com by DriveDog · · Score: 1

      Having written BATch files since 1985, the first time I tried JScript I decided not to use BATs again except for very simple things. Windows Scripting Host was a good idea that apparently 1) appeared too late, and 2) wasn't supported on all Windows versions for a long time. Too bad.

    2. Re:Command.com by pr0fessor · · Score: 1

      I use the windows command prompt every day and have for a very long time but I do have a nice collection of vbscripts and third party tools that are intended to run from the prompt. I never use powershell and I work in a mostly windows environment I would say that those vbscripts and third party tools make it fairly close to powershell.

    3. Re:Command.com by Anonymous Coward · · Score: 0

      Well... the best shell option for microsoft os widely used
      was TakeCommand by JPSoft until PowerShell arrived

    4. Re:Command.com by Anonymous Coward · · Score: 0

      Since Lantastic days, the better alternative supporting the full range
      of windows versions, was the freeware and still updated wix (and
      wixForms) shell script interpreter

    5. Re:Command.com by Anonymous Coward · · Score: 0

      Other alternatives to the WHS could be: byte compiled scripts,
      programmed in autoIT, wix, RapidQ; or if you are very lucky, to
      have it, Sax Basic (current "polar engineering" price is too
      expensive for shell scripting)

  8. 10 REM HAPPY BIRTHDAY by PvtVoid · · Score: 1

    20 LET X = 0
    30 IF X = 50 THEN 60
    40 LET X = X + 1
    50 GOTO 30
    60 PRINT "HAPPY "
    70 PRINT X
    80 PRINT " BASIC!"

    1. Re:10 REM HAPPY BIRTHDAY by NewWorldDan · · Score: 2

      As memory serves, you would want semicolons after lines 60 and 70 so as not to cause a new line. The dangers of posting untested code to the web.

      Anyway, I thought I'd share the greatest program I ever wrote: a chat-bot. I was 8 and taking a summer school BASIC class in 1984. Near the end of the summer, we had a group of seniors visiting, so I wrote a really simple chat program - just asked some questions and provided canned responses. When those seniors saw the computer talking about the weather they got up and backed away in fear and I had to explain that it said the same thing no matter what you typed, but they still wouldn't go near the computer again. Looking back, that was totally awesome.

    2. Re:10 REM HAPPY BIRTHDAY by Anonymous Coward · · Score: 0

      Reminds me the prank we did to non informatics students
      in late 80s programmed in turbo pascal; a very simple
      dos terminal "Ouija", that used Wile E Coyote "latin" for
      internal fixed lists of "spells", and gives chance (to in the
      knowledge operator) to type some answer while showing
      as keyed one of the canned "spells", latter showing the just
      typed in disguise answer back... or some "spiritual" excuse,
      when in use by operators not aware of the key combination
      for answer capturing

      We where so amused by the fear and irrationality of the magic
      thinking from should know better senior university students
      believing in the possibility of existence to working DOS "Ouija"

      Childish i know, but at 16 really wasnt that much ;-p

  9. My only programming class, ever. by mrhippo3 · · Score: 1

    As a senior at Taylor Allderdice HS (Squirrel Hill) in Pittsburgh, I had my ONLY formal programming class, in BASIC. When I went to engineering school at Carnegie-Mellon, I was not required to take any programming classes, so I chose not to.

    So of course my entire career has been spent using computers. I did use BASIC on my first job (HP 9830, dual cassette drives and a whopping 16KB of RAM), doing real-time data acquisition on large centrifugal compressors. I also wrote a resume as a series of PRINT statements in 1976. This resume was handed back to me in 1983 when I went to work at Penton publishing -- separate story. I have done a lot of CAD, structural analysis, software docs (issued 12,000 page of embedded systems compiler docs one year) and webwork. For another doc project, I hand-coded the help as .jsp. I was the doc person for a dozen or so developers. And to the chagrin of my daughter (a redditor) I sometimes hand code the corporate website.

    Yes, BASIC started me on the road to ruination. 40 plus years later and I am still at it.

  10. Re:Posts like these by morgauxo · · Score: 2

    Maybe you just don't have a very good grasp on who "most people here" are.

  11. One of my earliest multiuser gaming experiences. by Gondola · · Score: 3, Insightful

    Back in the day, I knew people that could provide me with magic phone numbers that would allow me to dial anywhere in the world, for free. Imagine that, right? I was only like 13. Statute of limitations and all that. This was in the 80s I guess.

    Anyway, I remember we used to somehow dial into a Darthmouth mainframe and from there we could do a couple things. They had some kind of multiuser Zork (or Zork-ish) text adventure that you could play. I tried it a couple times but I couldn't get into it at the time, even though I loved Infocom games.

    The biggest appeal was getting into the chat system. There, we could chat with what I assume were Darthmouth college students. "JOIN XYZ" I think was the command from the main menu.

    There was this cool VT display of who was in the chat, so you could tell how many people were there. I used to chat with these people all the time. It was great for a precocious 13 year old who couldn't talk with his peers because his vocabulary and worldview was greatly expanded from theirs. How unfortunate that my social skills were so backward at the same time.

    The details are a bit foggy, but I'm sure with some conversation with some of the same folks who used to chat there, I could dredge up those memories. Anyone remember chatting on that system?

  12. Re:Posts like these by wonkey_monkey · · Score: 1

    Oh OK: Let me change that to -1 (Most people here don't care)

    That's probably true for most of the stories that get posted here, but normal people skip the stories they're not interested in and comment on the ones they are interested in without being whiny bitches.

    Just let it go

    I think you need to take your own advice. Why does it annoy you so much that other people aren't like you (or at least, aren't like you claim to be)?

    --
    systemd is Roko's Basilisk.
  13. Mixed blessing by GrahamCox · · Score: 1

    BASIC is a horrible, horrible language. I'm conflicted though, since it's where I started, in 1978. I stuck with it for a few years not knowing any better, and even programmed the first Mac using MS BASIC for a short time in '85 before giving it up for good. But learning Pascal (Turbo flavour) was a breath of fresh air - almost as easy to use, and far, far more elegant and properly structured. From there it was a trivial leap to C and OOP, C++, Obj-C and the rest. I suspect many programmers of my generation have a similar story, but while BASIC is quick to learn and get started with, it does nothing to teach you how to be a *good* programmer, and encourages many bad habits. Maybe it got better in its later incarnations, I wouldn't know - once you've got to grips with C there's no reason to look at BASIC again. I guess we don't have to wait too long for C's 50th.

    1. Re:Mixed blessing by Alioth · · Score: 2

      There are some good versions of BASIC, even from years ago.

      Consider BBC BASIC for the BBC Microcomputer (a very common computer in the 1980s in British education and schools). BBC BASIC supports named procedures and local variables so you can write BBC BASIC programs just as structured as pretty much any other language. It's one of the few BASICs where you can easily write recursive routines (since it has local variables).

      Then there are BASICs that are just awful, like the excuse for a language interpreter that Commodore put on the C64.

    2. Re:Mixed blessing by slapout · · Score: 2

      That's what the B in BASIC is for -- Beginners. You use it to learn about variables and loops and if statements and other such concepts. Then you move on to other languages (C, Python, etc.) where the concepts are the same but the languages are better structured.

      --
      Coder's Stone: The programming language quick ref for iPad
    3. Re:Mixed blessing by narcc · · Score: 1

      This meme isn't dead yet?

      Give it up, man. If you can't, at least come up with an actual reason for hanging on to it.

    4. Re:Mixed blessing by psergiu · · Score: 1

      Well ...
      BASIC is still used in the micro-controller & embedded device, and is now structured as ever.

      Check out MM Basic

      --
      1% APY, No fees, Online Bank https://captl1.co/2uIErYq Don't let your $$$ sit in a no-interest acct.
    5. Re:Mixed blessing by jellomizer · · Score: 1

      I remember as a kid believing in this odd concept of programming hierarchy.
      You start with Basic, move to Pascal, then to C finally you end up in Assembly.

      However experience has taught me that Programming languages do not fall in a hierarchy, but tools good at solving different problems.

      Basic is good at Throw Away code. Solve your problem give your result. Doing it in any other language you are just wasting your time with details.

      Pascal is good for that simple program that you want to maintain and share and deploy. Better structured however still covers a lot of the memory management nonsense.

      C is good that Professional App that really needs to be good performance, the extra work in managing the memory means you can take shortcuts in the right spot to get extra Speed.

      Assembly when you need to interact with the hardware, make new drivers and bypass parts of the OS.

      It becomes the right tool for the right job, and less of how impressive you look by the fact you can code in some language.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    6. Re:Mixed blessing by Anonymous Coward · · Score: 0

      Sinclair's SuperBASIC was also pretty awesome for the time, especially with the fixes by people like Tony Tebby, and then the compilers... http://en.wikipedia.org/wiki/SuperBASIC

  14. Re:Posts like these by gstoddart · · Score: 5, Insightful

    Maybe you just don't have a very good grasp on who "most people here" are.

    If "most people here" care neither about the 50th anniversary of BASIC nor of time-sharing on computers ... one might argue that "most people here" aren't actually the target audience for Slashdot.

    That's like saying on an aviation forum nobody cares about the Wright Brothers's place in history.

    --
    Lost at C:>. Found at C.
  15. Brings back memories of TASC by swb · · Score: 2

    The AppleSoft Compiler. It seemed like magic, programs ran so much faster than interpreted. I seem to remember a demo BASIC brickout game being basically unplayable compiled because it ran so fast.

    1. Re:Brings back memories of TASC by jockm · · Score: 2

      Microsoft's TASC was also impressive because it was written in AppleSoft Basic and compiled with itself. No small feat, considering the Basic of the time. It was the first compiler I ever bought.

      --

      What do you know I wrote a novel
  16. ewww by DriveDog · · Score: 3, Insightful

    Familiarity, in this case, bred contempt. I've written far more code in all sorts of dialects of BASIC than anything else, and I avoid it now if at all possible. For 1964 or the limited hardware in the 70s (6502s, Z80s, etc.) I suppose it was OK. But this isn't 1964 or 1978. VB isn't Dartmouth BASIC, but it looks and feels like V'GER—all sorts of stuff agglomerated onto a simple-minded core to add capabilities. So I'll celebrate not having to use it. MS made gigabucks in spite of BASIC, not because of it. Too bad K&R didn't get to work a few years sooner so we would never have heard of it. Some older cities still have lead pipes. Doesn't mean it was ever a good idea, and they'd be better off had they never used lead in the first place.

    1. Re:ewww by Anonymous Coward · · Score: 1

      Too bad K&R didn't get to work a few years sooner..

      Too bad K&R got to work at all. C is just a bastardized form of BCPL. The IT world would be a better place if the BCPL language tree had died at the root.

    2. Re:ewww by Anonymous Coward · · Score: 0

      I've written far more code in all sorts of dialects of BASIC than anything else, and I avoid it now if at all possible.

      Well, the good news that I have for you, then, is that you always avoid it.
      10 LET CANAVOIDBASIC$="TRUE"
      20 WHILE CANAVOIDBASIC$ = "TRUE"
      30 GOSUB AVOIDBASIC
      40 WEND
      At this point, I could cite some property of Turing machines being able to do what other Turing machines do, so your most wonderful BASIC program could be written in the wonder language of "Ook! Ook!" ( http://www.dangermouse.net/esoteric/ook.html )
      For example, if you prefer C over BASIC, there's always dds. dds implements BASIC in 1.1KB of code. The documentation notes that "The actual compiler is written in COGNIMP$", so this same 1.1KB of C code is also effectively implementing COGNIMP$
      http://www.ioccc.org/years.html#1991_dds

  17. osaware by Jah+Shaka · · Score: 0

    dont forget to check out www.osaware.com !

  18. Meh by T.E.D. · · Score: 1

    Yeah, I've got a box full of old Creative Computing mags in the attic, and yeah, BASIC was my first programming language. But celebrate its birthday? Meh...

    The language certainly has its place in history, but frankly I moved on a long time ago, and for damn good reason. To me, this would be like celebrating the birthday of the Hustle or Electric Slide. I might occasionally pine for the days of wall-to-wall shag carpeting, but that doesn't mean I'm about to install it in my living room again "for old time's sake". It died for a very good reason. Let it go.

    1. Re:Meh by slapout · · Score: 1

      Think of it more like the anniversary of the slide rule. Sure, you wouldn't use it today for doing calculations, put it has a place in history and was a step toward more powerful things. And some amazing stuff was done with it, like going to the moon.

      --
      Coder's Stone: The programming language quick ref for iPad
  19. Pretty amazing by Anonymous Coward · · Score: 0

    We all know we only have computers because of NASA and astronauts. Who knew John Kemeny was actually an astronaut and used BASIC in space?

  20. Re:Posts like these by Rockoon · · Score: 1

    Oh OK: Let me change that to -1 (Most people here don't care)

    Your karma suggests that there is at least one thing that most of the people here can agree upon.

    --
    "His name was James Damore."
  21. Obligatory link of love by argStyopa · · Score: 1

    http://www.vintage-basic.net/g...

    "BASIC Computer Games
    From Wikipedia, the free encyclopedia
    BASIC Computer Games
    Author David H. Ahl
    Subject Computer programming
    Publication date
    1973
    BASIC Computer Games (1973, 1978, 2010) is a compilation of type-in computer games in the BASIC programming language collected by David H. Ahl. Some of the games were written or modified by Ahl as well. It was the first million-selling computer book.[1]

    The first edition of the book, released in 1973, contained 101 games that had been collected from a newsletter Ahl wrote for DEC's education department. Many of these games had originally been written on different platforms and then ported to DEC machines. These were easy enough to port to other popular platforms of the era, and many of the games re-appeared on other popular systems like the Data General Nova and HP 2100 series.

    Copies of the original collection were still widely available when the first hobbyist microcomputers started appearing in 1975, and it became quite popular with these owners. The release of the "1977 Trinity" machines (Apple II, Commodore PET and TRS-80) was soon followed by a great many new competing microcomputer platforms featuring BASIC, along with the userbase to go with them, and demand for the book led to a second edition in 1978. Sales remained strong for years, and spawned similar collections in More Basic Computer Games (1979), and Big Computer Games (1984) and Basic Computer Adventures (1984).

    The BASIC Computer Games are playable under the relatively obscure Microsoft Small Basic development environment for kids.[2] Computer Science for Kids has released a 2010 Small Basic Edition of the classic Basic Computer Games book called Basic Computers Games: Small Basic Edition.[3]

    The programs can also be run on a modern Microsoft Windows machine (32-bit only) by downloading the GW-BASIC interpreter.[4]"
    (http://en.wikipedia.org/wiki/BASIC_Computer_Games)

    http://www.atariarchives.org/b...

    I remember hammering in just about every game listed in the 1978 book. It really was fun as a 5th grader to puzzle through why these lines of text resulted in a computer doing stuff.

    --
    -Styopa
    1. Re:Obligatory link of love by j-beda · · Score: 1

      I had to pay for a copy of that book from the library, which got misplaced. I swear it was returned, but they never got it. It was more expensive then I thought it should have been.

    2. Re:Obligatory link of love by markana · · Score: 1

      Sigh. I still have my 1st edition copy, slightly worn. It took 4 of us in high school to type in sections of that Star Trek game (110 baud ASR-33, acoustic coupler). But then we played it until they banned the game due to excessive paper use :-) The advent of CRT terminals a few years later was greeted like the 2nd Coming...

      The book itself was banned in a number of school computer centers (well, the few schools that *had* computers at the time). Including the one at SPC, where a certain kid named Gates learned BASIC (via dial-up). I got mine from the local DEC rep, who swore me to secrecy.

  22. Ahh, BASIC by Overzeetop · · Score: 2

    The last, and only, computer language in which I was ever fluent.

    *sigh*

    --
    Is it just my observation, or are there way too many stupid people in the world?
  23. basic? by Anonymous Coward · · Score: 0

    you mean like visual basic.net 2012? Didn't know basic is 50 years old. wow. I'll look for screenshots for the regular basic cuz I wonder what the GUI/IDE looked like back then.

  24. I wrote my whole BBS package in BASIC by King_TJ · · Score: 1

    When I first got interested in running a computer bulletin board system, around 1986-87, I had a Tandy Color Computer 2 (with a whopping 64K of RAM) and a 300 baud auto-dial/auto-answer modem. What I didn't have was any good software to use for the purpose. Back then, the only BBS package I really knew of for the platform was a commercial one called Colorama (typically sold in "Rainbow" magazine, a Tandy Color Computer publication). As a kid who had a LOT more time than money, I was pretty uninterested in trying to buy that one.

    A buddy of mine who was learning to do assembly language coding for the Motorola 6809e processor in the Color Computer started working on a device driver which could translate screen output to modem output, and intercept the results of BASIC INPUT statements, taking them as input received from the modem. That was the missing piece of the puzzle for me, allowing me to code the rest of my own BBS package using BASIC.

    (As a side note... one of the limitations of the Color Computer 2 was the fact it couldn't display any lowercase letters. It knew about the ASCII codes for them, but would only show them on screen as inverse video; essentially looked like the usual uppercase text, except with black blocks behind each letter. Eventually, my friend enhanced his device driver to put the machine into a graphics mode and draw all of the text in a graphical font giving true lowercase and more characters per line than the 32 you got with the original Color Computer text font. It was a little sluggish, but worked and looked great!)

    Due to lack of suitable mass storage devices back then, I wrote the message forum portion of the BBS to store each line of text in DIM variables. Rather limiting, but looking back, it was kind of amazing it worked as well as it did. (I gave people a 15 or 20 line limit per message, I believe.)

    1. Re:I wrote my whole BBS package in BASIC by rk · · Score: 1

      There was a POKE you could use on the CoCo2 (and some versions of the CoCo1) that would switch to a character palette that displayed the lowercase characters as such.

      I recall having a driver that let you use the "hi-res" (256x192! Look out!) mode as the console, so you got more space, but more importantly could mix graphics and text quite easily. If your friend was responsible for that thing and you're still in touch with him, please thank him for me, because that thing rocked.

  25. I see...NERDS by spaceyhackerlady · · Score: 2

    ...and the world is all the better for it!

    ...laura

  26. Not the best, but it was my first by nevermore94 · · Score: 1

    BASIC may not be the best programming language, far from it, but it was my first and it gave me the love of programming that lead to where I am today. I got my first TRS Color Computer 2 when I was 10 for Christmas and I will never forget typing in my first example program (and saving it on a tape) and then starting to experiment and figure out what else I could do with this wonder. From there I upgraded to a CoCo 3 and eventually QuickBASIC on a PC. With that I wrote an AI program that got me to an International Science & Engineering Fair. From there I went on to college to major in CS and learn some real languages. I have been programming in Java for some time now and am now moving into Android development. But, it all started with BASIC on my CoCo and I will always remember it fondly.

    --
    Nevermore.
  27. Re:One of my earliest multiuser gaming experiences by MrHops · · Score: 1

    The biggest appeal was getting into the chat system. There, we could chat with what I assume were Darthmouth college students. "JOIN XYZ" I think was the command from the main menu.

    There was this cool VT display of who was in the chat, so you could tell how many people were there. I used to chat with these people all the time. It was great for a precocious 13 year old who couldn't talk with his peers because his vocabulary and worldview was greatly expanded from theirs. How unfortunate that my social skills were so backward at the same time.

    The details are a bit foggy, but I'm sure with some conversation with some of the same folks who used to chat there, I could dredge up those memories. Anyone remember chatting on that system?

    Oh yes. I was a freshman in '80, and I spent a lot (too much?) time in Kiewit, playing the adventure game, writing programs in BASIC (and later BASIC7, which had a multi-threaded version if you can believe that) chatting on XYZ. Probably talked to you at one point.

    BTW, it's 'Dartmouth'. I'm not fussy, but I'm sure there are alums who are.

  28. Re:Posts like these by Anonymous Coward · · Score: 2, Funny

    lead me to think that slashdot needs a moderation system for articles.

    -1 (Nobody cares)

    10 PRINT "MOD PARENT DOWN"
    20 GOTO 10

  29. Is it just me or... by Trashcan+Romeo · · Score: 1

    ... is that one evil smirk on the TRS-80 monitor?

  30. Err, not the "birth of time-sharing" by time961 · · Score: 1

    In typically breathless university press-release prose, TFA says "on May 1, 1964, ... time-sharing and BASIC were born"

    BASIC, sure, but time-sharing might better be dated to 1961, when CTSS was first demonstrated, and soon after widely used at MIT.

    1. Re:Err, not the "birth of time-sharing" by time961 · · Score: 1

      JOHNNIAC Open Shop System (JOSS) was another early time-sharing system, demonstrated in 1963. By 1964, the time-sharing idea was becoming widespread.

      But, yes, undisputably, Dartmouth gave us BASIC, and like George Washington's proverbial axe (which had both its head and handle replaced multiple times), BASIC remains with us today. At least it's not as harmful as C; BASIC arrays and strings always had bounds-checking.

  31. "My Computer Likes Me" by Anonymous Coward · · Score: 0

    "My Computer Loves Me When I Speak BASIC" - PCC's intro to basic.

    I remember reading it when sitting in a parking lot waiting for my Mom to finish shopping.

    Junior year of high school. HS got a teletype - yes, mechanical - that connected at 110 baud to an HP 2000F time shared basic. Most of my junior year got lost in programming and I can't believe the complexity of programs i wrote with line numbers :

    Two-handed spades card game, a little database that identified minerals, and the inevitable modifications to Star Trek, as well as hours of playing it.

    Creative Computing, 101 Computer games.

    Good times.

  32. BASIC by mdsolar · · Score: 2

    cause FOTRAN is hard --Barbie

  33. Dartmouth CS by CauseBy · · Score: 1, Interesting

    I graduated from Dartmouth in 2002 with a CS degree. Let me tell you, the reason they are throwing this big party for BASIC is because that department hasn't done shit since 1964. If I had to do it again, I would do it at a different school. The only good thing I can say about Dartmouth is that I found refuge in a gentle, fostering fraternity -- and that is the one thing that the Dartmouth administration has been bent on destroying. That campus is a wasteland of feuding heartless conservatives and asinine liberals. Good riddance.

    BASIC was kind of cool, though. I used it in middle school to print endless streams of naughty words. I don't know if it can do anything besides that.

  34. Apparently, so is spelling by Radical+Moderate · · Score: 1

    xxx

    --
    Never let a lack of data get in the way of a good rant.
  35. The original Basic Book by aled · · Score: 1

    I still think that Basic Programming [http://www.amazon.com/BASIC-Programming-John-G-Kemeny/dp/0471468304] by Kemeny & Kurtz (Basic creators) is a very fine way to teach a language. Practically every sample was useful in itself. Very didactic and well written.

    --

    "I think this line is mostly filler"
    1. Re:The original Basic Book by jmichaelg · · Score: 1

      The deal with Basic was it was everywhere. Any computer you had access to had Basic readily available from the command prompt.

      Now , it's Javascript. Available on most computers and runs on most computers.

  36. Atari Explorer by slapout · · Score: 1

    Yes, I have a few Creative Computings around. But I got my start after reading an article in Atari Explorer magazine about BASIC. I cut my teeth on the horrible Basic that was Atari ST Basic. But then I moved to the awesome GFA Basic. From there to C and various other languages. Remember the "B" in Basic stands for Beginner. It's a good language to teach the fundamentals -- variables, looping, etc.

    --
    Coder's Stone: The programming language quick ref for iPad
  37. I'll host my own birthday event, and you can, too by dave.leigh7335 · · Score: 1

    I think a really good idea for BASIC's birthday is to give away some free programs, written in a dialect of BASIC. So I'll be doing that. On April 30 I'll release a new program written in Gambas. Nothing super... it'll just be a nice little program that'll keep you clicking for a little while. You'll be able to tear it apart, look at the source code, see how an event-driven Gambas program works, etc. Of course, it will be released under a Creative Commons license. Anybody else want to dust off a BASIC compiler or interpreter?

  38. Remember, the B in BASIC is for Beginners by xanthos · · Score: 1

    Surprised at the number of hateful comments regarding BASIC. Even when it was created it was aimed at novices not experts, hence the name: Beginners All-purpose Symbolic Instruction Code. The true value was that the simple syntax made learning programming concepts much simpler. I used to teach a beginning programming class in the 80's that used BASIC. I always felt that I was able to instill a better understanding of what was going on with the simple Line # VERB parameter syntax of the early language. Breaking things down only four Verb types ( Definition, Assignment, I/O, Control) , the operators, and the two type of variables/constants (string/numeric). That's all there is folks. Would I want to try and write a compiler in it, no, but that is not what the language was written for.

    Dinosaur trivia points: why do loops commonly use the variable i. (Hint: int does not stand for index.)

    --
    Average Intelligence is a Scary Thing
    1. Re:Remember, the B in BASIC is for Beginners by Anonymous Coward · · Score: 0

      Though some do use N and M, because in the BASIC which came with the ZX Spectrum the FOR and NEXT key words were on the N and M keys.

  39. BASIC bad, ?? good by GPS+Pilot · · Score: 1

    We all know the Dijkstra quote... "It is practically impossible to teach good programming to students that have had a prior exposure to BASIC: as potential programmers they are mentally mutilated beyond hope of regeneration."

    Enough bashing then... what is an *excellent* choice of language to teach to beginners?

    --
    That that is is that that that that is not is not.
    1. Re:BASIC bad, ?? good by Anonymous Coward · · Score: 0

      We all know the Dijkstra quote... "It is practically impossible to teach good programming to students that have had a prior exposure to BASIC: as potential programmers they are mentally mutilated beyond hope of regeneration."

      Enough bashing then... what is an *excellent* choice of language to teach to beginners?

      JavaScript.

    2. Re:BASIC bad, ?? good by psergiu · · Score: 1

      I recommend MMBasic on a Maximite

      Quoting from http://mmbasic.com/ :

      MMBasic is a free and open BASIC interpreter for 32 bit microcontrollers.

      It includes floating point numbers, extensive string handling, multi dimensional arrays and structured programming features like do loops, multiline if statements, user defined subroutines and functions.

      MMBasic is generally backwards compatible with Microsoft's MBASIC and implements much of the ANSI Standard for Full BASIC (X3.113-1987).

      --
      1% APY, No fees, Online Bank https://captl1.co/2uIErYq Don't let your $$$ sit in a no-interest acct.
  40. Bunky? by wonkey_monkey · · Score: 1

    Well then, Bunky

    ...what?

    --
    systemd is Roko's Basilisk.
  41. 10 PRINT "Yipee" by Anonymous Coward · · Score: 0

    10 PRINT "Yipee"
    20 PRINT "Basic Turns 50 on May 1"
    30 PRINT "So much better than C which would look like this: printf("\nYipee\nBasic Turns 50 on May 1\n");"
    40 GOTO 10

  42. Re:I'll host my own birthday event, and you can, t by psergiu · · Score: 1

    Please make a MM Basic version for the Maximite !

    --
    1% APY, No fees, Online Bank https://captl1.co/2uIErYq Don't let your $$$ sit in a no-interest acct.
  43. Answered by a real dinosaur... by dave.leigh7335 · · Score: 1

    It's because of FORTRAN. Implicitly created variables named I through N are part of the "integer" block, and are integers by default. So programmers of all languages tend to use those variables because they learned from coding examples written by even older dinosaurs who learned FORTRAN first. 'Cause FORTRAN is bloody old. (full disclosure... my first programming language was FORTRAN 77)

  44. Happy Birthday Basic by slapout · · Score: 1

    10 ? "HAPPY BIRTHDAY BASIC!"
    20 GOTO 10
    30 REM This comment so the Slashdot filter won't complain about the all caps code yelling

    --
    Coder's Stone: The programming language quick ref for iPad
  45. Re:Posts like these by datavirtue · · Score: 1

    you sir, are an asshole. I had a LOT of fun doing that stuff.

    --
    I object to power without constructive purpose. --Spock
  46. The first one you have handy. by dave.leigh7335 · · Score: 1

    You're no more obligated to be married to your first programming language than you are obligated to be married to the first girl you ever met.

    1. Re:The first one you have handy. by Anonymous Coward · · Score: 0

      How about the first girl that kept you up all night pounding away?

    2. Re:The first one you have handy. by dave.leigh7335 · · Score: 1

      Definitely not her. You think she learned to do that by settling for the first guy SHE met?

  47. Re:One of my earliest multiuser gaming experiences by J053 · · Score: 1

    The Dartmouth BASIC timeshare system also had Star Trek and Lunar Lander (in 1972, anyway). Good times!

  48. Dartmouth should put a DTSS-BASIC system to shell by CronoCloud · · Score: 1

    I'm surprised that they haven't put some kind of DTSS/BASIC system up for people to shell into to see what it was like. I know there's a simulator, but they could put up a system with that XYZ and other things I've seen in this discussion. I had heard about DTSS before, but never got to experience anything like that...unlike some other lucky Slashdotters with high schools privileged enough to have a terminal connected to some university system.

  49. GOTO SmallBASIC by Anonymous Coward · · Score: 0

    http://smallbasic.sourceforge.net/

    Enjoy!

  50. Usborne computer books by Anonymous Coward · · Score: 0

    For anyone interested I have collected all of the 80s Usborne programming books and am (slowly) reviewing each one on a 6502 based machine I built and ported the original MS Basic to: http://www.asciimation.co.nz/bb/category/usborne

  51. It means both by tepples · · Score: 1

    It means both. But the BASIC meaning is a useful fallback for people who complain "you're immature for using $ to connote money grubbing corporations."

  52. Re:One of my earliest multiuser gaming experiences by Anonymous Coward · · Score: 0

    assuming he wasnt talking about the school for Sith lords

  53. My first program... by Lodragandraoidh · · Score: 1

    My very first program was 'hello world' in Basic on the High School computer lab's Apple ][ in 1981 (learned Fortran in that same course). I got a TI 99A for my birthday that year, and I wrote more noddy programs in Basic over the next few years, saving them meticulously on cassette tape.

    I can't imagine using Basic for anything useful these days, but it was fun while it lasted.

    --

    Lodragan Draoidh
    The more you explain it, the more I don't understand it. - Mark Twain
  54. Re:Posts like these by korbulon · · Score: 1

    You're mostly right. But really I'm more like a sausage: 90% asshole (but 10% heart).

  55. Re:One of my earliest multiuser gaming experiences by Gondola · · Score: 1

    It was a typo, of course. I've typed "darth"-something many more times than "dart"-something else in my life.

    '80 was probably too early. I would have been single digits. It was probably more like '84-'85 maybe? I remember some people had personal channels they would use, like some dude named Greg hung out in channel 32 I think?

    I guess it would be kind of weird and wrong to ask what your username was? I can't even remember mine for sure; it might have been Warewolph, or The Hoodlum. Both awful handles that I discarded soon afterwards.

  56. I went to Dartmouth at that time by mannd · · Score: 1

    I was there starting in 1969. Went to the Kiewit computing center there all the time. There was a BASIC program called DATE which was kind of a whacky psychoanalysis program in which you typed questions and it answered them humorously. It was called DATE because you would bring your date there (though women were few and far between at Dartmouth then) to impress them. I took some math classes from Tom Kurtz. Super nice guy. Saw Kemeny around a lot too. Those were good days.

    --
    Sig expected Real Soon Now.
  57. "Option Explicit" was in VB Verion 3 ~1995 by Anonymous Coward · · Score: 0

    EOM.

  58. VB6 is #6 by Anonymous Coward · · Score: 0

    And to celebrate Basics's 50th birthday, Visual Basic 6 has just risen to sixth place in the April 2014 Tiobe index of programming popularity. VB6 is just 16 years old but still widely used in business and government. And,of course, it is the same language as VBA which is still current in Microsoft Office
    http://www.tiobe.com/index.php/content/company/Home.html

    The call to "Bring back Classic Visual Basic, an improved version of VB6" is fifth highest on Microsoft's VisualStudio UserVoice site
    http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3440221-bring-back-classic-visual-basic-an-improved-versi