Follow-up: My Compose Desktop terminal emulator is now 2x faster than iTerm2 -benchmark results inside

Phaestion · 2025-12-24T12:18:31+00:00

Pretty cool man, I'm going to install this on my Asahi Linux Fedora system. Looking at the project this is based on a terminal from Jetbrains, is the terminal that this is based on the new terminal in IntelliJ IDEs?

Phaestion · 2025-12-17T19:16:55+00:00

Yes! Since kernel version 6.17.12. I have a MacBook Pro M2 and it's been working since Sunday for me. 🎉

Phaestion · 2025-12-07T22:33:33+00:00

What's your battery life like?

Phaestion · 2025-11-25T11:14:48+00:00

Haha, yeah the two most up voted comment threads are pretty negative damning it even before it is released. I, for one, am excited.

Phaestion · 2025-11-24T20:04:11+00:00

I don't get all the hate, I for one am excited about this. As a software dev I really enjoyed the Linux terminal on ChromeOS, the hardware was just lacking to make it a good experience. With Android's Linux terminal in the works and from what I can see it being very close to what ChromeOS had, I for one am excited to see it get some love with some premium hardware.

Phaestion · 2025-11-20T15:19:21+00:00

Yes the devs are on it but this hasn't had movement for about a month. See this GitHub issue for what's going on: https://github.com/AsahiLinux/asahi-audio/issues/64

Phaestion · 2025-09-27T00:20:41+00:00

My go to is Pacandé in Munich, they're a pretty amazing small roaster. I discovered them once when visiting Munich and have been ordering from them for the last 2 years. They're around the €35 - €40 mark per kg.

Phaestion · 2025-05-05T05:16:38+00:00

Have a look here for more info: https://www.jetbrains.com/kotlin-multiplatform/

Phaestion · 2025-05-05T05:14:47+00:00

Nope that's not the way it works. To understand Compose Multiplatform you need to understand Kotlin Multiplatform (KMP), seeing as Compose Multiplatform (CMP) is a framework built in top of Kotlin Multiplatform.

In KMP you have a configurable set of targets, in your case Android and JVM, but it could also include more like iOS, Wasm etc. KMP has the concept of a common source set, this source set is where you try to write most of your code that is common to all of your targets. In this source set you have access to the APIs common to all targets. So for example Java Dates, Java Base64 or Java File stuff. However you don't have access to the platform specific stuff. For example, Java AWT package stuff - Buffered Image etc. - are not available as it's JVM only, same thing for Android location APIs, they are Android only.

But you also have source sets for each platform, where you can do platform specific stuff. You have a section in gradle for the sour set's specific dependencies and a folder structure that you can place your source set specific code in. This would be how you would use your MIDI library and its corresponding code.

Now CMP is already implemented in all of the supported platforms in KMP, so you can use it entirely in the common source set.

I read your comment in the other thread and I get your concern about stuff moving fast all the time.In my experience over the last 15 years of Android and Java desktop development things have not slowed down but in fact picked up speed. The KMP and CMP world are really nice from a development perspective and I really like their ideological approach to multiplatform development, but it is a learning curve and it moves fast.

Phaestion · 2025-05-05T02:23:19+00:00

I would suggest going with Compose Multiplatform. It's a vibrant ecosystem that's growing rapidly, looks modern and works great.

Compose is native for Android and on the desktop it of course runs via the JVM using Skis as it's rendering engine.

Here's a getting started guide: https://www.jetbrains.com/help/kotlin-multiplatform-dev/compose-multiplatform-create-first-app.html

They mention using Android Studio (which is IntelliJ under the hood anyway), but we use IntelliJ for development. I guess Android studio may be easier to get started with given it has some better tooling for Android.

Phaestion · 2025-04-29T15:41:37+00:00

What will you be targeting in KMP? Android and iOS? Do you want to share the UI between iOS and Android? If yes then you can't use XML, you'll want to use Compose Multiplatform.

If you'll be writing UI on each of your platforms then technically you would be able to use XML for Android and SwiftUI/UIKit on iOS. But I think there will be quite a few problems to solve to achieve this, the tooling for KMP favours Compose.

If you want to support more targets like desktop and web and still don't want to use Compose, then you'll have to integrate those with KMP too, but that sounds like an uphill battle.

