Non-Clash Kernel#
v2raya#
Advantages:
- Completely open-source
- Supports ss/ssr/v2ray subscription links
- Can import servers individually
- Kernel optional and open-source (v2ray-core/xray-core)
- Cross-platform compatible
Disadvantages:
- Unable to resolve clash subscription links
Clash Kernel#
Clash for Windows#
Github: Fndroid/clash_for_windows_pkg
Advantages:
- No need to install clash kernel separately
- Kernel open-source (optional [clash/clash premium])
- Cross-platform compatible
Disadvantages:
- Unable to import servers individually, can modify configuration files individually but too cumbersome for GUI users
- GUI was open-source before but not anymore
Clash Verge#
Github: zzzgydi/clash-verge
Advantages:
- No need to install clash kernel separately
- Kernel open-source (optional [clash/clash premium])
- Components open-source
- Cross-platform compatible
WEB GUI#
All are open-source software and require manual configuration of clash kernel and configuration files.
YACD#
Github: haishanh/yacd
Clash-Dashboard#
Github: Dreamacro/clash-dashboard
Brief Evaluation#
In personal usage, for airport subscription users, clash configuration files have become the mainstream or even the only subscription method. Therefore, v2raya is more suitable for self-built nodes or users with good ss/ssr/v2ray support subscription services.
Clash Verge provides the same experience as clash for Windows, but Clash Verge has a higher level of openness. Personally, I prefer Clash Verge.
The following is based on personal usage experience and may not be universally applicable or reasonable.
Personally, I feel that the clash kernel is more efficient and has lower latency compared to v2raya or x-ray kernels.