-
Notifications
You must be signed in to change notification settings - Fork 1
ADR Template
Vlas edited this page Jan 21, 2024
·
5 revisions
- Status: Proposed
- Deciders: @kravalg, @TuranC, @vlas-pravsha
- Date: 2024-01-19
Technical Story: This decision is driven by the critical need to enhance the speed and overall performance of our website.
The project requires choosing between Preact and React for building the frontend. Both frameworks are popular choices for building user interfaces, and the team needs to decide which one to use based on the project's requirements and constraints.
- Performance The library should enable fast page loads and efficient data handling.
- Ecosystem support and third-party libraries
- Developer Experience: Ease of use, community support, and learning curve.
- Preact
- React
- Good, because it has a smaller bundle size, suitable for performance-critical applications.
- Good, because it provides a similar API to React, making it easier for React developers to transition.
- Bad, because it has a smaller community and ecosystem compared to React.
- Good, because of a large and active community, providing better support and resources.
- Good, because of extensive third-party library support.
- Bad, because of a potentially steeper learning curve for developers new to React.