So we got some questions.
The most specific one is about your rules. Are they open source? People can grab them and get inspired or use them?
They are not open source because they are project specific.
They are pretty simple. I might share some after when I get my laptop. Didn't take it with me here. Yeah, I try to-- the thing is, people use defaults for source tree, for SwiftLint, stuff like that. But those tools really shine when you take your project needs. And the way I build those rules is really simple. If I see the same comment in my PRs, it means it should be automated. If it's the same pattern over and over again, If you have to point out, oh, this is not how we do things, you might not deprecate the API, because for some reason, it might still be needed. But you can write a Swift linter role so that the next time it happens, you don't have to be the bad guy. That's the thing. The linters become the bad guy. I don't need to be the one saying, well, this doesn't follow our best practices. I can just make it-- as a team, we decided this is best practice, and the bot is the bad, bad thing, not me. We have a question from Woody. And what's the future of Sorcery with Swift macros?
I'm not worried.
- Okay, nice.
Very specific question as well. How does Pulse compare to the OS log feature?
- US what, sorry?
- OS log.
- Oh yeah, I mean, it's much more nicer.
The other thing is it's designed for networking, so you get a lot of custom UI with a lot of details. It's just better designed for those kind of stuff. OS log is too general purpose, so that's obviously just gonna be very raw logs instead of having this nice and polished experience.
- Performance wise?
- I mean OS lock is gonna be faster because it's using static strings and stuff.
- Thank you Christophe.
- Thank you.