And here go two pages of the (off-topic?) comments at coreboot-releated thread that do not mention the coreboot opensource BIOS :P
In order for Redox OS to succeed as coreboot's internal part, they should somehow fit it (maybe with LZMA compression) to about 3MB - so that, together with almost 1MB coreboot, this Redox OS would be able to fit to a standard 4MB BIOS chip. If they can do this, then it could succeed
Announcement
Collapse
No announcement yet.
Redox OS Exploring Coreboot Payload, Other Improvements
Collapse
X
-
Originally posted by cl333r View Post
My issue with Rust is parent-child relationship which can't be implemented "natively", either use Rc<RefCell<>> + Weak<RefCell<>>, or a third party library that does God knows what under the hood. I wonder how Redox implements its parent-child logic if any.
Last edited by shmerl; 24 February 2019, 02:56 AM.
- Likes 1
Leave a comment:
-
Originally posted by cl333r View Post
My issue with Rust is parent-child relationship which can't be implemented "natively", either use Rc<RefCell<>> + Weak<RefCell<>>, or a third party library that does God knows what under the hood. I wonder how Redox implements its parent-child logic if any.Last edited by lordnaikon; 23 February 2019, 08:00 PM.
- Likes 2
Leave a comment:
-
Originally posted by kaprikawn View Post
The stated goal of Redox is to have an OS written in Rust. X11 isn't written in Rust, it has a massive codebase, and it is legacy now. So porting it would be a mammoth task and be incredibly dumb. Whereas Wayland is a relatively small protocol, they could easily write something in Rust that could use it. I'm not saying they should, but Wayland is at least an option.
- Likes 2
Leave a comment:
-
Originally posted by cl333r View Post
My issue with Rust is parent-child relationship which can't be implemented "natively", either use Rc<RefCell<>> + Weak<RefCell<>>, or a third party library that does God knows what under the hood. I wonder how Redox implements its parent-child logic if any.
Prior to version 1.0, Rust actually had a garbage-collected pointer sigil (@ instead of & or *) but it was converted into the Rc and Arc standard library types as part of the effort to not specially privilege things which, algorithmically, are just standard library types.
(Which, for that matter, granted the added benefit of being able to explicitly choose between the minor performance boost of not using atomics (Rc) and the support for multi-threaded access that comes from using atomics (Arc)... or various other kinds of pointers from crates.io)
Rust is a victim of its own success if you're complaining that its compile-time prover for the correctness of single-ownership access (something no other language has yet, though Ada is working on it) isn't smart enough to prove correctness of multi-ownership access at compile time... something which may be impossible at a theoretical level.
That said, I'm not immune to that either. I come in from Python, which is horrendously slow by comparison, everything is wrapped in an Rc<T> and heap allocated, and the language uses a Global Interpreter Lock because putting everything in Arc<T> would be too slow, and, before you can blink, I'm grumbling about the complexity of making certain things purely stack-allocated and singly-owned with minimal copying. Rust just makes it so nice most of the time, that you don't want to resort to what GCed languages do under the hood all the time.
- Likes 1
Leave a comment:
-
Originally posted by kpedersen View Post
Why go though XWayland when just an implementation of X11 would be faster and have more GUI applications available to it?
Basically, standards generally take priority. Niche Linux compatibility can wait!
- Likes 2
Leave a comment:
-
Originally posted by kpedersen View PostI am not so sure I am convinced yet, but that is why this project is quite important to me. To find out if Rust really is the solution.
Leave a comment:
-
Originally posted by Compartmentalisation View PostBut what big advantage does Redox give at that point?
I am not so sure I am convinced yet, but that is why this project is quite important to me. To find out if Rust really is the solution.
Originally posted by Compartmentalisation View PostSoftware still keeps focusing Linux since the '00s.Last edited by kpedersen; 23 February 2019, 06:35 PM.
- Likes 1
Leave a comment:
-
Originally posted by kpedersen View PostI suppose if it can be supported by the main VM systems like VirtualBox, then that is actually a good start for user uptake.
Also, since about 3 days ago, I've conveniently seen some companies doing taxes going for upwards of €5000+ per hour billing VMs so those proven VMs are getting some attraction on the big money market.
- Likes 1
Leave a comment:
-
Originally posted by Steffo View PostA wayland implementation would be cool. This might ease porting applications with an GUI.
Basically, standards generally take priority. Niche Linux compatibility can wait!
Originally posted by Compartmentalisation View PostEven if this would be the best OS base in the world, would anyone be able to run it? As in, what's the driver state?Last edited by kpedersen; 23 February 2019, 05:42 PM.
- Likes 1
Leave a comment:
Leave a comment: