devaiops9001

Even if they have GrapheneOS, the lead developer of GrapheneOS publicly admitted struggling with mental health issues. People with mental health issues and severe personality disorders are very easy for nation state actors to manipulate and compromise. GrapheneOS is very strong on the technology specifics, but there's more to safe computing than just the technical part.

GrapheneOS, despite its human problems (as admitted by its project lead), does have at least near perfect if not perfect compatibility with the Google Pixel devices listed as release targets on the GrapheneOS website.

What exactly to do to benefit from the technology benefits of GrapheneOS, but protect the actual users, is still an open question.

Almost a year a go the lead developer of GrapheneOS, Daniel Micay, publicly admitted that he was experiencing mental health issues and announced he would step down from the project. As displayed by Micay's behavior, just in the last few days even, he is still dealing with those issues. Micay will jump to cry he is being "harassed" and melt down when he meets just the slightest amount of resistance in a discussion that hasn't deviated from technology. He will even do this simply due to the format or style one chooses to reply with, irrespective of content.

Today, we can see that Micay deleted off of GitHub his announcement that he stepped down, probably when he thought not a lot of people were looking. As evidenced by the writing style and choice of words on the project's social accounts, Micay is operating those social media accounts. The recent Git commit history shows he's active in the project again.

Micay does do great technical work. However he is very quick to jump to accuse others of "harassment" and "misinformation", dividing development efforts and excluding others from projects in what looks like an attempt to control others and reduce competition in the space.

As Louis Rossman pointed out, Micay bullies other people, some would even call it "harassment", then tries to hide it behind an excuse the he suffers some form of autism.

I looked into the "issues with the leadership", and everything I found was all a bunch of crap. The head of NixOS made a mistake stepping down, he should have told the SJW losers to get fucked.

This quote below, is really fucking dumb. A GNU+Linux distribution should absolutely never ever do this. GNU+Linux is not only not Windows, it should not adopt the very stupid patterns native to the mind of a Windows user. The guy who wrote this article should fuck off back to Windows.

" You ask me if it is possible to use popular tools like Chrome on Ubuntu. I say yes. Just download it from the official website and install it by double-clicking like you do it with exe files in Windows."

They should release the code.

eww, gross

An iPhone should be like a Macbook.

A user should be able to load a cryptographic key to the bootloader and boot any OS of their choosing. I'm kind of more on the extreme "Free Market" way of thinking, but even I think that government should step in and force an iPhone to be like a Macbook in this way.

>> in decades there will a vocal contingent of people lamenting the fact that we all run immutable Microsoft Kubernetes Ubuntu (MSKU) instead of using the more refined NixOS approach.

You are, unfortunately, correct. Some of us still run illumos Unix (SmartOS), but we are a tiny minority. I hope that things can work out so that something other than the lowest common denominator is accessible enough to also have a pervasive footprint.

A lot of very crummy ideas are popular in ways that would not have been imaginable 15 years ago.

>> or even an unsophisticated approach like a Dockerfile

In a handful of "higher end" on the salary side of DevOps/SRE roles I have done, I managed to quietly do things with flake.nix -- next time around I'll do them with Guix. I can get Guix container images going, that's not hard for me.

But yeah, doing things non-Docker isn't too hard for us DevOps ninjas (what DevOps was in 2012, not the watered down thing today).

After doing flake.nix, I managed to get written company policy ratified by our legal team that all container images must be binary reproducible. That probably fell apart since I left, unless the high quality CTO I was serving is still there.

>> base container images

This is very easy to solve for.

>> choice of scheme

There was more wisdom when everyone at least tacitly acknowledge that maybe not everyone should be touching servers.