![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Funnily enough, that person you mentioned who discovered that was marcan, one of the Asahi lead developers.
Funnily enough, that person you mentioned who discovered that was marcan, one of the Asahi lead developers.
there is no chance you would get back to the Intel system and plug it in every 2 hours.
don’t be irrealistic. most laptops in the Macbook price range will have 8 hours of usage in low consumption mode or around 6 or 5 if you need more power.
While I completely agree on the repairability front, which is really quite unfortunate and quite frankly a shame (at least iPhones have been getting more repairable, silver lining I guess? damned need for neverending profits), it’s just… non unrealistic.
That being said, unified memory kind of sucks but it’s still understandable due to the advantages it brings, and fixed-in-place main storage that also stores the OS is just plain shitty. It’ll render all these devices unusable once that SSD gives out.
Anyhow, off the tangent again: I have Stats installed for general system monitoring, as well as AlDente to limit charge to 80% of maximum battery capacity. All that to say, by now after around 1.5 years of owning the M2 MacBook Air (which I’ve been waiting for to buy/to release since late 2019, btw), I know pretty well which wattages to expect and can gauge its power usage pretty well.
I’ll try to give a generalized rundown:
Given the spec sheet’s 52 Wh battery, you can draw your own conclusions about the actual runtime of this thing by simple division. I leave it mostly plugged in to preserve the battery for when it becomes a couch laptop in around 5-8 years, so I can’t actually testify on that yet, I just know the numbers.
I didn’t mean for this to come off as fanboi-y as it did now. I also really want to support Framework, but recommending it universally from my great-aunt to my colleagues is not as easy as it is with the MacBook. Given they’re a company probably 1,000 times smaller than Apple, what they’re doing is still tremendously impressive, but in all honesty, I don’t see myself leaving ARM architecture anytime soon. It’s just too damn efficient.
*At least for my typical usage, which will be browser with far too many tabs and windows open + a few shell sessions + a (may or may not be shell) text editor, sometimes full-fledged IDE, but mostly just text editors with plugins.
zshenv
’s selling point isn’t necessarily that your typical functions are available across scripts (though that can be neat, too – I sourcealiasrc
as well as anutils
script file in my shell config) – it’s that it’s there for non-interactive shells too, whereaszprofile
is only applied for login shells (andzshrc
only for interactive ones).So for example, I could open a command in my editor of choice (Helix’s
:sh
for me), and if I define stuff using thezshenv
, all of my aliases etc. are right there. I just have to avoid naming conflicts for script function names if it’s the default shell, but that’s pretty easily done.