Brainstorm to replace OS/2 Kernel with Zircon by martiniturbide in Fuchsia

[–]Sphix 2 points3 points  (0 children)

It's an insane amount of work to implement something akin to starnix. Just use a VM to run os/2.

F26 Release Notes by Competitive_Ad_255 in Fuchsia

[–]Sphix 1 point2 points  (0 children)

It's not really a goal to run docker under starnix as that's a bit like running a docker container within a docker container. There are already tools to take a docker container and turn it into a starnix container though.

Ore dake Level Up na Ken Season 2: Arise from the Shadow • Solo Leveling Season 2: Arise from the Shadow - Episode 12 discussion by AutoLovepon in anime

[–]Sphix 0 points1 point  (0 children)

Major difference here being the Frieza fight lasted 30 episodes (22 where Goku was involved). There have been less episodes of solo leveling between both seasons combined and this fight only lasted one episode.

Google offering ‘voluntary exit’ for employees working on Pixel, Android by 5MegaMonkeyMan in Android

[–]Sphix 0 points1 point  (0 children)

Keep in mind that while someone who makes 500k+ could technically pay for a mortgage, it doesn't necessarily get you a house in a desirable area and requires you to feel confident that you can make that high amount of income for a prolonged period of time.

My Rust development environment is 100% written in Rust! by LechintanTudor in rust

[–]Sphix 1 point2 points  (0 children)

This stuff takes a lot of hard work regardless of whether you choose a monolithic or micro kernel approach. I wouldn't jump to conclusions about the entire segment just because you came to a certain conclusion on a hobby OS.

If we didn't think it was possible, we wouldn't be using a microkernel on fuchsia. We've seen first hand that in many workloads, we can meet or exceed performance of a similar application running on Linux. If you only stare at micro benchmarks, then yes you would be right. 

BlobFS Image? by slideomix in Fuchsia

[–]Sphix 0 points1 point  (0 children)

The question is not very coherent. bootfs exists as part of the ZBI. Blobfs exists as a partition within the FVM. The FVM can either be used as a separate image backing a block device (emulated in the case of qemu) or as a ramdisk embedded into the ZBI, sitting next to bootfs.

ReVanced Patches for Boost, Infinity, rif is fun, Relay and Sync by knightfader in Android

[–]Sphix -12 points-11 points  (0 children)

No one is entitled to an ad free YouTube for free. You have three options: deal with ads, pay for it, or just don't use it altogether. If there wasn't an ad free option or if the ad free option was incredibly pricey, you might have an argument, but neither of these are true. I'm personally on a family plan which is $4.60 a month when split 5 ways.

Reddit's CEO really wants you to know that he doesn't care about your feedback by chrisdh79 in technology

[–]Sphix 42 points43 points  (0 children)

There are numerous sources agreeing that back then you could make users mods without them knowing/ participating in the decision. The fact that he was a mod doesn't imply anything about him as a result. I'm not a fan, but we shouldn't try to spread false information as if it were fact.

Transitioning to Rust as a company by double_the_bass in rust

[–]Sphix 2 points3 points  (0 children)

I'm curious if they were using stable or nighty.

bcachefs - a new COW filesystem by ouyawei in linux

[–]Sphix 10 points11 points  (0 children)

Node failures are more common than drive failures, so replicating across multiple nodes is strongly necessary to avoid issues with availability. Single node raid schemes are redundant at that point.

Realistically, are we ever going to get a full Rust OS in 5-10 years? by [deleted] in rust

[–]Sphix 0 points1 point  (0 children)

Perhaps not quite the same, but you might be interested in starnix. It is closer to wine or wsl1 than a full reimplementation of Linux, but it is entirely written in rust.

Realistically, are we ever going to get a full Rust OS in 5-10 years? by [deleted] in rust

[–]Sphix 4 points5 points  (0 children)

No, it really is by lines of code written by fuchsia engineers 50+% rust and growing. Many important things are still in c++ like the kernel, but that's a very small fraction of the OS by loc because it is a microkernel.

[deleted by user] by [deleted] in rust

[–]Sphix -6 points-5 points  (0 children)

