Quote:
Originally Posted by Photon
On most OSes, if an installer would overwrite an existing library or similar, it could affect and potentially wreck in principle all other programs installed on that OS. This has also in fact happened.
|
Then make it so that it does not overwrite anything. If it needs specific libraries, it is sufficient to place them into the same directory as the program itself and AmigaOs will pick them up from there. Ideally, there is no installation needed - just copy it wherever you want to have it, and it runs.
Quote:
Originally Posted by Photon
Installation requires some form of permanent storage, and most Amiga models were sold without one.
|
It is 2023 now, and how many people *do not* have some form of permanent storage?
Quote:
Originally Posted by Photon
No installation means among other things, that Amiga programs can run on a mobile phone. It is up to the difficulty of emulation there. It's normally very difficult to set up a permanent storage here; like some emus "barely good enough for gamers only" and not for Amiga computer users.
|
Wait, is the goal here to write some Apps for your smart phone or write a program for the Amiga? The Amiga is not a mobile phone, and if someone is sane or insane enough to install an emulator there, it is not the burden of the program author to enable installation there.
Quote:
Originally Posted by Photon
But you can also cut it short at: "Amiga(D)OS by design chose to put some libraries in ROM and some on floppy disk, without ever providing installers.
|
Dare to look? There is a utlitiliy called "Installer", which (gasp!) is used for installing software.
Quote:
Originally Posted by Photon
If a language is OS-friendly, it can't be punished by using system routines to print text in the default font.
|
Languages are neither os-friendly nor unfriendly. Programs are. I have no problem writing Os-friendly programs in assembly, and unfriendly programs in Basic.
Quote:
Originally Posted by Photon
This is the conclusion that will be reached by a court if somehow rights owners should choose to sue you, and therefore you should without any hesitation put any and all Workbench files with your floppy disk release to make it work.
|
The court would not care on a particular language. Just whether you distribute copyrighted material. Just don't. Deliver your software such that it can be installed on an already setup system, and you do not need to distribute such material. Problem solved.
Quote:
Originally Posted by Photon
Anything else would make the OS itself ransomware (as stated previously). The OS (ROM+disks) has already been sold once. 
|
Anything else but what? Dependencies from the Os does not make the Os "ransomware" - that's silly. There is no need to deliver Os components as part of your own product because your customer already has them available at his end. Just make the program run from an existing installation and you are good.
Quote:
Originally Posted by Photon
It's highly topical, because if rights holders would in their own minds reach a different conclusion than from a court, they have just lost the rights they thought they had. This is for all devs, AND the rights holders.
|
I beg your pardon, but I doubt that there was ever the right that you could take somebody else's work without permission and redistribute it. As a program author, package properly. "Here is my code, put it into a drawer of the workbench, click to run". That is the simplest thing to do. There is no need to distribute Os components along as the Os components are already present.