Minh said:
TommyCarlier said:
*snip*
My point is that the variable = Class.Method(parameter) isn't straight forward language. And since small basic only has 14 keywords, the vast majority of code will be in this format.

I do like the global, dynamic type system for beginners. That's a definite plus. I just see too much of a bind to the old... While ("True") c'mon... seriously...

   With Flickr GetRandomImage("Rainier") => [pic]

or implicit import of a library...

   Import Flickr

Which could do the link & namespace import all in one swoop...

Then you can just do...

   GetRandomImage("Rainier") => [pic]

It's just too early to worry about namespace collision with the

   Flickr.GetRandomImage("Rainier")

syntax.

It's a nice development environment, but right off the bat, seeing 2 loop constructs w/ an obvious bend to OOP conventions, leads me to believe whoever is doing this has a long way to go to understand what language simplification is.

Do you really want to explain to a beginner what a namespace is and how to import a library or namespace? The advantage of Flickr.GetRandomImage is that the user does not have to know about libraries and modules and classes and objects: he just has to know that typing Flickr.GetRandomImage will get a random image from Flickr.

I do agree with your statement that While("True") looks horrible and that they should abandon legacy constructs like that in favor of simpler concepts.