Technology

60060 readers

2898 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago

MODERATORS

[email protected]

353

Maestro, a Linux compatible kernel written in Rust. (blog.lenot.re)

submitted 11 months ago by [email protected] to c/[email protected]

77 comments fedilink hide all child comments

Enter Maestro, a unix-like monolithic kernel that aims to be compatible with Linux in order to ensure wide compatibility. Interestingly, it is written in Rust. It includes Solfége, a boot system and daemon manager, maestro-utils, which is a collection of system utility commands, and blimp, a package manager. According to Luc, it’s creator, the following third-party software has been tested and is working on the OS: musl (C standard library), bash, Some GNU coreutils commands such as ls, cat, mkdir, rm, rmdir, uname, whoami, etc… neofetch (a patched version, since the original neofetch does not know about the OS). If you want to test it out, fire up a VM with at least 1 GB of ram.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 11 months ago (3 children)

Imo rust won't replace cpp without true Oop so I might just make my own objective rust and piss off Oop haters

[–] [email protected] 9 points 11 months ago

There has been no true OOP language since smalltalk, which btw wasn't class-based.

In practical terms Rust has subtyping -- barely, at least in technical terms the only thing that uses true subtyping is lifetimes. In practical terms you have qualified types (aka traits) supporting interface inheritance which is perfectly proper as everybody knows that you shouldn't inherit implementation as the Liskov Substitution Principle is undecidable.

"Language X will fail because it's not OO" what's this, the early 00s? I thought we left that hype train behind.

[–] [email protected] 2 points 11 months ago

What is true OOP?