I'm so confused right now.

So this is a lighter weight alternative to other Linux desktops?

Well, it can't run X or Wayland apps, so I wouldn't call it an alternative to those. An alternative to Haiku maybe.

why no X11?

Because everyone's going for Wayland, even though you still need XWayland to do anything useful on it because Wayland is comically incomplete.

well, I mean, why can't this ship with an X server? Or maybe it does and then I'm not sure why it is said that only Haiku apps are supported

It's not that it can't, if you can do something it doesn't mean you should. If we used X it'd be another linux distro isn't it? Part of the fun is to make your own UI feel.

This is great news for my wife and my parents, but it would really be nice to have the choice when it comes to my phone's OS. Just like I had with Linux. I boggles my mind how the components in a phone are somehow different to the components in a PC in that they are unaccessible to people who write drivers for them.

I'm English and have been living in Finland for decades. This is a very Finnish thing in the workplace and I love it. Now and again we will get some new "foreign guy" and it reminds me that some cultures (not all) are following these over polite, social formatting rules. It's a bit annoying, but they eventually assimilate :P

Ruby and RoR is cool and all, but as these web apps got more and more complex, the need for static types became too important. What gave PHP it's edge was types and is the reason I'm still using it after nearly 20 years. PHP seems to implement those important things just in time. OOP, better OOP, types, speed boost, and next probably concurrency.

Is is the need for static types or the need for better testing that is not focused on coverage of line of code?

Because if the domain logic is getting more complex then more types will not catch the bugs unless you are willing for codify business rules within types so then you have to test the types.

Looks like the Google news has peaked some interest. I'm currently waiting for my Xiaomi account to activate so I can unlock the bootloader and install Ubuntu touch on a Redmi 9.

i wonder if the solution is to just ask it to refactor its code once it's working.

I do this all the time but then you end up with really over engineered code that has way more issues than before. Then you're back to prompting to fix a bunch of issues. If you didn't write the initial code sometimes it's difficult to know the best way to refactor it. The answer people will say is to prompt it to give you ideas. Well then you're back to it generating more and more code and every time it does a refactor it introduces more issues. These issues aren't obvious though. They're really hard to spot.

You can, and it might make things a bit better. The only real way I've found so far is to start going through file by file, picking it apart.

I wouldn't be surprised if over half my prompts start with "Why ...?", usually followed by "Nope, ... instead”

Maybe the occasional "Fuck that you idiot, throw the whole thing out"

Oh, is this the deal with GrapheneOS too? Damn, I was excited about the Moto GrapheneOS collaboration.

So far its working pretty great. Very happy with GrapheneOS. And currently Android AOSP source code is still regularly released. If that changes it becomes a problem then.

I would buy a cheap Moto with GOS in a heartbeat