Where did you saw that I don't know Linux?
At least you are making far-reaching conclusions about the Linux ecosystem for no apparent reason.
You're making wrong assumptions, as usual, since you don't understand what people is writing, and therefore you reply with non-sense.
Unless you're affected by functional illiteracy (which requires actions on your side), you should first understand what was written, and only AFTER that write something (IF needed, and makes sense, of course).
Specifically, you've assumed that I didn't know Linux only because I cannot check something on my machine because it has Windows.
Have you understood your logical fallacy now, or should I draw a chart?
After a simple search: https://github.com/nosway/sfs
So what? You really don't see the difference between: "Linux supports SFS" and "I found on github"?
No. The goal is to read/write SFS on Linux, and whether it comes from from the master or from an external repository is irrelevant.
First, fork is one of the most used APIs in the Unix world.
First, statements must be confirmed. Why do you think so? fork() was written in 1962!
Who cares when it was written.
I actually don't see a fork of 99 out of 100 modern apps.
What you see or not is totally irrelevant, and at least it shows how limited is your vision and experience.
Here's an example which I've found with a quick search:
https://src.chromium.org/viewvc/chrome/trunk/src/base/process_util_posix.cc?pathrev=58558pid_t pid = fork();
331 switch (pid) {Chromium is a MODERN application (read: not from 1962) and it's clearly visible that it's using fork().
Its implementation is hidden
If it's hidden it means that it's still there, elementary logic at hands, and so the problem remains...
or replaced by another.
Same as above: irrelevant. It only proves that you're a noob in the Unix world.
What are you going to transfer that you are so annoyed with the fork?
Maybe because I know how AROS and an Amiga/like o.s. works, and that fork is a black beast for them?
So, you're a noob in the Amiga world as well.
Second, pthreads are an horrible patch over the consolidated process model in the Unix world.
Again, it isn't clear what this is based on. pthreads needed when porting often, e.g. for networked multithreaded applications. The link to one of the realizations that I personally use was given above.
And so? Then try to remove fork() from Chromium and give a modern browser (which is really needed. Current ones are outdated) to AROS, using pthreads instead.
Enjoy...
you need to rewrite the existing code trying to see if there can be another API or workaround.
Yes! When I port something I constantly rewrite implementations or borrow ready-made ones that have already been rewritten. I don't see a fork, but this is one of the 100500+ problems that can occur. The directive will be individually set and changed to vfork() or pthread_create() or another.
These are private things that simply accompany any porting, and not a universal disaster.
And so? Have I ever stated that fork is the only problem when porting apps (to the Amiga land)?
You continue to don't understand what people has written, making wrong assumptions, and falling in logical fallacies...
This requires time, and not even the guarantee to succeed (otherwise a lot more applications would already be ported to AROS or other o.sed.).
Up to 90% of all AROS applications are ported or adapted from *nix.
And so? This mean nothing. Many many others are missing, even very useful ones, and you don't know if porting some of them is easy like the above 90% ones.
The only reason why large projects aren't ported is that there are no people willing to spend time on this and also there are no people willing to learn,
Wrong. Take a look at the recent browser for MorphOS, which was written (porting Chromium, AFAIR) by a SINGLE person, and it's being continuously and frequently updated. Don't tell me that it's an easy task. But it was made by ONE person.
but there are plenty of theoreticians.
Clap clap clap. You made the dig of the day. What's next?
And at least theoreticians have knowledge, which is clearly missing to you, which don't know neither Unix nor the Amiga/AROS worlds.
Do you understand the topic of thread before start writing on it?
Do you understand the difference between an idea and an unscientific fiction?
Unscientific fiction? Like this one that you've written:
"Attach the file hardware_database.csv to your next post. I suggest you keep it up to date.
We will write the application somehow: we will rely on your file."?
Which shows that you don't even have a clue about how problems should be solved. And you're supposed to be a coder, from what you've written 'til now. But with almost zero problem solving mindset, as it was shown by your non-sense proposal that you've written me.
So, yes, your statement can be clearly classified ad sci-fi in the programming world.
But my ideas are not, on the exact contrary, because they are practical solutions to real problems, which only need to be implemented, since they are technical feasible.
And if you don't understand this and continue to talk about "unscientific fiction", it only shows how limited are you on both technical knowledge and coding skills.
So, go learn something because you've deep gaps to be filled, instead of tickle people which, on the contrary, knows very well what he speaks about...
