Originally posted by xfcemint
Announcement
Collapse
No announcement yet.
Rust-Written Redox OS 0.8 Released With i686 Support, Audio & Multi-Display Working
Collapse
X
-
-
Originally posted by xfcemint View Post
The first problem is that you can't use Android vs main-tree Linux as an example because Redox OS (a microkernel) can alow drivers to stay under closed-source licenses, unlike the main-tree Linux kernel, where manufacturers are forced to open-source their drivers.
Android is ALSO, NOT a microkernel OS. You bringing up the point that Redox is, contains nothing to support your counter-claim to my statement.
The second problem is that you claim that Android is popular only because of licensing terms, but you are disregaring all the other possible factors.
You are writing complete nonsense.
Leave a comment:
-
Originally posted by xfcemint View Post
We are talking here about the Redox OS (it's in the title). Redox OS uses a microkernel. You keep mentioning Android for some reason that makes absolutely no sense or relevance. What's wrong with your head, I can't figure out.
EDIT: I just can't believe what an idiot this Waethorn is. He just made me check the title of the thread, because I was thinking that I might have been posting in the wrong thread.
Leave a comment:
-
Originally posted by xfcemint View Post
It appears to me that you don't even know how to read. In a microkernel, there is no need for drivers to be "modules", because drivers can simply run in userspace. That fact makes your sentences about as sensible as if a monkey was randomly typing them.
You are the asshole, because you are writing your claims as strong opinions, while at the same time it is obvious to everyone else that you don't have sufficient knowledge to support your strong opinions.
Leave a comment:
-
Let me bring in a different argument, I can't really take a programming language serious as future technology that is not notated with the clearly superior s-expressions. Clojure was a reasonable attempt to bring forward the superior s-expressions and functional programming into the mainstream, sadly it more or less failed.
But it starts even below that, I might overlook somehow no native s-expression support and maybe at some point some s-expression libraries or wrappers like Hy-lang could heal the garbage fortran inspired languages, but not if they are that horrible.
Like just to attract dumb C programmers that need C syntax to accept a language they implemented the incorrect block levels of if blocks.
https://doc.rust-lang.org/rust-by-ex...l/if_else.html
That's as dump as having billions of computer users have to use a layout that was made as compromise for physical typewriters and just so that nobody has to relearn not only have we a stupid qwerty layout, no we also have lines shifted, because otherwise the sticks of the typewriter would have got blocked each other. For that reason only our letters are shiftet vertically per line, so such stupid reasons are used to have worse products.
In lisp you have clear that the else is the same block than the if so:
Code:(if cond (true-statement) (false-statement))
Now in fortran style languages that would have to look something like:
Code:if{ condition cond { true-statement(); } else { false-statement(); } }
At least Rust seems to give back the value of the last statement in a block, that is something that allows code that is not with 1000 temporary variables.
And there are C-style languages that can do that, while in julia in the examples the if statement is not exactly like my example they have a "end" at the whole if block that surrounds from if -> end. You can have easy small ide tools that parse that while a C or Rust if/else is only parsable by a special case because nothing signals that the if blocks ends after the else block all syntax points to them being 2 separate blocks.
But that is just a small example of the problems. In python you are supposed to use some crazy dict lists hack to make up that it's normal control flow sucks so much. (no switch case statement) and if/else is a very code repetitive structure. (especially with multiple ifelse substatements)
But again it's not only the bad implementations of the fortran style structures it's the fortran style notation itself, Lisp is just better for functional programming and in most cases functional programming is superiour and you need less names of variables and get more optimised DRY code, and it pushes you to write better code.
The only reason to not use s-expression is either habit and what you get socialised in horrible schools / universities or if you use something like notepad to program.
Leave a comment:
-
Originally posted by xfcemint View Post
So you, the ignoramus of the thread, claim that the only reason why manufacturers like to support Android is the difference in the license. And, we should take the words of ignoramus as granted.
Otherwise, I stand by my point.
Leave a comment:
-
Originally posted by xfcemint View Post
I don't know what has suddenly gotten into you, as you appeared to be quite a rational person a few posts earlier.
In a microkernel, drivers are just normal applications. They don't need to be under the same licence as the kernel. So, a microkernel can be GPL, and drivers can be closed source. OK?
You might as well complain about fuse drivers, and yet every commonly used fuse driver is open source. People have a strong preference for open source drivers. They're the ones get picked up into mainline. They're the ones people distribute. They're also the ones that see community improvement.
It's the real reason why time and time again open source software has won out over closed source software. It's almost NEVER been because companies were compelled to release their code by the GPL. Instead it's the open source software that received community attention and contribution that became superior.
Even if a company were to try to push a closed source microkernel driver, the fact that it's resting on an open userspace with a defined interface means that every interaction it makes with the hardware can be traced. This makes reverse engineering vastly easier as you have direct introspection into everything the driver does.
Edit: It's also not like the GPL does you any favors in preventing closed-source drivers. How many years did nvidia ship a closed source driver before begrudgingly opening up? And in the end the driving force was AMD and their open drivers providing a competitive alternative.Last edited by Developer12; 25 November 2022, 04:08 PM.
Leave a comment:
-
Originally posted by xfcemint View Post
I have given you the "good argument", but you are so ignorant that you failed to realize that licencing issues in a microkernel are different from those that you know of in a monolithic kernel.
I'm not going to read the rest of your post because your ignorance makes you unable to understand what is relevant in this discussion, and what is not.
The difference is in the license, which is what I pointed out from the beginning, not that Android has a microkernel, which it doesn't.
Leave a comment:
-
Originally posted by Anux View PostI didn't explain well enough what I meant:- If I have a function that adds values I could clone my variable, let 2 threads add values and add the returned values.
- In C I would simply give the same pointer to both functions and wait till they are done.
- Likes 1
Leave a comment:
Leave a comment: