Hi Tobias, Steve,
Tobias:
I agree that employers
should be looking for people who write understandable code, but these days, recruitment is usually hived off to a third party who run a text search on a database full of CVs to see who pops up. I get requests all the time for a "SQL DBA" when what they mean is "SQL Server DBA" - I don't do SQL Server, I do Oracle and I get hundreds of emails with text like "your CV shops that you are a candidate for a position as a SQL DBA" followed by a list of mandatory skills, none of which I have.

I even have words in my CV that will be picked up by these text searches to get me in the door for an interview - where I usually get the position, even if I don't have the particular skill the third party was searching for. (Something like I'm afraid that I do not have XXXXX as one of my skills" - try it sometime!
I should state for the record, that I think SuperBASIC is one, if not the, best BASIC that there is going. I love it.
Steve:
Python produces no bloatware as it is "interpreted". Interpreted in as much as it is "compiled" into byte code when executed:
Code: Select all
echo 'print("Hello World!")' >> MyCode.py
python MyCode.py
Hello World!
and the compiled version is then run by the Python Interpreter. That version, the bytecode, is
deleted when the program exits. It can also be compiled into byte code of course:
which creates a file named "__pycache__/MyCode.cpython-37.pyc" but you'll still need the Python Interpreter to run it:
Code: Select all
python __pycache__/MyCode.cpython-37.pyc
Hello World!
This is very much how early Visual Basic applications "compiled". With the above tiny example, the source is 45 bytes and the compiled bytecode is 122 which could be classed as bloated however, a bigger example file, something from Oracle's VirtualBox installation, is 43,754 bytes as source and "only" 37,415 bytes as a compiled module. So, not really bloatware I would say. (It's still not properly compiled though, as it's still interpreted bytecode and is not compiled down to machine code.)
Python bloat is thus "in the eye of the beholder" I would say. SuperBASIC is much the same compare the typed in and SAVEd source as opposed to the "compiled" QSAVEd source. Python coding is "real" coding as much as any other language is. BASIC is for beginners - and yet, look at all the QL programs written in SuperBASIC - compiled or otherwise. It's still a real language too. (IMHO)
I do get a little annoyed at the plethora of new languages that are coming out though - there seems to be a new one every week these days. Many, most, seem to vanish just as quickly - thankfully!

. Evolution of the fittest I expect. Maybe that's why Python still exists - it does have advantages?
While we agree that learning [Super]BASIC is a good thing, there are others who think that learning BASIC should prevent you from ever becoming a programmer. Opinions vary obviously. I taught myself BASIC by reading the Personal Computer World magazine long before I had a ZX-81, then when I got one, I had to pretty much unlearn much of it in order to fit in with ZX-Basic as was. Fun! However, I was still able to move on to Z80 Assembly, C and COBOL by the time I got to college and into a number of jobs - all of which I hasten to add, were looking for skilled people in the chosen language. Your mileage may vary of course. When ever I'm involved in recruiting in whatever company I'm working at, we definitely look for existing skills. We can do training on the job - but not for language skills, more for our standard requirements and perhaps other business functions which are specific to the company - I had to do OTJ training for Financial stuff when I worked in a software house writing HP/Credit system and also for Barclays Bank. However, if we need a C++ programmer, we don't employ a BASIC programmer and teach them C++ OTJ. People are too expensive I'm afraid.
For some reason, JavaScript does my head in. I really cannot get to grips with it - but then again, I haven't actually sat down and tried to learn it properly. Maybe one day - if/when I retire?
Cheers,
Norm.