… or you can just close your eyes, and move your face around. The device will not unlock if you're not looking at it and after 3 or 4 tries will ask for the password.
Right, there’s a multitude of ways to trigger a passcode requirement, but the point here is quick/immediate procedures that can be learned into muscle memory.
I remember writing apps for PalmOS (long time ago) distributors like PalmGear took over 60% from international developers like me, plus they held your earnings until you hit a minimum payout threshold. Add bank fees on top of that, and it was basically not worth developing for the platform. 30% felt like a godsend in comparison. (I'm not defending the Apple / Google tax)
I do something similar. Over 90% of my YouTube consumption is with Alfred workflows which use mpv and yt-dlp under the hood. I just press a keyboard shortcut and the frontmost tab closes in the browser and starts playing in mpv.
The remaining percentage is still annoying, as it happens from the phone.
why is your tool so hard to use on ios? the website instructions say you need a companion siri shortcut, but no where is there actually a shortcut listed.
combing and coming through searches and reddit all comes up with non-working siri shortcuts that complain that the url is not found.
This kind of thinking is exactly why Electron-based apps end up consuming 4% CPU while doing nothing, and why some games use 100% CPU just sitting in their menus.
Why would you expect users to manage threads, processors, and system resources themselves?
I agree with you, but I wonder what the incentive is for developers to use resources responsibly. Is it just that users will uninstall apps that drain their battery? Or are there penalties imposed by the OS on developers who refuse to play nicely?
At a minimum this is done diligently for Apple-written software.
For foreground apps like electron actually this wouldn’t do anything because you generally want it to be foreground. However, various extensions probably should use a different QoS level because responsiveness is better (eg code indexing, builds, etc).
The incentive is a better user experience and a lot of times software engineers end up using the software they’re building so the self interest incentive exists. And developers also exist who view it as a craft and push themselves to write better software.
If they'd drastically improved their tooling then yes.
But sadly it's not that easy to create a statically liked binary in swift. The last time i did it it also included the whole runtime, and the resulting "hello world" binary was 50mb large. Annoying at least.
For years I wished they got their stuff together, but at this point I'd be very suprised. They probably have too much technical dept already due to the support of XXX edge cases Apple need for iOS/MacOS development.
In this thread on Swift for AWS Lambda, a dev gets a Linux static build to 5.9 megabytes:
"Then, I stripped it and it's now 5.9Mb. That's an impressive 86% reduction.
Given that musl libc.a is 2.4Mb and libc++.a is 10Mb, I find that 5.9Mb for an executable that contains both libc and the Swift runtime is not that bad :-)"
Good that they work on it. And the efforts to refactor foundation into smaller modules go in the same direction.
I continue to root for them but they need so many improvments to be a realistic alternative to python/typescript/go/java for regular backend development.
At least in my field where we need to sure that other developers can continue the development without much hassle.
Just as an example, with those languages it's almost trivial to setup a basic projekt with dependencies. In swift however, it takes careful reading ot the swift package manager documentation to understand their concept of "products", "targets", etc.
And I'm pretty sure i'd have to start from zero when i use swift for the advent of code in a few days.
There are many problems with devepdencies in Python, or package.json/gradle files. But at least they are (almost) foolproof to get started.
I hope this helps people to consider Swift 6 as a viable option for server-side development, since it offers many of the modern safety features of Rust, including simpler memory management through ARC, compared to Rust’s more complex ownership system and more predictable than Go's garbage collector.
I'd love to use Swift on Cloudflare Workers, but SwiftWASM doesn't seem production ready whereas Rust just works (mostly) on workers. Swift on AWS Lambda looks promising though.
Custom controls are the enshittification of the <video> tag. IMHO there's no custom video component that allows the user to control volume, picture-in-picture, AirPlay, control speed and scrubbing better than the standard controls, especially on mobile.
Here's a great example, no need for a custom-made refine and Map component document because with refine's headless approach, you can use Map components as you please.