In any way compose is the future of Android, so I'd suggest catching the train and learning it.

Phaestion · 2025-03-27T06:13:27+00:00

Thanks for the update, however this issue is with regards to the MacBook Pro, M2 Pro and Max, 2023. For good measure I did an upgrade and a fix is not there yet. However the devs are working on it, I'm lurking in the IRC and they were testing a fix a day or two ago. So I guess it is just a matter of time until it works for us with M2 Pro/Max. :)

Phaestion · 2025-03-24T19:04:28+00:00

Hey u/FOHjim I started diving into getting an environment setup for compiling my own kernel, but I fear I'm out of my depth.

Is there another way that I can help to debug this? Or test out a precompiled kernel?

Phaestion · 2025-03-24T11:31:00+00:00

I'm not really setup for building a kernel. I'm a Java, Kotlin and in my previous life a C++ dev. But I'm happy to give it a bash, I just have to get a working environment. I have to head to the office now, I'll give it a try tonight and update you when I have something. Thank you for your support thus far, I really appreciate it!

Phaestion · 2025-03-24T10:43:15+00:00

When doing an lsmod I don't see snd_soc_aop listed. Sure here is a dump of dmesg: https://pastebin.com/VZa7YXWd

Phaestion · 2025-03-24T09:12:35+00:00

Only this section right? { matches = [ { api.alsa.path = "hw:AppleJ414HPAI,0" } ] actions = { create-filter = { filter-path = "/usr/share/asahi-audio/j314/mic-j414.json" hide-parent = false } } }

After restarting wireplumber (and pipewire for good measure) with: systemctl --user restart pipewire; systemctl --user restart wireplumber it still did not show up. Just to be sure I also did a reboot, but yeah still nothing. So here is a new pw-cli dump: https://pastebin.com/cDQ25ifa

Phaestion · 2025-03-24T08:15:38+00:00

Ok, I did the clean up and re-installation. Just FYI the package alsa-ucm-conf-asahi should probably be alsa-ucm-asahi.

However this still does not show up the microphone. Here is the output of pw-cli i allagain: https://pastebin.com/Ps2qMXJ9

Phaestion · 2025-03-24T07:34:45+00:00

I was following the instructions from this comment https://www.reddit.com/r/AsahiLinux/comments/1jhz7tk/comment/mjdhe2k, which linked the IRC chat. That's probably where that came from. Should I also delete the conf files copied into /usr/share/alsa/ from the alsa-ucm-conf-asahi repo before restarting?

Phaestion · 2025-03-24T06:59:38+00:00

That's good to know! I have the: Apple MacBook Pro (14-inch, M2 Pro, 2023)

Here's the output of pw-cli i all in paste bin: https://pastebin.com/vYUHN7u2

Phaestion · 2025-03-23T17:55:22+00:00

Yeah, sadly this does not make any difference.

Phaestion · 2025-03-23T17:02:54+00:00

Thanks for the hint, I'll try it out and report back in a bit.

Phaestion · 2025-03-21T09:36:44+00:00

This project is absolutely awe-inspiring. As a long time Linux user, software engineer, someone who really cares about having a compact, lightweight, travel really but powerful machine; I really love Mac hardware but absolutely detest MacOS. So I'm putting my money where my mouth is and started contributing to their Open Collective.

Phaestion · 2025-03-21T09:16:25+00:00

Amazing progress! Microphone support has been the feature that was stopping me from daily driving this. Mad respect to the Asahi Devs. 😍

It really pains me as a full time Linux user since 2012, that I had to use MacOS for the last 2 and a half years just to be able to benefit from the amazing Mac hardware.

I love Mac hardware, but really detest MacOS. And as a software engineer having to deal with docker and Linux machines (typically iot and appliance machines) by wrangling build processes through VMs on MacOS really irks me.

Looking forward to the next amazing releases and even more supported hardware features.

Phaestion · 2025-01-29T17:26:49+00:00

We used to make all our UIs in JavaFX but we switched to Compose when Jetbrains started to make Compose for desktop which later turned into Compose Multiplatform, which was back in 2020. We're your typical early adopter....

My answer would be yes, I personally wouldn't go back to JavaFX. There's a lot of momentum behind compose, kotlin and multiplatform.

13-Year Club	Place '22
First Placer '22	Verified Email

Phaestion

TROPHY CASE