1,220 karma · joined October 15, 2013
Whereas 2D (inkjet) printing has all of the above (minus one motor), and actually comes with a few non-trivial non-printing related expectations as well, like loading and expelling a print surface (often many in one print), optionally flipping said print surface (and this requires that ink has dried as well) and colour processing to map computer colours to real-world colours.
It might have been easier to port to because of good OS design, but running games for it will still be inefficient compared to running on actual hardware.
Yep, thanks!
At the rate we're going here the existing kernel devs will alienate any capable new blood, and Linux will eventually become Google Linux(TM) as the old guard goes into retirement and the only possible way forward is through money.
I may be wrong, but that's how I understood it, but who knows how Linus will handle any given situation. ¯\_(ツ)_/¯
> To support much-requested features like tasks, search capabilities, and offline access, we’ve started work on our next generation of Proton Calendar apps for iOS and Android, which we aim to release toward the end of 2025.
I love Proton, but there are aspects of E2EE that they haven't worked around well enough at present, in my opinion.
The biggest pain points are:
- Collaboration
- Offline access
Both of those are highly relevant for calendars, so it doesn't surprise me they didn't hit the nail on the head on the first try. Da1 Db1 Dc1 Pa1 Pb1
Da2 Db2 Dc2 Pa2 Pb2
Da3 Db3 Dc3 Pa3 Pb3
___ ___ ___ Pa4 Pb4
___ represents free space. After expansion by one disk you would logically expect something like: Da1 Db1 Dc1 Da2 Pa1 Pb1
Db2 Dc2 Da3 Db3 Pa2 Pb2
Dc3 ___ ___ ___ Pa3 Pb3
___ ___ ___ ___ Pa4 Pb4
But as I understand it it would actually expand to: Da1 Db1 Dc1 Dd1 Pa1 Pb1
Da2 Db2 Dc2 Dd2 Pa2 Pb2
Da3 Db3 Dc3 Dd3 Pa3 Pb3
___ ___ ___ ___ Pa4 Pb4
Where the Dd1-3 blocks are just wasted. Meaning by adding a new disk to the array you're only expanding free storage by 25%... So say you have 8TB disks for a total of 24TB of storage free originally, and you have 4TB free before expansion, you would have 5TB free after expansion.Please tell me I've misunderstood this, because to me it is a pretty useless implementation if I haven't.
Has anyone who sees this attempted to run Home Assistant OS in a Home Assistant Yellow "compute module board" using a Radxa CM5?
It's tempting to me because the Radxa CM5 uses a mainline kernel instead of the Broadcom-modified kernel the RPi CM4 uses, but I understand that there may be some level of work needed to be done to support the compute module + board combo, and I'm curious if that is true for the Radxa CM5 + Yellow board combo.
Or have I misunderstood anything?
Jokes aside, I just don't think the size of the device should be what decides the features that go into it. Sure, battery would be on the chopping block unless you make the device thicker, but I would have no problem with a thicker device, especially if it's otherwise the size of the 12/13 mini.
I'm confident it's possible to make a device the size of the 13 mini (slightly thicker to accommodate larger battery), with all the features of the 16 Pro, and I bet it would sell like hot cakes. I think many Pro purchasers buy Pro as a status symbol, but they don't actually want a large phone, that's my head canon for explaining why the 12/13 mini had poor sales figures, and I guess I know I'm probably wrong, but I want to be right, I'm tired of these huge phones that don't fit in my hand.
I have it in iTerm, and I don't in WezTerm.
We can blame Apple if we want, but they are not going to implement this feature for us.