Tom MacWright
@macwright.com
7 months ago i'll try to collect some notes, i've definitely relying on ~5 people who have documented their processes super well for a lot of guidance
💬 0
♻️ 0
❤️ 2
i'll try to collect some notes, i've definitely relying on ~5 people who have documented their processes super well for a lot of guidance
so far i've gotten rabbit holed into: ecopak, x-pac, dyneema and other high-tech fabrics. paracord and whether other cords are better. sewing technique and zipper sewing. and more. also mocked this up in cad.
spent today so far crafting a frame bag for my new bike - cardboard mockup, the actual thing will be constructed of ecopak & cordura. attempting to keep the news off.
I absolutely agree but part of my brain learned that being extra productive needs the “big headphones” 🥲
I’m so tempted to do the same but I like being untethered and freeeeeeee
> Low battery, please recharge headset. Power off. RIP my flow
An Atuin contributor is proposing i18n support.
If that's something you'd like to see in Atuin, please chime in! Even better if you'd be able to contribute translations
forum.atuin.sh/t/internatio...
deno's Worker abstraction is roughly an isolate and is what we used in our v3 runtime. our version of it exhibited memory leaks and you couldn't do things like bound the cpu usage per isolate. cf workers etc probably have a much more powerful tool for running isolates blog.val.town/blog/first-f...
(based only on outside knowledge of deno deploy) - afaict they're running a subprocess in a cgroup per account as an additional level of isolation beyond v8 isolates: deno.com/blog/subhost...
Yeah, SwiftPM features often work well – until you start using the Xcode integration in a large app :/ And your only option is then to file a radar and hope for the best. Xcode being closed source and littered with bugs is a strain on the whole Swift(PM) community.
That does sound like the perfect case! The swift-openapi-generator (github.com/apple/swift-...) does exactly that if that helps. Sort of surprised that there's no similar open source solution for GraphQL – but if there's not, I think there would definitely be interest in the community.
lina khan appears to have dropped this report just days before the next administration takes over. she's doing the work, regardless of how bad the situation is looking. i wish we had more characters like this in gov.
We're working on some documentation for this but in the meanwhile you can take a look at this test case: github.com/Effect-TS/ef...
Thanks a lot for your kind words! Much appreciated! Still trying to figure out how to be a good podcast host! 🙏
I definitely feel tooling is likely a part of the reason why the adoption has been relatively low. Curious what you wanted to build with the build plugin? 🙂
Or are build plugins just better suited for more robust cases like Swift OpenAPI generator and for the rest, build phases are fine? Or maybe it's just a matter of time for build plugins to pick up. I don't have answers, just questions 😅
I think that's partly right. But I still would have expected more folks to replace their build phases with build plugins. However, build phases "feel" more lightweight and usually are enough to do the job at hand.
Is tooling lacking a bit? (Case in point: bsky.app/profile/gits...)
I found this cool build plugin that ensures one can't import implicit dependencies – a common issue that makes builds less deterministic and is especially painful at scale: github.com/Nikoloutsos/...
And I wondered why we haven't seen more packages like this.
I wonder why #SwiftPM build plugins have not gained broader usage (at least that's my impression)? Do they slow build times, are they too clunky to develop, something else?
As part of our Swift Stories newsletter, we do small interviews with folks from the Swift community (and beyond). Do you have suggestions for who we should interview?
Let us know on our online forum (community.tuist.dev/t/worthy-fiv...) or in the thread below 👇