so many unknowns...

1. macOS and Windows require installation of Xcode and Visual Studio respectively, and if in Apple's case you kinda can install these tools headlessly and choose to install only the "build tools" package, Microsoft's creature is gonna daze and confuse you with a crap-ton of checkboxes and no easy "just install whatever is minimally needed to compile my code" button, and I don't recall if there is way to install build tools on Windows through terminal.

2. what is going to be distributed? source code itself or actual binaries? and what will the security model of Glaze store be? same as extensions, "everything is open-source and undergoes Raycast's and community review"?

3. Glaze is going to come to Windows and Linux, if we trust the Q&A section at the end. what will Glaze build upon? separate frameworks and languages for each platform or something multi-platform [1] like Tauri or Kotlin Multiplatform? or are you going to copy the Raycast extension model - just run Node, expose some platform integration, and parse React render trees through "Glaze Runtime"? I've been working on a bug in Vicinae [2][3], and I've seen this model in action. it's very hard to make it perform well, but all it takes to achieve native look and feel is to just map React render trees to whatever system component OS offers. (in Vicinae's case, it's Qt. bet that it's done with SwiftUI on macOS and WinUI 3 on Windows.)

[1]: there is a difference between "cross-platform" and "multi-platform". "cross-platform" means "I behave equally across platforms and have no awareness of native look and feel" (e.g. Electron, Unity, Flutter), while "multi-platform" means "I can adapt across platforms to the degree you need" (e.g. C/C++, Rust, KMP)

[2]: https://github.com/vicinaehq/vicinae

[3]: https://github.com/vicinaehq/vicinae/pull/1158

Glaze by Raycast