Matt Massicotte

swift ⌨️, outdoors 🏔, justice ⚖️ | @chimehq, prev: @crashlytics, @apple | find me at and @[email protected]

[Matt Massicotte @mattie]

I expect I'm going to lose access to this handle soon, so I just wanted to quickly say I miss you all and I'd love to stay connected. Find me!

[Matt Massicotte @mattie]

@FeifanZ I'm afraid DMs are broken for me. Do you have any other services you use for communication?

[Matt Massicotte @mattie]

@FeifanZ hello!

Stumbled onto your post about SourceKit-LSP. Super good! I actually know what's up with the OS-identification issue. You have to pass along user (not app!) environment variables.

I also work a lot on LSP stuff! I wonder if there's a way we might collaborate?

[Matt Massicotte @mattie]

@FeifanZ I maintain this library: https://t.co/kWtPzc890h

User envs (what a user has defined in their shell) vs what a standard macOS app gets when launched. Matters for most language servers.

And what you are building is super cool!

[Matt Massicotte @mattie]

@Richthealgoritm I never use this site anymore, but I just had to come to tell you that I absolutely *love* your channel!

(And, your linktree link is broken on YouTube - extra chars at the end)

[Matt Massicotte @mattie]

@Frizlab hello! Still enjoying your FSEventsWrapper library. I opened a PR recently to being to address some Swift concurrency compatibility issues. Just wanted to make sure you saw it - absolutely no pressure though. Please take your time.

[Matt Massicotte @mattie]

@kuba_suder @msmialko Yeah it’s bizarre how it’s being exposed on iOS. It even has implementations for UIKit, but they are marked unavailable. Clearly something went wrong at the last minute. I think this explains why there was no WWDC session too.

[Matt Massicotte @mattie]

@kuba_suder @msmialko (Sorry not around here much)

From what I can tell, it was supposed to make it to iOS but was pulled. Currently still not enough pieces available to be usable I’m afraid.

[Matt Massicotte @mattie]

@_nghiatran @github I know that you are focusing on apps specifically, but have you looked at https://t.co/BQDHaMGhgy? They do fantastic work!

[Matt Massicotte @mattie]

@thecoolwinter Forks yes, but even *linking* against GPL code means you must be GPL. It’s designed to ensure that if you use it at all, you must also use the same license. LGPL is a little more permissive.

[Matt Massicotte @mattie]

@thecoolwinter You mean GPL? Number one reason has to be the virality. That’s definitely while I don’t like it.

[Matt Massicotte @mattie]

@kylnew @MargoChepiga Any 🐘 accounts I can link to over there?

[Matt Massicotte @mattie]

@isEqualToDan 😓

[Matt Massicotte @mattie]

@nsphin White oak is my favorite material!!

[Matt Massicotte @mattie]

@krzyzanowskim Now, or course it is *better* to get it right without help. But there are lots of ways to send signals along the way so if you are unable to, you can still potentially get through.

[Matt Massicotte @mattie]

@krzyzanowskim I’ve conducted > 100 of these kinds of interviews between Apple and Twitter. Apple even wanted pass/fail but that just isn’t how people work. Many times feedback would be basically “didn’t solve it but … I think they are still good”

[Matt Massicotte @mattie]

@tjeerdintveen If you do write about it, I’d love to read more about the trade offs. My understanding is generics are always preferred for perf and safety, but erasure is useful for API boundaries (and maybe other things too!)

[Matt Massicotte @mattie]

@tjeerdintveen Yeah that’s how I understood it. I was just confused because I do not think of it as new/old at all, but just a much more convenient way to get type erasure if I need it.