Search
112 results for “younata”
-
CW: Old woman yells at SwiftUI
@younata @SwiftUIisGreat I feel you and can say as a #dotnetMaui developer: currently there is NO stable ListView/CollectionView available. That’s crazy as this control is THE Main Control of almost every app.
-
@ctietze @younata Alas it is more complicated than that. #expect() predates (slightly) the introduction of move-only types. The technical constraints preventing us from relaxing the relevant argument types to ~Copyable are… complicated.
We're planning to refactor #expect() entirely in order to resolve the problem, but we likely need to wait for Borrow<T> to land among other compiler changes.
-
#LazyWeb (plus search sucks nowadays)
Any recommendations for a non-tesla-branded NACS home charger? Ideally one that doesn't have any app/internet connectivity involved.
From some quick searching, it looks like the "best" way to do that is to use a portable charger and install a NEMA 14-50 connector.
-
To be balanced, here’s why I still like Pull-To-Refresh:
1. It’s fun.
2. On small, mobile devices, it frees me from having to dedicate permanent space to something that, really, should be a fallback mechanism (all apps should automatically get pushed new data to them as soon as the backend has that data, and you should only have to manually refresh when something is broken or the person is being particularly impatient. For features that must use polling… you have a point there. Though I think the polling should be designed to be user-configurable, with sane defaults - frequent enough to get new data quickly, but respectful of things like 429s, and overall not cause/contribute to DOS attacks).
3. By this time, most people have learned this pattern and are used to it.
-
I think that pull to refresh is a bad UX pattern.
1. PTR is not discoverable. You have to know to attempt to scroll up beyond the bounds of what you’re looking at in order to use this. Many PTR implementations try to help with this by showing (part of) a loading indicator as close to when you start scrolling up as possible.
2. PTR basically forces you to layout items in chronological order, newest at the top. What if you want things laid out with newest things at the bottom, like many chat apps have? What if it doesn’t make sense to arrange things in chronological order? In Instagram (which, yeah…), PTR is not “check for any more recent posts”, but rather “give me an entirely new list of posts”, and it’s very confusing if that’s not what you’re expecting. More benignly, if someone edits a mastodon post, you won’t see that edited post at the top of your chronologically-ordered timeline when you PTR. Unless you check the notification, you won’t see the edit.
3. PTR requires you to lose your scroll position when you want to refresh. You have to scroll to the top, and then scroll beyond that in order to get new things. Many apps offer affordances for this by detecting the scroll-to-top and showing a “return to previous position” button for some amount of time after. This is still a bit of a hacky workaround compared to have a refresh button that you can tap from any scroll position, where you won’t lose your position while the refresh happens.
4. Similar to 3, most PTR implementations (e.g. using UIRefreshControl on iOS) require you to stay at the top in order to see the status of the refresh. A lot of apps also show a loading indicator in a more static area (like the navbar) in recognition of the fact that, when viewing your email, you don’t want to have to stay at the top of the list just to verify that you’ve completed a fetch. It’s frankly silly.
-
Parts to finish the cargo bike’s tube replacement arrived today, and I was very quickly able to finish the job.
The reason this was so involved is I needed to replace the rear wheel’s tube. Which is the same wheel that has a hub motor (a GMAC-10T from Grin). Which already turns this from a 5 minute job to an hour+ job. However, this time, one of the nylock bolts the motor uses to secure itself to the dropouts (in addition to a torque arm) was slipping (somehow? The threads on the axle weren’t stripped) and I couldn’t get it to the specified torque. Couldn’t find a replacement m10x1.0 nylock bolt locally, so I had to order some (from McMaster, which is expensive, but I know they have what I’m looking for + they’re not Amazon).
The bolts came today, and a couple minutes later, I had a new bolt threaded on and torqued to the correct amount. Quick ride verified that it’s correctly mounted.
This is by far the worst part of rear hub motors. They’re just an absolute pain to get on or off the bike. They offer a much better riding experience than front hubs, but replacing a tube or tire is a nightmare. I should figure out if I can go tubeless with this thing.
Edit: to be clear, this is my only complaint about this setup, and I otherwise love it. I get regenerative braking in a very powerful geared hub motor. It’s perfect for carrying and pulling cargo.
-
Parts to finish the cargo bike’s tube replacement arrived today, and I was very quickly able to finish the job.
The reason this was so involved is I needed to replace the rear wheel’s tube. Which is the same wheel that has a hub motor (a GMAC-10T from Grin). Which already turns this from a 5 minute job to an hour+ job. However, this time, one of the nylock bolts the motor uses to secure itself to the dropouts (in addition to a torque arm) was slipping (somehow? The threads on the axle weren’t stripped) and I couldn’t get it to the specified torque. Couldn’t find a replacement m10x1.0 nylock bolt locally, so I had to order some (from McMaster, which is expensive, but I know they have what I’m looking for + they’re not Amazon).
The bolts came today, and a couple minutes later, I had a new bolt threaded on and torqued to the correct amount. Quick ride verified that it’s correctly mounted.
This is by far the worst part of rear hub motors. They’re just an absolute pain to get on or off the bike. They offer a much better riding experience than front hubs, but replacing a tube or tire is a nightmare. I should figure out if I can go tubeless with this thing.
Edit: to be clear, this is my only complaint about this setup, and I otherwise love it. I get regenerative braking in a very powerful geared hub motor. It’s perfect for carrying and pulling cargo.
-
Parts to finish the cargo bike’s tube replacement arrived today, and I was very quickly able to finish the job.
The reason this was so involved is I needed to replace the rear wheel’s tube. Which is the same wheel that has a hub motor (a GMAC-10T from Grin). Which already turns this from a 5 minute job to an hour+ job. However, this time, one of the nylock bolts the motor uses to secure itself to the dropouts (in addition to a torque arm) was slipping (somehow? The threads on the axle weren’t stripped) and I couldn’t get it to the specified torque. Couldn’t find a replacement m10x1.0 nylock bolt locally, so I had to order some (from McMaster, which is expensive, but I know they have what I’m looking for + they’re not Amazon).
The bolts came today, and a couple minutes later, I had a new bolt threaded on and torqued to the correct amount. Quick ride verified that it’s correctly mounted.
This is by far the worst part of rear hub motors. They’re just an absolute pain to get on or off the bike. They offer a much better riding experience than front hubs, but replacing a tube or tire is a nightmare. I should figure out if I can go tubeless with this thing.
Edit: to be clear, this is my only complaint about this setup, and I otherwise love it. I get regenerative braking in a very powerful geared hub motor. It’s perfect for carrying and pulling cargo.
-
Parts to finish the cargo bike’s tube replacement arrived today, and I was very quickly able to finish the job.
The reason this was so involved is I needed to replace the rear wheel’s tube. Which is the same wheel that has a hub motor (a GMAC-10T from Grin). Which already turns this from a 5 minute job to an hour+ job. However, this time, one of the nylock bolts the motor uses to secure itself to the dropouts (in addition to a torque arm) was slipping (somehow? The threads on the axle weren’t stripped) and I couldn’t get it to the specified torque. Couldn’t find a replacement m10x1.0 nylock bolt locally, so I had to order some (from McMaster, which is expensive, but I know they have what I’m looking for + they’re not Amazon).
The bolts came today, and a couple minutes later, I had a new bolt threaded on and torqued to the correct amount. Quick ride verified that it’s correctly mounted.
This is by far the worst part of rear hub motors. They’re just an absolute pain to get on or off the bike. They offer a much better riding experience than front hubs, but replacing a tube or tire is a nightmare. I should figure out if I can go tubeless with this thing.
Edit: to be clear, this is my only complaint about this setup, and I otherwise love it. I get regenerative braking in a very powerful geared hub motor. It’s perfect for carrying and pulling cargo.
-
Parts to finish the cargo bike’s tube replacement arrived today, and I was very quickly able to finish the job.
The reason this was so involved is I needed to replace the rear wheel’s tube. Which is the same wheel that has a hub motor (a GMAC-10T from Grin). Which already turns this from a 5 minute job to an hour+ job. However, this time, one of the nylock bolts the motor uses to secure itself to the dropouts (in addition to a torque arm) was slipping (somehow? The threads on the axle weren’t stripped) and I couldn’t get it to the specified torque. Couldn’t find a replacement m10x1.0 nylock bolt locally, so I had to order some (from McMaster, which is expensive, but I know they have what I’m looking for + they’re not Amazon).
The bolts came today, and a couple minutes later, I had a new bolt threaded on and torqued to the correct amount. Quick ride verified that it’s correctly mounted.
This is by far the worst part of rear hub motors. They’re just an absolute pain to get on or off the bike. They offer a much better riding experience than front hubs, but replacing a tube or tire is a nightmare. I should figure out if I can go tubeless with this thing.
Edit: to be clear, this is my only complaint about this setup, and I otherwise love it. I get regenerative braking in a very powerful geared hub motor. It’s perfect for carrying and pulling cargo.
-
Today is yet another day where I’m wishing that UITableView & UICollectionView were not subclasses of UIScrollView. 🫠
-
Seeing the news that gas prices has hit yet another all-time high reminds me of my video from December, on the state and future of sustainable aviation
I think it's good, but that opinion is clearly biased.
-
CW: Old woman yells at SwiftUI
-
Interop between XCTest and Swift Testing? In the economy? It's more likely than you think.
Legitimately, I'm really excited for this. This'll enable much more consistent set of tooling that can easily be used in Swift Testing and in XCTest. It'll also make migrating from XCTest to Swift Testing much more simpler and much safer.
Go leave feedback at https://forums.swift.org/t/st-0021-targeted-interoperability-between-swift-testing-and-xctest/84965
-
CW: General Aviation drama
Last week, the AOPA (airplane owners and pilots association) board sacked now-former CEO Darren Pleasance after ~a year in the role. Claiming they reached a mutual decision driven by the fact that Pleasance lives in Bend, OR, and they want someone closer to AOPA headquarters in Maryland.
To be explicit, this entire thing is fucking bullshit. Quite frankly, Pleasance is the best CEO AOPA has had in years. He’s helped advocate for much needed change in the aviation community: pushing for unleaded fuel (yes, it’s the mid 2020s and most small aircraft still burn leaded fuel), advocating for mental health reform, use-of-ads-b reform (trying to get it so that it can’t be used for fees and such), and otherwise working to grow GA by meeting with pilots and working to address their actual needs.
This is in very stark contrast to previous CEOs who seemed much more like they were just pushing to make it so existing aviators could keep flying as they got older (and maybe shouldn’t be flying anymore?), and were otherwise uninspiring leaders.
Quite frankly, I’d like to see those in the board responsible for this change to be fired or otherwise forced to resign. Barring that, I’d like Pleasance reinstated.
Like, I am a member of AOPA solely because it’s a way to support a friend who writes for them. But I have felt much better represented by EAA (experimental aircraft association), of which I am very happily a member, because they’re actually working to do the job AOPA should also be doing.
You bet your ass I’ll be sending AOPA a letter about this bullshit.
-
Like most GA aircraft, my plane has a very loud interior. Whenever I fly, my watch fairly constantly warns me about excessive noise levels. Usually 95 db, occasionally I see 100 db. Noise cancelling headsets are basically required to be in the aircraft while the engine's running. But even then, the noise is still noticeable.
Searching on the vansairforce forums (<3 old school forums), it seems that a lot of the cause of excessive cabin noise is basically panels vibrating against each other, and adding soundproofing material (tape, foam, etc.) helps to massively reduce the noise. The problem then becomes an optimization problem of where to apply the soundproofing to maximize effect while minimizing weight.
I'm thinking of taping a bunch of cheap mics to various spots in the airplane, recording the sound amplitude to try to figure this out. I'm hoping to be able to achieve a noticeable decrease in sound levels doing this.
Of course, I'll also decrease sound levels by just adding carpet to various panels, which I want to do anyway (my cabin is spartan). But I also want to see what the combined improvement will be.
-
My friend @cyanoacry (much more active on bluesky, @cyanoacry.bluesky.social) has a blog about the kinds of thing he gets up to with his Rutan Defiant. Yesterday, he posted a highlights of 2025, which included 2 live streams while flying! Plenty of people record and publish their flights after the fact, not that many livestream them!
https://cyanoacry.substack.com/p/defiant-hijinks-dec-2025-part-2
-
I finished and released a new video on the state of electric aviation! It’s been a labor of love for the past 4 months, and I hope you all enjoy it!
If you’d like read this rather than watch a 24 minute video, I have the transcript up at https://knowledge.rachelbrindle.com/videos/electric-aviation-viability/index.html
-
I finished and released a new video on the state of electric aviation! It’s been a labor of love for the past 4 months, and I hope you all enjoy it!
If you’d like read this rather than watch a 24 minute video, I have the transcript up at https://knowledge.rachelbrindle.com/videos/electric-aviation-viability/index.html
-
I finished and released a new video on the state of electric aviation! It’s been a labor of love for the past 4 months, and I hope you all enjoy it!
If you’d like read this rather than watch a 24 minute video, I have the transcript up at https://knowledge.rachelbrindle.com/videos/electric-aviation-viability/index.html
-
After Swift Testing added support for image attachments on apple platforms and windows platforms (insert 90s-era M$ insult here), they had realized they really should consolidate the different AttachableAs${PLATFORM_SPECIFIC_IMAGE_TYPE} protocols down into just a single AttachableAsImage protocol that each platform needs to conform to.
This is just large enough of a change to require evolution review, which I volunteered to manage! If you have thoughts, please add them to https://forums.swift.org/t/st-0017-consolidate-swift-testing-s-image-attachments-api-across-platforms/82815 (or message me on the swift forums).
The review period started some 30 minutes ago and runs through the end of October 30th!
-
A couple weeks ago, I gave a talk at @omt_conf on What's New in Testing. That talk was recorded, but while I wait for it to be edited and published, I published an edited (and updated!) version of my speaker notes from that talk.
There's a lot new in testing since last year. I'm still surprised there wasn't a WWDC video about all the new things you can do.
https://rachelbrindle.com/2025/06/26/whats-new-in-testing-swift-6-2/
-
A director at work reached out to me, asking if I was interested in giving a talk promoting the use of GitHub copilot (I was asked because I had been enrolled in an optional GitHub copilot training series, even though I never attended any of the trainings).
I am, explicitly anti-llm, and I said as much, citing quality, plagiarism, their resource usage, etc.
Interestingly, this person said he found this perspective of interest to him because he hadn’t heard of these concerns before. He said he’d schedule time for us to go over this more in-depth. I hope this was something said in good faith.Now, lazyweb, what sources do you have for a lot of these concerns and claims? Like, where does the claim that “a 100-200 word response from ChatGPT uses about 2 water bottles of water” come from?
That Microsoft paper about how llms make us think less critically is also great, and I already have a link to that. -
Been trying to receive NOAA APT satellite signals for the past ~week using an rtl-sdr dongle & a basic V-dipole. Yesterday, I ordered and received an LNA to boost the signal. Combined with a pass of NOAA-15 that basically went directly overhead, I was able to pick up this (composite) image. Which did not decode correctly, because clouds do not look like that (I didn't save the raw signal).
But I managed to get a signal, which is progress and very exciting to see!
Sometime down the road I'll build a QFH (a helical antenna) which should dramatically improve the signal quality.
-
This new water bottle I got as some pretty cool conference swag from #OMTConf (where bitrise paid local artists to make art on the bottles!) fell out of my bike while riding, and I ran it over, flattening it.
I’m kinda sad about it because it was a really cool design. At least it was in a position where the design was mostly saved, but still. Not really useful for anything except as a display piece.
-
I’ll be speaking at #OMTConf tomorrow (Tuesday June 11) at 2:30 pm pacific on Testing Swift Concurrency and SwiftUI!
I’ll also be at their tent Thursday morning to discuss testing until noon pacific time!
It’s at the Residence Inn on Main Street in Cupertino, tickets are free. Check them out at https://omt-conf.com
And yes, it’ll be recorded.
Looking forward to meeting folks tomorrow!
-
For my #OMTConf talk, I was given feedback in a practice run that my pre-recorded demos were too fast paced with almost no pausing for the audience to understand the points I'm trying to make. The audience won't have the ability to press pause or go back if they miss something.
So, I'm re-editing them to add at least a second of delay after each line (and of course extending the subtitles to last through the silence), and wow. That has significantly improved the experience of watching them.
-
Woo! I’m so excited to announce I’ll be presenting at One More Thing conf during WWDC week!
I’ll be talking about testing, and specifically about testing SwiftUI and Swift concurrency!
I’ll also be a “floating expert” there on testing in general.
Hope to see you there!
-
I'm proud to announce that the require dsl has shipped in Nimble 13.1.0!
I've found this to be a very natural way to express "I need this assertion to pass before the test continues", in a dsl that's very familiar to users (it works very similar to Nimble's expect dsl).
I'm looking forward to the amount of duplicated code in test that this will remove.
https://github.com/Quick/Nimble/releases/tag/v13.1.0
#SwiftLang #swift #iosDevelopment #iosDev #nimble #UnitTesting
-
I've been working to add require to Nimble, an assertion which throws if it fails, and returns the result of the expression asserted on. Inspired by the Require macro from swift-testing.
If you're interested, I'd love feedback! The linked PR works, but I'm still dogfooding it and it overall needs to be cleaned up (and documented 😳).
https://github.com/Quick/Nimble/pull/1103
#SwiftLang #swift #iosDevelopment #iosDev #nimble #UnitTesting