yes, amber is entirely clientside. that is what makes it interesting. but the smalltalk web frameworks are mostly backend frameworks designed to run in pharo or

yes, amber is entirely clientside. that is what makes it interesting. but the smalltalk web frameworks are mostly backend frameworks designed to run in pharo or squeak, which means they feel way to bulky and not suited for an SPA web frontend were i want to dynamically update the DOM when data changes instead of generating a whole new page to send to the browser like traditional web frameworks. there's nothing to stop you from making the backend just a proxy to the existing API what is stopping me is that this forces me to run two backends and an additional layer of indirection.