The #SwiftUI .searchable() modifier has to be hands down, the most unreliable, inconsistent API to ever come out of Apple.
Not only does the behaviour of it change drastically between dot releases, it's next to impossible to get it to behave in a coherent way across all platforms.
I shouldn't install a minor OS update and have my app change like this. SwiftUI is so bad at this.
And no, I don't want to spend hours filing a feedback!
Web LLM runs the vicuna-7b Large Language Model entirely in your browser, and it’s very impressive
https://simonwillison.net/2023/Apr/16/web-llm/
Yep - confirmed with a small sample app. The issue is due to the fact that on iPhone, token searches open up a full screen ‘Picker' with a search bar on top, so you can select the tokens, or search manually. The problem is that when hitting the ‘search' button (whether you selected a token or not), it doesn't dismiss the picker to go back to your list, it just sits there.
Feedback filed: FB12105057
Anybody else notice the behaviour of .searchable(text:tokens:suggestedTokens:) changed in iOS 16.4? The old behaviour was to hide suggestions on return. Now they always display, and there doesn't seem to be a way to hide them?
I see a bunch of search stuff got deprecated in 16.4, but I'm not using any of that.
This kinda stuff breaking/changing between dot releases is such a huge time sink ☹️ #SwiftUI
Undo/Scheduled Send is one of those features that seems like it would be trivial to implement (just delay sending the message, duh!)
But delay long enough and iOS will kill your app. And if you are terminated, how do you guarantee waking up at the right time to send? There's no public API to do this.
For Big Mail I've had to get creative, ultimately relying on a cloud component.
(Apple Mail is allowed to cheat somehow, of course 🫢)
Today is #WorldDownSyndromeDay — so I would like to celebrate my beautiful brother Andy! 🎉
(and Happy Birthday for last week 🎂)
I often find myself needing to make a small edit, or perhaps just try something out quickly, and it completely kills any flow I had.
There has got to be a better way to edit a Swift Package in situ/locally than this whole song and dance?
Does anyone have a better workflow? https://developer.apple.com/documentation/xcode/editing-a-package-dependency-as-a-local-package
Polarized opinion: Dismissing AI as you would dismiss cryptos/bros is not a smart thing to do. Unlike cryptos, current AI tooling is already an integral part of some tools and workflows (including my own tools and workflows). It's there to stay and improve. Also, dismissing AI because you believe it's bad for authored content is very narrow-minded. #AI #tools
“The bank has been put under control of the federal government, making it the largest bank to fail since the 2008 financial crisis”
https://www.nytimes.com/2023/03/10/business/silicon-valley-bank-stock.html
Absolutely unbelievable that SVB could collapse in less than 24hrs (SVB being the default bank for many startups).
What will happen to funds above 250k? Extraordinary.
https://techcrunch.com/2023/03/10/silicon-valley-bank-is-being-shut-down-today-by-regulators/
Small announcement... https://www.producthunt.com/posts/gowalla
🏳️🌈 Founder / Maker
Building that new email app.
Swift and rollercoasters are my thing.
Recovering VC.