Out of all the complaints I've seen about BASIC/Visual Basic, this has never been one of them.
Out of all the complaints I've seen about BASIC/Visual Basic, this has never been one of them.
It has both value types and reference types and both can be passed either by reference or value, giving four ways of passing parameters compared to Python's one way.
It has both early and late binding, compared to Python which again has only one kind.
It has "default properties" on objects, which lets you sometimes use some objects directly in place of some of their properties but sometimes not.
It has different syntax for function calls in expressions and statements, combined with a completely redundant third way (the "call" statement) that confuses matters further.
And in addition to being both statically and dynamically typed (with "Object" declarations) it's also both strictly and loosely typed (with Variant values).
It was written in time with completely different paradigms and the two languages weren't even built with the same design considerations in mind.
Obviously, newer languages are going to tend to be easier to work with for beginners, that should be a given. We've made massive improvements in the field in the last few decades.
The whole point of this comment chain is to discuss whether BASIC was easy to use so it's clearly not a given.
Newer languages have the benefit of hindsight and rapidly improved technology. Better graphics, more power, fewer of the heavy limitations that came with early technology. Between the time that BASIC and Python first came out, we went from System/360 mainframes to Windows 3.0 on our home desktops. Obviously newer languages are going to be able to take advantage of this increased power and wider abilities of computers.
It should be plainly obvious to anyone who takes more than a second to think about it.
Because "easy" is a somewhat relative term. The category will shift over time.
The category shifts over time, sure. But what does that have to do with BASIC being easy or not? They're two separate topics.
"In hindsight, that wasn't actually easy. It was a massive opportunity for highly motivated learners, but the amount of motivation needed was more than what can fairly be called easy."
I'll compare to an early bicycle with no pedals. They were a breakthrough at the time, but in hindsight they hadn't reached "easy".
And just like making a better bike, plenty of the issues with BASIC could have been fixed on the equipment of its heyday.
And it's not just that things improved over time and you need to be new. There are very old bikes that are plenty easy. But it took a while to figure out.
Subroutines don't.
Is that a pointless distinction? Why?
Who ever needs to refactor BASIC!?
On the C64, I find even 6510 / 6502 assembly to be easier to follow than C64 BASIC.
OERN would make it so uncaught errors were silently ignored and execution would just continue on the next line as if nothing wrong happened. This would likely result in more errors, which would then also be ignored.
Something broke but we still moving to the next line.
However, if someone is going to learn, I'll bet they'll pick up python in a similar amount of time, and get a lot better tools when they do it.
BASIC was invented in 1963 and exploded in popularity in the late 70s. Python 1.0 didn't come out until 1991.
The commenter you're replying to argues that BASIC no longer has the advantages it had in 1963, which are unrelated to the language syntax, and that Python offers a closer alternative in that it makes programming accessible.