Do we want some sort of low-level "escape hatch" primitive for letting projects install custom tools that don't install through dependencies. Use cases include things like gcc, Java, phantom, headless chrome, etc. You might argue that this can be solved through other means, including shoehorning them into dependencies or system-level configuration management (e.g. images). On the other hand, low-level escape hatches tend to relieve a lot of pressure in the design of a layered system, making it possible for users to solve their problems without needing to lobby for the addition of lots of special cases at the higher layers.
In thinking about escape hatches we'll also want to figure out what underlying parts of Notion we want to expose to the API, e.g. caching and tool version management.
Do we want some sort of low-level "escape hatch" primitive for letting projects install custom tools that don't install through dependencies. Use cases include things like gcc, Java, phantom, headless chrome, etc. You might argue that this can be solved through other means, including shoehorning them into dependencies or system-level configuration management (e.g. images). On the other hand, low-level escape hatches tend to relieve a lot of pressure in the design of a layered system, making it possible for users to solve their problems without needing to lobby for the addition of lots of special cases at the higher layers.
In thinking about escape hatches we'll also want to figure out what underlying parts of Notion we want to expose to the API, e.g. caching and tool version management.