>> Grouped aliases/imports/requires are a mis-feature in my view. They save a few characters when typing but they complicate searching for module uses and refactoring.
> Totally agree with this. I prefer to not use aliases most of the time, or to explicitly list out each module path separately if they are too long to fit inline. All preferences though.
recode[0] has a formatter plugin that reformats grouped alias/import/requires
There’s an automation that’s triggered when you receive an email. Coupled with Mail’s “Send later” feature in iOS 16 and some parsing, you can send messages at any time you want.
I bought a burrito during lockdown in the UK, but it was such a miserable experience.
The menu wasn’t particularly intuitive, and took me a few minutes to pick out what I wanted — then I was greeted with a registration page. Email, password, phone, address, you name it, they wanted _everything_ — I only wanted to collect. They didn’t take mobile wallet payments either! Manual card entry!
I feel like the restaurant recognised they had a problem, but contracted out a solution to the lowest bidder that actively went out of their way to design the worst UX.
In the end I actually went ahead and built a platform that’s not user hostile.
Im going to rewrite the landing page and do another round of marketing soon. The page that I wrote in an afternoon is far too negative in hindsight. It needs a positive spin.
The web experience has been reduced to an indexer. Following the HN link, there's an option to open the app store, or navigate to the subreddit's index. Even choosing to navigate to the index and open a post directly displays the same prompt.
My expectations mirror your own, but a few of Jeff's thoughts imply that they won't take this path:
> App bars become UINavigationControllers. Standard controls just need light branded touches. Lists can align with modern UITableView and list-based collection view APIs. Menus are just UIMenus.
> And the best code is often no code :)
> The time we're saving not building custom code is now invested in the long [...]
AirPods using lightning is one of the more obnoxious Apple decisions in the last 5 years or so. Even long after the iPhone has moved on to USB-C or no port at all, your AirPods Max will still force you to charge with Lightning.
I guess it's a good thing that everybody's AirPods and AirPods Pro are going to be dead in a couple of years, so if they update them to use USB-C they won't hang around too long. Thanks, poor battery longevity!
Apple took a lot of grief for retiring the 30 pin connector and USB-C didn't yet exist when they did so. At the time I recall Apple saying they would support Lightning for 10 years. That was 9 years ago. It makes sense that the AirPods would use the same connector as the iPhone - imagine the mess that would be if they didn't! Anyway, since next year is the 10 year anniversary of switching to Lightning I suspect that's when they're going to transition all the iDevices (except Watch) to USB-C.
You're probably right. I know I don't use the wire to charge my phone any longer. Also eliminates a port which should improve the device's water resistance.
The lightning ecosystem is that a huge percentage of people in the united states expect their phones, and their friends' phones, to charge over lightning. This is a convenience for them. I'm not really defending it, since usb-C would be much easier for me, but I can understand why the transition would be painful for a lot of average users.
> Totally agree with this. I prefer to not use aliases most of the time, or to explicitly list out each module path separately if they are too long to fit inline. All preferences though.
recode[0] has a formatter plugin that reformats grouped alias/import/requires
[0] https://github.com/hrzndhrn/recode