Hi,
A recent KrabArena benchmark comparison between Astro and Next.js for dashboard-like applications showed Astro often leading in areas such as performance and build output size.
Given that FullAgent/fulling includes a dashboard component (as indicated by the dashboard entrypoint and potentially code within app/), and typically uses a dockerfile for build and deployment, these potential improvements might be relevant for optimizing the project's frontend delivery.
This is not a suggestion for a full rewrite, but rather an optional, small investigation. One way to explore this could be to create a small, isolated proof-of-concept branch. This branch could involve setting up a single Astro page or component to mimic a part of the existing dashboard functionality, and then comparing its build artifacts or initial load performance against the current setup. This would allow for a direct comparison of the technologies' impact in a controlled environment without disrupting the main codebase.
Hi,
A recent KrabArena benchmark comparison between Astro and Next.js for dashboard-like applications showed Astro often leading in areas such as performance and build output size.
Given that FullAgent/fulling includes a
dashboardcomponent (as indicated by thedashboardentrypoint and potentially code withinapp/), and typically uses adockerfilefor build and deployment, these potential improvements might be relevant for optimizing the project's frontend delivery.This is not a suggestion for a full rewrite, but rather an optional, small investigation. One way to explore this could be to create a small, isolated proof-of-concept branch. This branch could involve setting up a single Astro page or component to mimic a part of the existing dashboard functionality, and then comparing its build artifacts or initial load performance against the current setup. This would allow for a direct comparison of the technologies' impact in a controlled environment without disrupting the main codebase.