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.

Ok but there’s a big difference between being on the bleeding edge of tech and releasing games which are borderline unplayable because of bugs and framerate issues to the point where Nintendo issues an apology on your behalf.

I think I’m cautiously optimistic after seeing the gen 10 trailer, but at the same time after ZA I’m ready to skip out on it if the direction looks bad.

I just want my black/white remakes so I can be done with this franchise -_-

Not that I want to defend Nintendo but Palworld barely even qualifies as the same genre as the mainline Pokemon games, literally the only thing they have in common is that you catch monsters

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

I’m comparing hardware to hardware, not artificial Apple software restrictions.

That’s great but hardware doesn’t exist in a vacuum. With an ecosystem as locked-down as an iPad’s you can’t just ignore the software. It’s not like you’ll ever be able to uninstall it because it’s intentionally locked down, unlike a macbook which allows installing apps and even modifying the bootloader to boot into a different OS.

Edit: Forgot to mention the fact even for people that might not care about that, iOS will automatically kill any app that uses more than a certain amount of RAM (I think it was 4GB? I don’t remember the exact number) so in a lot of scenarios you can’t even take advantage of the hardware in an iPad because of the locked down software

Ok but if you want to do actual work on it then these things absolutely do not cancel each other out because you have to spend $270 on a keyboard/trackpad regardless, and now have to use a clunky touchscreen on your 13 inch tablet half the time.

Yes, the M4 is much faster and it is probably only stupid product segmentation keeping it on the iPad. But the reality is, iOS/iPadOS puts OS-level limits on how much you can even take advantage of that hardware even if there is an iOS app for the thing you want to do

TLDR: If you really want a MacBook just get a refurbished M1/M2 MacBook and call it a day, bonus points for putting Asahi on it

That’s fair, I assume most people probably aren’t following ladybird that closely so it’s easy to miss. It just bothers me because shrugging off small individual problems and ignoring a bigger trend is arguably what let people like DHH get a platform in the first place.

How many times do I have to give him the benefit of the doubt though?

First it was the “using they in documentation is political ideology” Github issue, then he publicly defended DHH when people called him out for being a white supremacist, he implied tech companies are discriminating against white people with diversity policies, and he tweeted that he hopes young people will carry on Charlie Kirk’s legacy.

If one or two of these things happened in isolation, I could maybe understand giving him the benefit of the doubt as a non-American (for that last one) non-native English speaker. But all of these things taken together? I personally don’t think I can look past that.

All things considered the way they’re approaching the migration is fine enough - they’re only moving specific portions at a time, they’re not stopping C++ development, and they’re making sure it doesn’t introduce regressions. Adopting a memory-safe language for something like a browser makes sense because it completely eliminates that class of vulnerabilities.

The problem is the way they’re approaching the code itself. From their wording, it sounds like they’re relying on AI heavily for both writing and reviewing the code. Rust has a steeper learning curve than most languages and is very different from C++. They even mention in the blog that their current Rust code looks like C++ code ported over. If they don’t take the time to actually learn Rust before adopting it, it’ll just lead to security logic issues that their AI couldn’t catch because C++ and Rust don’t always behave the same way. And that’s completely ignoring all of the other ethical/technical issues with AI

Ok but the radio station change might cause my car to spontaneously combust so I should make a new car from scratch with my car factory just in case, that way I’ll still have a car.

Never change, NixOS

Nah NixOS is a picture of a factory automatically making cars

Presumably just for transparency in case humans down the line went looking through closed PRs and missed the fact that it’s AI.

Xlibre is backed for the most part by the singular maintainer that was still willing to work on X11 who got kicked out for being too toxic and breaking existing code. For what it’s worth, it also explicitly used MAGA language in its README for a while.

Phoenix is intended to allow for support of legacy software/DEs and provide a more modern/maintainable version of X11. It isn’t trying to compete with Wayland, it’s trying to live alongside it for environments that won’t or can’t move to Wayland. It also technically won’t be a complete X11 implementation, as it’s ignoring older portions of the protocol.

Neither option addresses the elephant in the room: The X11 protocol is still fundamentally broken in a lot of aspects. Multi-monitor support, especially when monitors aren’t the same resolution, refresh rate, or physical size, is broken at a fundamental level. It will never work even as well as Windows, which is already an incredibly low bar to clear.

Wayland is slow moving, sure, but it is a much more stable base to work with than Xorg ever was. From a security, modularity, and extensibility standpoint, Wayland is a lot better. There is a reason most of the Xorg team developed a completely new protocol instead of just reimplementing X11 themselves.

It can be hit or miss, really depends on the bank. I’m in the US and mine worked fine after I enabled a compatibility setting in the app list, but that’s kind of anecdotal. I think there is a community compatibility list somewhere of banking apps that work/don’t work on GrapheneOS.

If you were able to install Bazzite then installing graphene shouldn’t be any harder than that. It has a web-based installer that was pretty easy to use as long as you follow the instructions.

The pixel 8 will be supported through the end of 2030 (graphene support follows the same timeline as Google because of firmware-level updates that are still needed from them) so you could still get a lot of use out of it.

GrapheneOS my beloved