Without going to RISC OS I can see how other BASIC implementations would be limiting for you. Now some of that can not be done easily with any more traditional programming language, so for those things your choices are of reason.scruss wrote: ↑Mon Nov 26, 2018 4:44 amSomething like Perl or Python: it'll allow me to dig about in deep and messy structures without having to bother me with memory allocation. Maybe store stuff in a SQLite or Spatialite database: take a query and spit it out in the the vector data format of my choice for further transformation in (say) OpenSCAD. The language doesn't have to be super fast or pure: just no limits. F'rinstance, I just realized that the database I looked at for neighbourhood buildings is around 2.6 GB, but Python didn't complain.
Nothing wrong with that view. Different people do best with different systems. For me something like LXDE, KDE, GNOME, Windows, etc are productivity killers, so I can see how the UI can kill productivity when it is far enough outside what you are accustomed to.RISC OS is such a productivity killer for me: single core, no wifi, broken multitasking, only runs on small hardware, the most unusual GUI ever. I know you're very partial to it, but it's a fast nope for me.
Though I would point out that RISC OS is no longer restrained to single core. Yes SMP is a new beast for RISC OS so there is precious little that takes advantage of it yet, though as with any new feature it will see more and more use.
Yes the GUI is different from many others. For some of us it is easier, there are those that do not like it. Each person has what works for them.
That depends on the BASIC. For BBC Basic V handling multiple byte character strings is no different from any other language, so you may have to only one time write a couple of conversion/comparison routines to correctly compare between charactor encodings (something that used to be a common need, and is again thanks to Unicode). And there is no limit to the potential size of the data source.I know that the first bootstrap Unix commands were written in Fortran, 'cos back in the day most computers shipped with a Fortran compiler. HP used to write a lot of their system stuff in Basic dialects. But I'd hate to think of how Basic shell scripts would handle big data with mixed Unicode data.
MS-BASIC realy, how does MS-8K BASIC with a few extensions qualify in this at all, one of the worse examples of BASIC on small systems ever was MS-8K BASIC. Though it is MS-8K BASIC that tainted the view of many about BASIC, as we all saw MS-BASIC sometimes called AppleSoft, sometimes called CBM BASIC, sometimes called TRS BASIC all of it was MS 8K BASIC.If you want AppleDOS 3.3, you know where to find it. ☺Wouldn't it have been nice if, instead of replacing those confusing System V init scripts by a huge C program, that those systemd programmers would have written a collection of easy to understand startup scripts in Basic.