The motivation/justification from the author why they believe removing lisp but adding Electron somehow sums up to being "lightweight"?
Maybe the author thought of the UX/baggage/legacy or something else when they thought about "lightweight", rather than how much memory/cpu cycles something is using? Not sure, but maybe there is a more charitable reading of it out there.
Probably none. Still I’m curious what is the authors understanding. Whether he actually thinks it is a lightweight solution or whether that’s kind of advertising phrase, like ‘blazingly fast’
There are currently no other devices meeting the update and security requirements. GrapheneOS is partnered with a major Android OEM working on making devices meeting all of those requirements along with providing official GrapheneOS support. The devices are planned for 2027 but is being announced by the OEM in March 2026 so people will know which OEM it is soon.
Good news they are making their own devices. But until then pixels are technically the most secure android devices and graphene would not be as robust on other devices.
Small correction, GrapheneOS are not making them. They are partnering with an existing large OEM to ensure one or a number of future flagship devices meets their security, privacy and support requirements.
It has been officially stated that GrapheneOS is partnered with a major Android OEM working on making devices meeting all of those requirements along with providing official GrapheneOS support. The devices are planned for 2027 but is being announced by the OEM in March 2026 so people will know which OEM it is soon.
Asahi project looks barely alive, almost abandoned. I know that their explanation of low activity is that they are being active elsewhere, supposedly pushing all their work upstream, but this has been happening for months and they don't give any reports about their progress, so I'm worried it will all die soon. And given that the project barely brought some Linux compatibility for m1 and m2 hardware and no prospects for bringing similar compatibility for newer generations - I fear it all will be kinda useless in the end.
They inarguably have slowed down, but this should be expected as the project matures. It has also inevitably now faced the time when new generations of contributors are needed as existing ones retire/ move to other projects.
How can it be mature if it can't even boot on newer MacBooks. The slowness does not seem to be due to running out of impactful work that needs to be done.
The new leadership team blogged last year that their priority would be on upstreaming their existing work.
> Our priority is kernel upstreaming. Our downstream Linux tree contains over 1000 patches required for Apple Silicon that are not yet in upstream Linux. The upstream kernel moves fast, requiring us to constantly rebase our changes on top of upstream while battling merge conflicts and regressions. Janne, Neal, and marcan have rebased our tree for years, but it is laborious with so many patches. Before adding more, we need to reduce our patch stack to remain sustainable long-term...
Where do the M3 and M4 fit in? Until upstreaming and CI progress, the core team cannot prioritize new hardware.
I think the majority of that upstreaming work (that isn't on hold until the kernal is ready for the Rust graphics driver to land) has happened and additional features like DP alt mode for USB C have been demoed.
The next update from the team should land on their blog after 6.19 ships
Activity has died down as a result of general Linux kernel developer drama, petty in-fighting, and other factors, but that doesn't change the results they did produce during their most prolific phase so far.
Without proper support from upstream like AMD, Intel, and Qualcomm (to some extent) are doing, Linux will never work as well on Apple's hardware as it does on normal hardware.
Looks believable that they are indeed the devs behind the project, but it's weird to post stuff like that to... reddit? They have a site for the project, why not post there?
Similarly, if you place enough cars near each other - you can start jumping over one and then just float around those cars indefinitely without ever touching ground and risking off getting arrested.
However, if cops or anyone else start shooting at cars - they will eventually explode and thus get you WASTED.
> It's the SI unit, what else do you want to use lol?
HVAC companies in the US exclusively use ‘tons’ to describe the amount of heat a chiller or heat pump can move. Trane, Daikin, and more all use ‘tons’ on both their marketing and engineering material.
1 ton ~= 3.56kW, but a 1-ton chiller will use ~= 1kW of electricity to remove 3.56kW of heat due to the COP of 3-4 for an air cooled chiller.
Since every cooler review took payola to pump bogus performance charts so they never settled on scientific measurements.
For those wondering, the standard measure is thermal resistance in degrees per watt, for linear systems - doubling the heat that needs to be transferred doubles the temperature difference between the sides. Adding in heat pipes, liquid convection, etc is going to make the system non-linear, so then it makes sense to talk in terms of the delta-T at given wattages. And then since there are phase-change materials, the working temperature should be specified as well. Yes, there are three scalars before you even get to things like scaling fan speed.
(I'm not a mechE so I'm sure there's something I'm missing still)
reply