|
If today, you had a computer like C64, would you love it to start with BASIC or there is an other language you would prefer for the prompt?
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
Cough, coughKornfeld Eliyahu Peter wrote: If today, you had a computer like C64 ZX Spectrum
I would probably jump right in to using assembly or the closest thing to it as the memory restrictions meant that the database I designed, using BASIC, for my ZX Spectrum back in 1984 only held twelve aircraft.
But for the command line, yes BASIC would be fine as a launching point.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
|
Be careful what you wish for!!!
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
Then this[^] might be for you  
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
VB6 rules!
Haters are going to Hate!
|
|
|
|
|
I'd be too busy crying because VS won't run on it to care ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
So you think VS is the perfect tool to start with? Or just getting old and comfy?
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
It's not what I started with - punched cards - but that doesn't mean I want to go back to 'em! 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Of course, not. But I think the generation that started without the luxury of IDEs gained something the youngers have not. The fact that you had only assembly for serious use and BASIC for playing around forced you to learn (and not event internet  )...
So if you had the same experience today (as being beginner) would BASIC do it or maybe another language we have today would work better?
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
No, because Basic teaches you bad habits that become engrained. Go with a strongly typed language if you want to develop seriously, weakly typed if you want to play at it (and don't mind the computer getting it wrong in annoying ways from time to time).
C# is a good starter language for people who want to do this for a living! 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: C# is a good starter language for people who want to do this for a living!
But did we knew that we will do it for a living (if that's what you call it)? We all were playing around... and showing off...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
Sorry to disagree...
The BASIC that came on the C64, TRS-80, Sinclair etc. had only one bad habit, the GOTO instruction!
I can't swear to the others, but you HAD to type variables in TRS-80 BASIC, and there was so little memory available that the size of every variable was important.
You had to do your own memory management too, e.g. re-use variables rather than just declaring new ones etc.
All in all it taught me a more good practice than bad.
I seem to remember that sloppy typing and variants only appeared very much later in VB?
So old that I did my first coding in octal via switches on a DEC PDP 8
|
|
|
|
|
We started the same way! My first programming was switches on PDP-8s then paper tape. Disassembling Scripsit on TRS-80 to add hotkeys for Compugraphic typesetting was a fun project!
|
|
|
|
|
For a person new to programming, I would recommend a simple basic. If they want to mature as a (paid) programmer, then learning languages with more rules (C, C++, C#, Java, etc.) should be next. If they only want to play around, then stay with basic. Also, some of the scripting languages seem to be going backwards and becoming less professional. It seems that Javascript and python have less rules than C and C++ and programmers are being paid to write in those languages. And, even "no code" environments are becoming popular and may be how people create their own applications.
|
|
|
|
|
Basic, basic, basic all the way! Or should that be BASIC?
I learnt on Algol, then moved to Fortran, then I worked for HP in the glory days of Bill, Dave and John Young on the HP98 series of boxes in - would your believe - BASIC!
I can still type error-free basic in almost any dialect as fast as I can write English. 
Squirley brackets? Who needs 'em?
|
|
|
|
|
I started with RGB-II on the IBM mainframes back in 1974. I eventually did COBOL and CICS but was quite happy when I moved to the PC and learned BASIC as my first language. Then I moved onto Turbo Pascal for several years, which I completely enjoyed...
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
HP-BASIC on the 9845 sucked big time, except for an add-on wheel (IIRC) that let you change a variable value run time; very cool for plotting graphs of transfer functions and tweaking them onscreen. I much preferred the 9825 running hpl, which let my program change its own code at run time. It drove the QA types crazy when they tried to validate my code.
Will Rogers never met me.
|
|
|
|
|
BASIC for sure ! These were cool times !
|
|
|
|
|
The main point of those early computers was that Basic was integrated into the shell. This allowed the programmer to start programming without the intermediate steps of opening an editor, saving and then either compiling & running, or interpreting the program.
As far as programming languages are concerned, I would prefer something more structured, for example Pascal. I'm not sure how you'd integrate that with the shell, though.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
BASIC came on built-in ROM chips, there's nothing stopping them do PASCAL or any other language.
|
|
|
|
|
The issue isn't the implementation of the language, but the integration with the shell. Pascal, for example, requires much more in the way of preliminary definitions that BASIC does (e.g. PRINT "Hello, World" is a legal BASIC statement, but Writeln("Hello, World"); requires all kinds of boilerplate).
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Not sure what boilerplate you're referring to, the examples I see online don't have any, but regardless in BASIC you constructed programs using lines so
10 print "Hello"
20 goto 10
That doesn't preclude having boilerplate code.
|
|
|
|
|
I have a C64 and an equally aged BASIC manual... both a few years older than I. 
But to answer the question: BASIC.
|
|
|
|
|
I never really programmed in BASIC - my soul is clean and unfettered by guilt.
That long ago, the only real language I knew was FORTRAN.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
