Share interesting bits from the internet that you’ve recently come across and explain what inspired you about them.
Include any artwork with a reference that you liked and that’s connected with app development or design.
Share interesting bits from the internet that you’ve recently come across and explain what inspired you about them.
Include any artwork with a reference that you liked and that’s connected with app development or design.
Bringing another one from @marekfort
The type evolution Elixir is undertaking is fascinating to watch: Data evolution with set-theoretic types - Dashbit Blog
Copyleft licenses are not restrictive
https://drewdevault.com/2024/04/19/2024-04-19-Copyleft-is-not-restrictive.html
Railway started building their own infrastructure for hosting web applications and covered the journey in this blog post. It’s astounding the level of details that goes into every aspect of building that, like how cables should be positioned within the rack.
Expo is stepping into Vercel’s domain by allowing the deployment of Expo web apps to their platform. I’d have expected the opposite to happen, but Vercel seems to be very strongly focused on the web.
While SwiftPM build plugins have been underutilized (at least that’s my impression), I found this one quite cool – it basically does what our command tuist inspect implicit-imports
does, but it can warn you sooner as it’s integrated in the build process.
This is another example of a feature that we should provide to raw Xcode projects.
BTW, it builds on this other tool to detect the imports: GitHub - twostraws/Sitrep: A source code analyzer for Swift projects.
Anthony Fu, a well-known developer in the JS ecosystem, is embracing what he calls “Epoch Semantic Versioning”, to model more frequent breaking changes, as opposed to doing many minor changes and then one major version that’s a pain to migrate to.
Having gone through a painful 3-to-4 migration, and considering we often ship “soft” breaking changes, I wonder if we should adopt this at Tuist:
It’s definitely interesting! But at this point, I’m hesitant to move to a different versioning scheme that’s unknown in the community. We have done some “soft” breaking changes, primarily in the CLI API, but we have not done a breaking change of the ProjectDescription
module – and we have been committed not to break tuist generate
between minor versions (at least knowingly). So, I feel relatively good at upholding the SemVer semantics – in a large project like Tuist, some minor breaking changes in other parts of the project are somewhat unavoidable (unless one would do breaking changes often).
Not directly Swift-related, so maybe not what you’re looking for, but this recent interview/podcast from Developer Voices was fascinating to me:
It’s a discussion with Dave Lucia who built out testing infrastructure as a service for television applications. The lengths they had to go to to make it work with all the various television models was wild, and the way they built the software to automate it was equally compelling.
Thanks for sharing that one @hisaac. I’ll give it a listen. Also very cool to see Elixir in it.
haha I thought the Elixir bit might catch your eye!
SRCL, a React library to build terminal and web applications with terminal aesthetics:
@cschmatzler used the Zag library for the dropdown component in our new web design system – it’s a state machine-driven implementation of interactive components. I reckon something like this could be made into a Swift library in cases where the built-in SwiftUI components don’t cut it.
Things that people get wrong about Electron:
This mockup animation generator looks terrific: https://rotato.app/
It was used to do this mockup that I saw on Mastodon and I found it stunning.
The latter link could also be used for the artwork – the app from Marcel is beautiful.