Viewing profile — mattiemass
mattiemass
HN member- Joined
- Sat, May 24, 2014, 8:59 PM UTC
- HN karma
- 2,069
- Public activity
- 318 items
- HN profile
- View on Hacker News ↗
About mattiemass
No profile information was provided.
Recent public activity
-
comment
Comment #37703812
I have found myself, many times, in exactly the same situation. I think a concurrency-compatible queue is basically essential for many kinds of pretty boring situations. I made one…
- story
-
comment
Comment #37466242
These tests are being extracted from an editor project I work on. The tests themselves use the OSSignpost API for high-precision measurements combined with the XCText infrastructur…
-
comment
Comment #37464785
Author here. I'm not entirely sure why this project would be of interest, but I noticed it here so figured I'd provide a little more context. The test suite is small, and there are…
- story
- story
-
comment
Comment #33420782
I'm truly sorry to hear that you are disappointed. And I really do get it! The full story is long, but I can sum it up with: our number one request, by far, is support for more lan…
-
comment
Comment #33414781
Same thing on macOS. The containing app does not need to be running for the extensions to be active. You are right that the extension bundle can only be used by this mechanism, but…
-
comment
Comment #33413591
The only reason I was able to figure out how to use ExtensionKit at all was because of a chance encounter with an Apple engineer during WWDC that provided some needed information. …
-
comment
Comment #33413281
Practically speaking, that's still basically an SDK. It's all over XPC, but the interface still needs to be defined.
-
comment
Comment #33413159
(author of that quoted blog post here). You are correct, there's nothing new about apps offering plugins/extension systems. What's new here is: this works across sandboxed apps, su…
-
comment
Comment #33412968
I'm sorry it's working so poorly for you. 2.0 has some performance issues that do make it seem more like slow-open in a number of situations. We're working on it.
-
comment
Comment #33412846
Honestly, dropping v11 for 2.0 was a really tough call. Adopting ExtensionKit, and getting that out the door right when v13 shipped was difficult, but that was the goal we set out …
-
comment
Comment #33412769
That's more or less exactly what we've done. Our SDK does have support for LSP. But, unfortunately those extensions still need to be made. Or are you talking about a generic LSP ex…
-
comment
Comment #33412651
We did start off with just Go. After doing a bunch of infrastructural work, we added another, Ruby. We've just finished generalizing this, in a way that both more 1st- and 3rd-part…
-
comment
Comment #33412601
You did not. Aside from Rust and Swift, all the added languages are preliminary. A minimal extension is required to, for example, connect Chime up to an LSP server to get semantic …
-
comment
Comment #33330559
Thank you so much! The limited language selection was definitely a problem. Go, Ruby, Swift, and Rust extensions are all available today. Go and Ruby aren't open-sourced yet, but w…
-
comment
Comment #33330061
thank you so much!
- story
- story
- story
-
comment
Comment #31359905
I sincerely appreciate you saying this! The open source work we've done is something I particularly enjoy. Our work with LSP has been a blast, and I know that there are actually ot…
- story
- story
- story