Yep, this falls into stuff we more or less have agreement on as far as how we get there. There is a long list of challenges ahead which we haven't wanted to address because the number one way we fail is losing touch with the basic needs of running this single DEV instance.
In the past few weeks, mostly since @molly_struve
and @jacobherrington
joined the core team to bring relevant experience and new perspective, we've begun truly thinking through some of what you're describing. But we're giving ourselves a long leash in terms of eventually making this codebase appropriately agnostic and technically efficient.
We'd eventually like to provide a few managed options and do support for the ecosystem alongside continuing to thoughtfully monetize this and any other networks we spin up to operate ourselves.
Yep, this falls into stuff we more or less have agreement on as far as how we get there. There is a long list of challenges ahead which we haven't wanted to address because the number one way we fail is losing touch with the basic needs of running this single DEV instance.
In the past few weeks, mostly since @molly_struve and @jacobherrington joined the core team to bring relevant experience and new perspective, we've begun truly thinking through some of what you're describing. But we're giving ourselves a long leash in terms of eventually making this codebase appropriately agnostic and technically efficient.
We'd eventually like to provide a few managed options and do support for the ecosystem alongside continuing to thoughtfully monetize this and any other networks we spin up to operate ourselves.
I do feel I should say sorry to you Ben. You've probably heard my complaint about modularizing one too many times now.