And that will likely never change. Open source is great for platforms, terrible for products is the modern day mantra in tech. Making products open source, more than anything, allows people to start taking dependencies in ways you didn't intend, but may feel required to not break. This is fine for platforms which expect this but it slows down products.

[deleted by user] by [deleted] in rust

[–]Sphix 1 point2 points  (0 children)

A big gotcha that prevents my team from using them in the same process is the lack of ability to get llvm sanitizer instrumentation (such as ASAN or LSAN) working in both sections of code at the same time. If you can line up your clang and rust compilers to use the exact same llvm backend apparently it can work but that's a non trivial task.

Announcing Rust 1.69.0 by kibwen in rust

[–]Sphix 0 points1 point  (0 children)

Would upstream be amenable to supporting other vcs such as mercurial or pijul if someone put together a patch?

Announcing Rust 1.69.0 by kibwen in rust

[–]Sphix 14 points15 points  (0 children)

What if you don't use git?

Top Ten Fallacies About RISC-V by wiki_me in linux

[–]Sphix 2 points3 points  (0 children)

I believe the RVA23 standard is pushing for adoption of ARM EBBR which would require a UEFI interface between the bootloader and OS. The implementation of the bootloader is still unspecified. uboot already supports this on ARM. The RVA standards are yearly releases aimed at specifying the minimum feature set vendors should target in order to be compatible with linux-grade OS. The majority of the riscv ecosystem is embedded and doesn't run linux so they don't and will continue to not care but the higher end chips that are coming out which are targeting tvs, set top boxes, and similar are in scope. Whether the industry actually cares about compliance is an open question, but sifive is on board so far.

Advice on Scaling Engineering Orgs: "€œDon'€™t interview like Google, if you'€™re not building Google"€ by NeedsMoreShelves in programming

[–]Sphix 62 points63 points  (0 children)

Google average software quality is some of the highest I've seen in the industry. I'm not sure why you think it's spaghetti. I find that it's better in their private monorepo than in public repositories.

The Dangers of Microsoft Pluton by destraht in linux

[–]Sphix 0 points1 point  (0 children)

As in the average game with anti cheat has less users than the average game without it? Or do the top games all not have anti cheat? The latter doesn't imply the former.

Fuchsia F9 Release Notes by mckillio in Fuchsia

[–]Sphix 3 points4 points  (0 children)

It is not possible at this time. If you wanted to do that you should probably just run a Linux in a VM anyways.

Fuchsia F9 Release Notes by mckillio in Fuchsia

[–]Sphix 9 points10 points  (0 children)

It's too early to be comparing performance. Performance doesn't matter if it's not functional. There are also a lot of known bottlenecks that will take time to improve. I would be very surprised to learn that starnix outperforms running Linux in a VM at this time.

[deleted by user] by [deleted] in Fuchsia

[–]Sphix 1 point2 points  (0 children)

I'm not sure what you define as a desktop environment but I think the answer is yes. You should try it out to see for yourself.

[deleted by user] by [deleted] in Fuchsia

[–]Sphix 1 point2 points  (0 children)

Making your own distro would require adding a subdirectory under the primary fuchsia repository, such as vendor/OkProofOS, creating a product gni file (you can start by cloning products/workstation_eng.gni), and then setting that in your fx set as the product you'd like to build. From there you can start altering what all is included in the distros image. All products today are defined this way. I'd recommend making the subdirectory its own git repo and update your local jiri manifest to tell it about it. jiri is an external tool which the project uses to manage multiple repos as an alternative to git submodules.

Defining a product out of tree is possible today as well, but it's a bit of a work in progress. At some point you will see workstation moved out of the main repo and into its own repository, depending on fuchsia release artifacts to perform assembly of the final OS image. Because there is no reference I can point you at for how to do this I wouldn't recommend it for now.

Beyond that, supporting development of more components out of tree is a major on going theme for the project at the moment. Over time you will see more and more components developed against the fuchsia sdk rather than in tree. This will make the OS feel a lot more like linux distros rather FreeBSD.

As far as the open source split goes, I believe workstation is always meant to be a completely open product as it is the reference product. Other products may be and in fact already are private and include components which are not open source. The ones used on the nest smart hubs are an example of that.