Serious question: how is this similar to TockOS, other than being written in Rust? TockOS doesn't use an MMU since it's designed for single-address-space applications on microcontrollers.
1,288 karma · joined June 4, 2016
(If you think that issue trackers should be for users to be able to tell each other if they've experienced the issue too, then that's part of the problem with "+1", "Me too", "fix this please", and other useless comments. That's what a forum is for, and today they're super-easy to create. You don't even have to host them yourself, nor do you need to be affiliated with the project!)
Lesson: if you don't trust the maintainers, you can't trust the software. Keep your own fork and issue tracker if this is a problem, but don't force maintainers, many of whom are not acting in a professional product management capacity, to do extra work for your benefit.
Freedom of speech does not imply freedom from consequence.
1) This is being used as a target for Servo. Even if it ends up being useless (I won't pretend to be able to predict the future), the investigation into getting consistent 90+ FPS performance out of web rendering engines, regardless of content, is going to be excellent for the web. VR is a challenging environment for the Servo team to prove its technological prowess, and for many engineers, a challenging environment is exactly the kind of motivation necessary to push at boundaries.
2) Mozilla missed the "social" hype train and their mobile OS project was widely considered too little, too late (not to mention the terrible performance of mobile web engines at the time). Both of these areas are dominated by large, (effectively) proprietary vendors. Facebook's purchase of Oculus signaled to many that "social" was going to move to yet another platform. Mozilla's goal here is to get out in front of a potential VR hype train, keeping the open web as a major player in order to keep their mission relevant.
3) Mozilla believes the web is the ultimate platform for connecting people. It is one of the few markets with a political landmap that encourages collaboration between the multiple players. Therefore, for Mozilla, the capabilities of the web must always be expanded to prevent balkanization of the Internet into product-specific networks, such as Apple's iMessage. I am actually encouraged by their willingness to jump in front of VR, despite my own belief that VR won't be as relevant as many prognosticators think.
This is my analysis, take it with multiple grains of salt.
Personally, I'm of the opinion that APIs should be as misuse-resistant as possible, and GPG is notoriously intransigent about actually acting as a well-designed API. Additionally, The Update Framework (TUF, https://theupdateframework.github.io/) prevents these issues by design.
> if you want to make a mess of things in your application you can do so without bringing down the whole system
You don't need an exclusive community to make that work. We as an industry have tools: fuzzers, testing frameworks, better programming languages and type systems, and proof assistants, all of which will do a better, more consistent job of ensuring quality than project leads being assholes.
My workplace is extremely polite to each other AND we don't lie to each other. I recently submitted a code review that was full of violations of the style guide, and nobody was rude nor dishonest.
This line of thinking is a fantastic way to create a non-inclusive group.
Gotta stop you right there. Hero worship should not be considered a good thing in our industry.
The kernel subsystem maintainers, who actually review the code prior to getting it merged, are the ones with the real power and the necessary knowledge, and I'd argue they are more qualified to oversee the project's future than Torvalds.
1. The Rust team is on top of releasing fixes for these bugs. Additionally, the new borrow checker has detected all of the recent borrowck bugs.
2. The code required to produce this does not look like idiomatic Rust. One would hope an organization adopting Rust would choose to review such blocks of code with more scrutiny. That said, this isn't enough of a guarantee -- such code could be buried deep inside a large patch, making it challenging to discover.
I eagerly await the new borrow checker, and other projects aimed at increasing confidence in the Rust compiler's checks.
Sick of the C Apologism Task Force's idea that "if only rockstar programmers wrote code we wouldn't have any problems", completely ignoring the reality of software development and the evidence of 50 years of exploits.
If you aren't in Rust, just use Vulkan. There are high-performance wrappers for it in various stages of development, such as MoltenVK[2] for macOS and iOS, and VulkanOnD3D12[3] for UWP. Non-UWP Windows, Linux, and Android should support Vulkan natively through their GPU drivers.
[1]: https://github.com/gfx-rs/gfx