We’ll have to agree to differ on this point.

But I’m afraid that it is childishly immature to refer to the licence you choose not to use as a “virus licence”. If I were still choosing software to use in business I would discard without a further thought anything produced by someone using such childish language.

You're apparently not my target market, as I consider your decision to judge software not on technical merit or restrictions imposed on your business, but political opinion, to be childish.

Dedicating works to the public domain is difficult if not impossible for those wanting to contribute their works for public use before applicable copyright or database protection terms expire. Few if any jurisdictions have a process for doing so easily and reliably. Laws vary from jurisdiction to jurisdiction as to what rights are automatically granted and how and when they expire or may be voluntarily relinquished. More challenging yet, many legal systems effectively prohibit any attempt by these owners to surrender rights automatically conferred by law, particularly moral rights, even when the author wishing to do so is well informed and resolute about doing so and contributing their work to the public domain.

You're apparently not my target market, as I consider your decision to judge software not on technical merit or restrictions imposed on your business, but political opinion, to be childish.

Judging PDOS and sibling works on technical merits against GPL software also results in a preference for GPL software.

It is also quite ironic for you to say this, as you tend to judge licenses based on whether exits with zero or otherwise.

I seem to recall you applying this exact logic to ISC, MIT and similar permissive licenses. While I would not opt for them, they sit right in line with your stated mission goal

where relying on (copyrighted and broken) BIOS or UEFI implementations, or emulation layers is okay

Personally, I'd trust someone

On that note, I cannot trust your license opinions, seeing as you seem to fail to acknowledge

While ever an author refuses to relinquish his rights, he's the undisputed copyright holder and can take me to court.

I started with the processor circuit. You can see it here https://github.com/Alexey1994/simple-processor-circuit. Continued with a simple stackless operator language for the circuit. The ultimate goal is a ram machine in the form of a wristband with a display, keyboard and a bunch of gpio ports. I came to the conclusion that cpm like OS is the best for my homemade.

Well, who's with me?

Your BelOS is not suitable? Why not?

BelOS is exactly what I want.

So for what purpose do you need people with you?

My benefit is that I will not feel alone when I create programs for my OS.

Other people can contribute to writing the OS they need. What's more, people don't have to wade through mountains of junk from commercial OSes to write their programs: they can use the best API I've crystallized.

I need to somehow convince people that I sketched a quality OS. I provided the code, then it's up to people.

Isn't all this hidden behind a C library?

Any C90-compliant program will thus compile.

I can e.g. provide C90-compliant "pdmake" so that you have a make program available.

And I can provide C90-compliant micro-emacs, but you will need to support ANSI X3.64 in addition to C90.

An API cannot be just a C library.

In addition to some standard API, it should be possible to add your own. There is no chance for an ordinary person to add it to c90.

I studied the pdpclib code and I do not understand how, for example, to give the user an API for direct work with PCI or LPT directly from the kernel to the application.

For example, in COM from microsoft, you can register a custom component, and if not for the terrible uuid, this would be a great api.

Or does the user need to write the dll/so library as a kernel module?

My approach is simple: there is a global .h file for all applications of the entire api of the operating system, in which the user can add his own API, implement it in the kernel and recompile the kernel and applications.

I started with the processor circuit. You can see it here https://github.com/Alexey1994/simple-processor-circuit. Continued with a simple stackless operator language for the circuit. The ultimate goal is a ram machine in the form of a wristband with a display, keyboard and a bunch of gpio ports. I came to the conclusion that cpm like OS is the best for my homemade.

Well, who's with me?

My benefit is that I will not feel alone when I create programs for my OS.

Tell me about it! I often end up with no energy for coding because I've put so much into social things, sometimes including posting here.