Last couple of days I've kind of been using #asahilinux as my main non-work OS. This could actually work. It's obviously not great, there are a ton of things that still aren't working, but I'm sort of used to having my #linux setups looking like something I've put together with a lot of duct tape. Now for a change the missing parts aren't entirely because of me, but honestly, it actually feels like #computers being kinda #fun again.

It's also my first full on dive into
#sway, although I've tried it a bunch of times before and gotten it to be nearly good enough so I can switch away from i3. I just still can't get it to a place where I'd feel comfortable doing that on my work machine. I don't have any #X11 packages (except Xwayland) on it and it actually seems to work mostly ok for most everyday things I'd need.
In fact my issues with it fall in three categories.

The relevant one is things still missing in
#asahi itself:
- built-in
#audio being disabled due to the overdrive protection stuff still missing (which is kinda meh for me anyway, I almost always use headphones)
- no
#thunderbolt support, which is the only serious problem as far as I'm concerned, cause I like my keyboard and big monitor setup at home and really wish I could use it with asahi
-
#suspending the laptop doesn't seem to work properly, since it keeps draining a bunch of power in that state, even though it's still less than if not suspended

There are a bunch of tiny annoyances that come from
#sway and #wayland
- some tools I use on
#i3/#X11 just don't have adequate analogies. It's mostly simple stuff like fbxkb, but it still bugs me.
-
#xwayland does lead to some things not working quite as expected, e.g. 1password's global shortcut actually doesn't work, so I need to go and click on it in the system tray to open it. I assume the underlying cause of this is also why the firefox 1password extension acts as a standalone thing, as if I don't have 1password installed separately.
- speaking of the system tray, it seems to be a serious hit and miss w.r.t. what will and what won't work
- the
#clipboard is different. I have developed a lot of habbits around using clipboard and selection on X11 and the fact that that doesn't reliably map onto anything in wayland kinda bugs me, but I realize this is mostly a very me problem.

And then there's the fact that a bunch of stuff seems to not be distributed as an
#aarch64 package. Especialluly packages on #AUR will almost always be marked as #x86_64 exclusive, even though downloading and building from source pretty much always works. I'm guessing that will be slowly getting better over time, especially if more non-apple aarch64 laptops start going more mainstream.
@kunev Pretty much describes my experience as well. Whenever I install an AUR package that is not marked as supporting aarch64 I try to remember to go and leave a comment asking the maintainer to add the arch. We'll get there, little by little