News for hackers. Stuff that matters.
Re:Learning BASIC Like It's 1983 by AstralStorm on Monday September 03, 2018 @04:02AM (#17901158)
You could actually do that right now in a better way.

Most of the assembly and other DATA/POKE stuff is less than relevant nowadays as hardware has improved and a lot of magic is already done in firmware.

The form of "type it in, verify and run; explain mistakes and correct solution" is still didactically valid.

I'm pretty sure there are programming language interpreters out there with simplicity of BASIC, including BASIC itself.

On MS-DOS, you had a variety of commands built in and extensibility via BASIC too. (or more) Programs could be written as batch files. On Unix-like, the primary interface was via shell, csh, ksh or later POSIX. A set of built in commands. If you wanted something more advanced, programming languages and interpreters were easily available, typically pre-installed.

It was the main interface, magic words. We have regressed to pictures now and most extensibility has been hidden, removed and made very indirect.

Hardware doesn't come with programming manuals anymore as it is deemed too complex (yeah right) and expensive. It is be great if your GPU came with a description and software to write and execute shaders, for example. PC with instructions how to programmatically reboot it, start it or access sensors. How to access EFI services. What the machine code looks like. Etc.

Re:Learning BASIC Like It's 1983 by Annatar on Monday September 03, 2018 @04:36AM (#17901294)
"Hardware doesn't come with programming manuals anymore as it is deemed too complex (yeah right) and expensive."

It doesn't come with manuals because it is considered a trade secret. Commodore had to lay the hardware bare because it wasn't fast enough to program in a high level language nor did the high level languages fully support their hardware, whereas the hardware of today is so fast that nobody thinks anything of it programming it through a driver or a shared object library in a high level language. It's still wrong not to lay the hardware registers and their functionality bare (yes NVIDIA, have you forgotten your SGI roots?)

Re:Learning BASIC Like It's 1983 by AstralStorm on Monday September 03, 2018 @09:10AM (#17902381)
Rarely it is the case that showing relevant performance characteristics and APIs really exposes anything. AMD is perfectly fine with exposing the programming manual and most of setup code - it is not where the real important secrets lie...

It takes time to produce useful documentation though.

Re:Learning BASIC Like It's 1983 by IronBacon on Monday September 03, 2018 @03:30PM (#17904432)
I would also guess that RIAA/MPAA are somewhat responsible with the secrecy to enforce the DRM.

I've read a discussion in a forum where an AMD employee when questioned if it was possible to have a GPU's FW without DRM (or something like that) his answer was that would probably be a commercial suicide (OK, I'm little tired right now and I'm not recalling all the details of the conversation but I can try to dig it up... ^__^;)

Re:Learning BASIC Like It's 1983 by rwallace on Wednesday September 05, 2018 @03:35AM (#17915811)
Hasn't that changed in recent years? I've seen manuals for recent AMD GPU instruction sets.
Re:Learning BASIC Like It's 1983 by pjmlp on Monday September 03, 2018 @01:59PM (#17903978)
I remember that Amiga programming manuals had to be additionally bought from Commodore.
Re:Learning BASIC Like It's 1983 by Annatar on Tuesday September 04, 2018 @01:02AM (#17906771)
But they were available, and most of us used the optical character recognition scanned version on the LSD doc disk.

25 years later I bought the real thing.

Re:Learning BASIC Like It's 1983 by richrichardsson on Tuesday September 04, 2018 @03:50AM (#17907327)
The hardware reference manual was published by Addison-Wesley. Gave me a little nostalgia ping when I noticed the Stroustrup C++ book I bought recently was also published by them.