With SST v3 you're still specifying specific resources in code though, so at implementation time you have to decide which underlying infra you want to use. E.g. will you use Lambda or Fargate, this means using different SST components.
How Encore is different is that you only declare the semantics in code, and then at deploy you decide which infra to use depending on your needs for each environment. Similarly, you can choose at deploy time if you want to colocate services or deploy as separate processes, with no refactoring needed.
Founder here. Sorry to hear you're not happy with the support, appreciate the transparent feedback. We do our best to be responsive for community support requests, but sometimes we can't keep up with the volume. FWIW we offer paid private support if you feel you really need super fast response.
Thanks!
Leap doesn't currently use an MCP, but it we've build the same sort of logic for reading information from the Encore app's runtime into the Leap application itself. We found it was more controllable and token efficient.
yeah, i really like the achievement system for the interactive demos. it's a fun way to make sure readers are actually engaging with the lesson, and understanding its points.
Thank you so much. I still have a way to go. People who struggle with low contrast will struggle with the default colour scheme, for example. But I'm trying to make progress with every new post <3
