So let's check the answer(against Raycast Architecture)

[Yukaii]

Read Raycast's awesome writeup first.

What I was right about Raycast

• The observation around Raycast's open source strategy is that they manually review and prevent some security issues, while still sharing solutions. (I have a blog post that discusses Raycast in a "developer" way. The post is in Traditional Chinese)
• Raycast uses React Reconciler and JSON representation for components, which is similar to the approach taken in blast.
• Raycast uses a prebuilt Go binary with esbuild included to build the Raycast CLI, a similar approach is taken in blast-cli.

Differences (where blast could improve)

• Blast could improve by adding worker thread isolation for running extensions.
• Raycast currently uses file descriptors and JSON-RPC for IPC, which seems to not work on Windows.
• Raycast uses serial queues and buffered streams to ensure that messages arrive and leave in order.
• Raycast uses JSON patch to incrementally update the component tree.