| 8 Mar 2026 |
 Randy Eckenrode | * | 11:03:00 |
 ragdoc | Do you guys expect nix-darwin to work with the Notebook Neo? The instruction set of its A18 pro should be close enough to the M chips', correct? | 11:56:42 |
| Randy Eckenrode | If Apple releases a Mac that doesn’t support existing applications, they really messed up. | 11:57:23 |
| Randy Eckenrode | So I’d expect it to work unless Apple uses it to introduce some new hardening feature to macOS that breaks Nix. | 11:57:53 |
| Randy Eckenrode | Like making the user experience more like iOS, but I highly doubt that. | 11:58:18 |
 toonn | I wonder more about Asahi compatibility. | 11:59:35 |
| ragdoc | I also wonder if building nix-darwin packages will work well enough, what with the 8 GB unified RAM limit and reduced CPU oomph. I don't expect nix-darwin to cache pre-built stuff for the Neo. | 12:00:34 |
| Randy Eckenrode | nix-darwin won’t know. We don’t build CPU-specific packages. | 12:01:56 |
| Randy Eckenrode | Rebuilds (especially of bigger packages) will suck though. | 12:02:13 |
| Randy Eckenrode | (Other than instruction sets. We tune for M1.) | 12:02:29 |
| Randy Eckenrode | * | 12:02:51 |
| Randy Eckenrode | * | 12:03:25 |
| ragdoc | To be fair, the Neo is not aiming at the type of tech-savvy folks who would care about their package manager. | 12:04:25 |
| ragdoc | I'm still sad about the support for AMD64 going away. Bugger. What good is a beefed up MacBook Pro if it is no longer supported. That machine served me exceedingly well, and it would continue to do so with software support. | 12:07:50 |
| Randy Eckenrode | That’s the nature of hardware transitions on Apple platforms. They’ve executed it successfully several times (m68k to PPC, PPC to Intel, Intel to Apple Silicon), but they always drop support for the old architecture eventually. | 12:10:14 |
| ragdoc | Oh, I know that well enough, having gone through it before. It's understandable from Apple's POV, but that doesn't soften the blow for Joe User. I love my MacBook Pro, old as it is, and could very much do without the cost involved in switching to an M-series based device. | 12:13:53 |
| Randy Eckenrode | I was not fond of my old Intel MacBook Pro. It was noisy and hot under load. I replaced it as soon as I could. | 12:16:03 |
| Randy Eckenrode | I used one of those apps to turn off turbo boost just to keep the noise down. | 12:16:30 |
| ragdoc | It's admittedly not a quiet device, compared to the 2026 llineup. It was however quieter than the machines surrounding it in my work environments, which fell under "good enough for the girls I go out with". 😉 | 12:19:02 |
|  @luzifer2222:matrix.org left the room. | 12:48:38 |
 emily | have you considered running NixOS on it? | 14:02:01 |
| emily | that will get security updates long past Apple stopping them in 2028 | 14:02:30 |
| ragdoc | Certainly an option worthy of consideration. I guess I'll add an M-based Mac to my devices before Apple fully abandons Intel models, and once that happens, I can see myself switching ye olde MacBook to NixOS. I have no plans to sell it. | 14:15:16 |
| emily | you will probably find you like that Intel machine a lot less once you have used an Apple Silicon one 😅 | 14:16:22 |
| emily | the difference is quite dramatic | 14:16:37 |
| ragdoc | Shush please, I am trying to convince myself that I still don't need a new machine, even in light of Apple's latest lineup. 😄 | 14:30:14 |
| ragdoc | When I feel too tempted, which happens ever more often, I look at my bank account. | 14:31:48 |
 antifuchs | so, the x86_64-darwin deprecation warning... does that get issues even if you're not building for intel/darwin? I've removed all mentions that system from my flake and it still seems to get issued. | 14:45:37 |
| antifuchs | oooh, is it because any transitive package declares that it supports the platform? lol | 15:15:20 |
| emily | shouldn't be | 15:35:40 |
