4 ms·
> i am not interested in fullstack solutions because they only work for greenfield projects. i mostly build frontends for existing backends with a REST API or s
by lolinder 3y ago
> i am not interested in fullstack solutions because they only work for greenfield projects. i mostly build frontends for existing backends with a REST API or similar.
There are probably other reasons to avoid a full stack framework, but this isn't one—there's nothing to stop you from making the backend just a proxy to the existing API.
Aside from that, Amber is entirely client-side from what I can see. The Amber server is the equivalent of the Webpack or Vite dev servers, just used during the development process. It looks like Amber compiles to plain JS that runs directly in the browser.
- em-bee 3y agoyes, 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.