Comparisons
Comparing Web Dev Frameworks
Purpose
To research, analyze (dev experience, libs, etc.) and benchmark comparable, real-world web dev frameworks.
Approach
For each Framework being analyzed, create a publicly avail (no auth, no ip-whitelist) web app, with the same data, design, components, structure, styling, and configs, and with comparable tools (parsers, compilers, builder, bundler, etc.) and API calls. This focuses benchmarking on core framework performance.
Project Structure
Create an app with the framework's default project structure. Customize only to achieve similar functionalities or to compare specific features (like SSG).
Data
Use identical, built-in content. Access the same public headless CMS, using the same API calls and auth approach (none, unless testing auth).
Analysis
Benchmarks
- Server Speeds, including HMR and initial startup, build and render times
- Resource Usage, including CPU and RAM
- Footprint, including bundle sizes
Developer Experience
Code organization, maintenance, debugging and collab
Docs, Tools and Libs
Copyright @ 2024 Anne Brown