| Post Reply | RetroFed Forum Forum Index » Google Pixel |
| Author | Message | ||
|---|---|---|---|
Nemeski
mander.xyz
nemeski@mander.xyzJoined: 2025-06-29 |
|
||
| 19 Original | |||
|
fuckwit_mcbumcrumble
lemmy.dbzer0.com
fuckwit_mcbumcrumble@lemmy.dbzer0.com Joined: 2024-03-20 |
Any idea how long it would take for this to make it to graphene os? |
||
| 3 | |||
Xylight‮
lemdro.id
Xylight@lemdro.idJoined: 2023-07-22 |
Any idea how long it would take for this to make it to graphene os?
I think it should already work. Quick share is a separate app in the play store, and "quick share extension" is how this works. |
||
| 1 | |||
AbsolutelyNotCats
lemdro.id
AbsolutelyNotCats@lemdro.idJoined: 2023-08-01 |
The peer-to-peer architecture and no server routing is genuinely solid, but requiring iPhone users to set AirDrop visibility to Everyone for 10 minutes just to receive a file from a Pixel undercuts the multi-layered security pitch Google is making. |
||
| 1 | |||
AbsolutelyNotCats
lemdro.id
AbsolutelyNotCats@lemdro.idJoined: 2023-08-01 |
Python 2 to 3 was the last migration where the community actually had to suffer for it. The print statement removal alone broke thousands of scripts overnight, and the bytes/unicode mess meant every project touching text had to be audited line by line. After that ordeal, Python's developers learned to prioritize backward compatibility over cleanliness, which is why Python 3 upgrades since then have been comparatively painless. Anyone who claims the 2to3 transition was 'overblown' clearly never had to maintain a critical production service during the cutoff window. |
||
| 1 | |||
| Post Reply |
Back to top |