6 ms·
Best thing about this is that it is available for most of the major platforms with an easy to use GUI. iOS app is excellent. Some important bugs to beware: On
by ComputerGuru 3y ago
Best thing about this is that it is available for most of the major platforms with an easy to use GUI. iOS app is excellent.
Some important bugs to beware:
On Windows having the LocalSend app running with the Window visible (after a receive?) prevents the system from sleeping. On Linux, it does the same even if the window isn’t showing. On Linux, having the LocalSend window visible and idle consumes an insane amount of cpu with the desktop window manager constantly refreshing damages. On Windows, the app (with the “startup minimized” option checked) if configured to launch at startup will often show the window anyway (not that you want it running in the background given the sleep issues).
- arvindkumarc 3y agoYes. Love this cross platform, non proprietary software for local file sharing.
- ahmedfromtunis 3y agoThanks for the heads-up. I just installed it and it's the most most hassle-free experience I ever had with this type of apps. My only gripe with it is that I need the receiving device awake and the app on the foreground (at least on android) for it to work. Even with the quick save option activated. I wish quick share (né nearby share) was available on linux (even if via chrome).
- grishka 3y ago> I wish quick share (né nearby share) was available on linux (even if via chrome). I made NearDrop, which is a macOS implementation of Nearby Share: https://github.com/grishka/NearDrop https://github.com/grishka/NearDrop And of course, someone tried to reimplement it for other OSes: https://github.com/PlutoHDDev/CrossDrop https://github.com/PlutoHDDev/CrossDrop
- ahmedfromtunis 3y agoI'll give them a spin, thanks for the links!
- harikb 3y ago> having the LocalSend window visible and idle consumes an insane amount of cpu with the desktop window manager so Flutter :)
- Alifatisk 3y agoAny backstory to this?
- harikb 3y agoLet me see if I can explain it - These "declarative" UI frameworks work very different from any UI frameworks in the past. They (theoretically) rebuild the data structures backing the current view of the UI and do that 60+ frames per second. Good thing is that there is very little chance of data-out-of-sync-with-UI kind of bugs. But the bad part is that tons and tons of alloc/dealloc and literally the code is executing all the time. Now in practice, it is not all that bad. They have a magical garbage collector that makes is all better. Every release it just slightly better, but I can't help think that they are solving a problem they created to begin with. But I might be too old and may be the productivity is worth it. This is in addition to the fact that none of the widgets are truly native. The "code" is native, but the UI is not. Even react-native apps might be this way, but they at least use Safari/webkit widgets, if not truly native iOS/Android widgets.
- Alifatisk 3y ago> But the bad part is that tons and tons of alloc/dealloc and literally the code is executing all the time. Considering what you said, it's quite impressive that Flutter is able to perform this well and render thousands of widgets per second. https://youtu.be/pD38Yyz7N2E?si=7jTaQdX9ln37_fHR&t=3052 https://youtu.be/pD38Yyz7N2E?si=7jTaQdX9ln37_fHR&t=3052
- remram 3y agoThousands is supposed to be a lot? Also what if I want to run other apps at the same time? They better not have too many widgets of their own?
- sunnybeetroot 3y agoAny chance you could raise an issue?
- kokizzu5 3y agojust disable the animation, 4-7-14% if animation enabled, 0-2-3% with animation disabled.