"No way to prevent this" say users of only language where this regularly happens
| Love | Swift and Rust |
| Hate | Flaky tests |
| Love | Swift and Rust |
| Hate | Flaky tests |
"No way to prevent this" say users of only language where this regularly happens
@overcastfm Hi there! I'm still having my playlists get out of order a dozen or so times per day. Is that something that's on your radar?
My maybe-wrong observation is that episodes that should be sorted last (because they're new and the playlist is oldest-to-newest) get “lumped in" with new episodes that are correctly sorted first (because they're new and prioritized) if they get added at roughly the same time. (Re-setting the sort rule fixes it temporarily)
I subscribe to NPR's and BBC's hourly news feeds, which (if I'm right) exacerbates this problem quite badly
@overcastfm I really appreciate how fast you're squashing these bugs :)
Also very excited to hear that the "speedometer" will be making a comeback. For whatever reason, I love that thing!
@iandundas
I got caught by this recently, but I didn't realize that NSLog/OSLog would still appear, so I just went full fuck-it and started logging to a random label onscreen.
Good to know there's a less stupid thing I could've done
Friends on the Gulf Coast—I want to do a Swift Platforms meetup. I don’t know if anyone is out there who wants it, but can’t hurt to try. Whether you’re a day one beginner or seasoned pro, it could be a great time. The area I can realistically target is Gulfport MS - Pensacola FL.
Please share for visibility!
Objective-C professionals around the world, I summen ye 🗺️
Is there not a way to annotate an Objective-C method that returns a Foundation type like NSString to avoid automatic bridging to Swift.String?
I really want to stay in NSString-land.
(Actually, I probably even want to keep fiddling with an NSMutableString *as* a mutable string)