You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@seata.apache.org by Qiufeng Liu <li...@apache.org> on 2025/05/20 01:55:01 UTC
Proposal on replacing the front-end framework of Seata Console
1. Background1.1 Current Issues
Currently, some packages referenced by the Console frontend framework have
not been updated for a long time, leading to dependencies that cannot be
upgraded to the latest versions. This results in frequent security
vulnerabilities and other issues.
1.2 UI Library Issues
The UI library currently referenced by the Console frontend framework has
relatively low popularity, incomplete documentation, and is not -friendly
for contributors to quickly get started and iterate.
2. Purpose2.1 Technology Upgrade
To restructure existing functionality using a frontend framework and UI
library that are highly popular, well-documented, and have stable update
frequencies.
2.2 Technology Selection
To select a framework that considers the current frontend technical
proficiency of contributors.
3. Frontend Framework Selection3.1 React Stack
React Official Website <https://react.dev/>
3.1.1 Global Popularity
React is likely the most popular frontend framework globally.
3.1.2 Flexibility
React offers high flexibility, but the coding styles of different
developers may vary significantly, and different frameworks (e.g., umijs or
icejs) may have distinct writing styles.
3.1.3 Performance Optimization
React sometimes requires developers to consider performance optimization,
and different coding styles may lead to noticeable performance differences.
3.1.4 Dependencies
The dependencies in the React stack are not unified, for example, global
state management solutions like dva and redux are available.
3.2 Vue Stack
Vue Official Website <https://vuejs.org/>
3.2.1 Global Popularity
Vue is also highly popular globally, though possibly not as much as React.
3.2.2 Coding Style
Vue primarily uses template syntax, resulting in smaller coding style
differences among developers. However, it is less flexible compared to
React.
3.2.3 Performance Optimization
Vue includes built-in optimization algorithms, so developers generally do
not need to focus excessively on performance optimization.
3.2.4 Dependencies
Vue provides a series of official dependencies for project construction,
with relatively unified packages.
3.3 Other Frameworks
The selection of other frameworks will be discussed separately.
4. UI Library Selection
The following lists some relatively popular UI libraries for reference.
Specific selections should consider international popularity, the number of
components, and their ease of use.
4.1 React Series
- Ant Design: Official Website <https://ant.design/>
- daisyui: Official Website <http://daisyui.com/>
- shadcn: Official Website <https://ui.shadcn.com/>
4.2 Vue Series
- element-ui: Official Website <https://element-plus.org/>
- daisyui: Official Website <http://daisyui.com/>
- vuetifyjs: Official Website <https://vuetifyjs.com/>
- Ant Design Vue: Official Website <https://antdv.com/>
*5. About TypeScript*
The project will directly adopt TypeScript and no further discussion will
be made.
*Which framework and UI library do you want to use the most? Welcome to
reply and discuss.*
--
Best Regards,
Qiufeng Liu(liuqiufeng)
Re: Proposal on replacing the front-end framework of Seata Console
Posted by YongJun Hong <yo...@apache.org>.
Vue +1
Since committers and PMC members have limited bandwidth, it makes more sense to focus on the core features like distributed transactions instead of the Console's front-end framework.
For this reason, I recommend using Vue, as it tends to have more consistent coding styles and is easier to maintain.
Additionally, as a frontend beginner myself, I find Vue to be more approachable, which is another reason for my recommendation. 😁
On 2025/05/20 01:55:01 Qiufeng Liu wrote:
> 1. Background1.1 Current Issues
>
> Currently, some packages referenced by the Console frontend framework have
> not been updated for a long time, leading to dependencies that cannot be
> upgraded to the latest versions. This results in frequent security
> vulnerabilities and other issues.
> 1.2 UI Library Issues
>
> The UI library currently referenced by the Console frontend framework has
> relatively low popularity, incomplete documentation, and is not -friendly
> for contributors to quickly get started and iterate.
> 2. Purpose2.1 Technology Upgrade
>
> To restructure existing functionality using a frontend framework and UI
> library that are highly popular, well-documented, and have stable update
> frequencies.
> 2.2 Technology Selection
>
> To select a framework that considers the current frontend technical
> proficiency of contributors.
> 3. Frontend Framework Selection3.1 React Stack
>
> React Official Website <https://react.dev/>
> 3.1.1 Global Popularity
>
> React is likely the most popular frontend framework globally.
> 3.1.2 Flexibility
>
> React offers high flexibility, but the coding styles of different
> developers may vary significantly, and different frameworks (e.g., umijs or
> icejs) may have distinct writing styles.
> 3.1.3 Performance Optimization
>
> React sometimes requires developers to consider performance optimization,
> and different coding styles may lead to noticeable performance differences.
> 3.1.4 Dependencies
>
> The dependencies in the React stack are not unified, for example, global
> state management solutions like dva and redux are available.
> 3.2 Vue Stack
>
> Vue Official Website <https://vuejs.org/>
> 3.2.1 Global Popularity
>
> Vue is also highly popular globally, though possibly not as much as React.
> 3.2.2 Coding Style
>
> Vue primarily uses template syntax, resulting in smaller coding style
> differences among developers. However, it is less flexible compared to
> React.
> 3.2.3 Performance Optimization
>
> Vue includes built-in optimization algorithms, so developers generally do
> not need to focus excessively on performance optimization.
> 3.2.4 Dependencies
>
> Vue provides a series of official dependencies for project construction,
> with relatively unified packages.
> 3.3 Other Frameworks
>
> The selection of other frameworks will be discussed separately.
> 4. UI Library Selection
>
> The following lists some relatively popular UI libraries for reference.
> Specific selections should consider international popularity, the number of
> components, and their ease of use.
> 4.1 React Series
>
> - Ant Design: Official Website <https://ant.design/>
> - daisyui: Official Website <http://daisyui.com/>
> - shadcn: Official Website <https://ui.shadcn.com/>
>
> 4.2 Vue Series
>
> - element-ui: Official Website <https://element-plus.org/>
> - daisyui: Official Website <http://daisyui.com/>
> - vuetifyjs: Official Website <https://vuetifyjs.com/>
> - Ant Design Vue: Official Website <https://antdv.com/>
>
> *5. About TypeScript*
> The project will directly adopt TypeScript and no further discussion will
> be made.
>
>
> *Which framework and UI library do you want to use the most? Welcome to
> reply and discuss.*
> --
>
> Best Regards,
> Qiufeng Liu(liuqiufeng)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@seata.apache.org
For additional commands, e-mail: dev-help@seata.apache.org