Zangoose

They are quite literally taking the "if you don't like it, fork it yourself" approach. Who said they aren't going to make changes/improvements on top of it?

I don't see anyone else mentioning it but this is also probably because brave browser is published under the MPL license so the licenses are actually compatible between projects. They don't want to implement completely from scratch because there is a compatible existing implementation that they can build on top of instead of starting from scratch.

I was born to be a jojo's reference

I was confused about this also, I've been using GameNative on a pixel 10 on and off since I got mine in October. Maybe compatibility just got a lot better because of fixing GPU drivers? I did notice a lot of games had issues but I assumed that applied to anything that doesn't use snapdragon

It depends. I run GrapheneOS and it can pass everything except the most strict integrity check (which is just that you're using a custom ROM at all).

In practice most apps don't have any problems. Google assistant doesn't really work for me but I've seen posts saying people have gotten it working. Google wallet and Google Pay are also explicitly blocked by google, so they will never work.

I think the reason GrapheneOS never did a GSI is because most of their security improvements rely on specific hardware calls that GSI abstractions don't provide access to. This probably would still be an improvement over lineage though, just not as secure as base Graphene is.

The work-life balance is otherwise pretty good and my manager/direct coworkers are chill 🤷

Otherwise I would have lost motivation a long time ago

That's the thing though. Even if the code is good, the plans are good, the outputs are good, etc, it still devolves into chaos after some time.

If you use AI to generate a bunch of code you then don't internalize it as if you wrote it. You miss out on reuse patterns and implementation details which are harder to catch in review than they are in implementation. Additionally, you don't have anyone who knows the code like the back of their hand because (even if supervised) a person didn't write the code, they just looked over it for correctness, and maybe modified it a little bit.

It's the same reason why sometimes handwritten notes can be better for learning than typed notes. Yeah one is faster, but the intentionality of slowing down and paying attention to little details goes a long way making code last longer.

There's maybe something to be said about using LLMs as a sort of sanity check code reviewer to catch minor mistakes before passing it on to a real human for actual review, but I definitely see it as harmful for anything actually "generative"

As someone who has to sift through other people's LLM code every day at my job I can confirm it has definitely not gotten better in the past three months

NixOS manages to be all of these at once except the manual dependency management

As someone who has worked with a pretty large C# codebase and several smaller ones, I've found it to be one of the least efficient languages to program in. This is maybe not a technical fault of the language, but the way Microsoft encourages developing C# means that once you get past a certain point even simple MRs will have 10-20 files changed. There is sooooooooo much boilerplate caused by .NET that even things like Java Spring Boot just don't have (and even then I'd consider Java to be a pretty bloated language in terms of boilerplate).

That's ignoring the fact that the ecosystem surrounding .NET is a lot more enterprise-y, meaning a good portion of libraries require paid licenses to use.

My company uses it for some of our legacy on-prem hosting, but a lot of that is being actively decommissioned.

Most of the world can't feasibly install non-Apple-approved apps on iOS without paying $100 a year so something like that would probably never catch on in iOS land