chrash0

i must admit, as someone who has been using Linux (on Intel platforms for that matter) for over a decade i didn’t know this existed. that said, this seems like a huge misstep. maybe it wasn’t a widespread product, but having a reference implementation seems like a no brainer. maybe i’m missing something.

it’s fine as far as laptop keyboards go. i’ve pretty much given up on laptop keyboards being really satisfying. i use a mechanical when possible

it’s not worth it to me. the battery life is a huge feature, and it does feel like Asahi development has slowed. i have enough computers to tinker with. i bought my Macbook specifically to be an entry point into my other machines, i.e. from the airport or brewery or coffee shop.

maybe when it makes sense to buy a new laptop i’ll find some time and motivation to contribute, but just using Asahi doesn’t really appeal to me.

no it totally does. i use Ghostty even

i completely understand. as a Rust developer that uses Neovim, i have some hills like that too. and if i was more of an OS dev and/or had the time i might be interested to help improve the platform. my last attempt was a Thinkpad, but i had to have an external mouse for that thing, the fans were causing me to fail stealth checks, and the battery was basically a UPS.

i know a laptop that’s amazing in almost every aspect except that it doesn’t run Linux. the Macbook Pro. to me there’s barely any real comparison to be made unless Linux or Windows or the keyboard layout is a hill worth dying on to you.

i have servers and my gaming PC on Linux, but i wouldn’t trade my Macbook with its unified memory, incredible battery life, best in class touchpad, and top notch screen for anything else. Windows is dying, and chip designers (outside of Apple) seem more interested in cashing in on AI than providing a user experience. i was excited to see what Qualcomm would do, but it doesn’t seem like OEMs or Windows are particularly interested in supporting that platform as a next leap forward, while Intel is bleeding on the side of the road and AMD is constantly side-eyeing Nvidia. i think it would be peak irony for Nvidia to come out of left field with a desktop class ARM processor that’s Linux native, but that’s a pipe dream. what the ecosystem needs is a real competitor to Apple that is more focused on desktop machines than enterprise contracts. maybe RISC-V Frameworks will break out in a meaningful way. but it just seems like anything else these days in a compromise based on some biased preference or moral judgement.

anyway all that said i’m glad there’s an ecosystem of people who are stubborn enough to work on this platform. i have my own stubbornness, but i just don’t have the motivation to apply it here

academic fraud has always existed

one that i’ve used in the past but isn’t mentioned here is type state based. when developing a file upload service i have a File struct with different states that implement FileState, ie struct File<TState: FileState>. Uploading, Staged, and Committed. Uploading contains a buffer and some block IDs, Staged has no buffer but includes the block IDs, and Committed is just a marker. they can have different methods based on their type state like impl File<Uploading>. this gives us the type safety of, for example, not allowing a partially uploaded file to be committed, while still sharing some state like ID, etc.

this is why i moved from Arch to NixOS. now i know what system packages are installed and can even leave comments in the config to remind myself what the heck cyme does, for instance

god help the poor soul tasked with maintaining a JDK 8 system in AD 2034

yeah it does seem like i need to dive deeper into the manual and get some better diagnostics