Pros of lede

• More comprehensive and feature-rich OpenWrt distribution
• Actively maintained with frequent updates and improvements
• Includes a wider range of pre-configured packages and optimizations

Cons of lede

• Larger codebase, potentially more complex for beginners
• May require more system resources due to additional features
• Some customizations might not be compatible with vanilla OpenWrt

Code comparison

lede:

#!/bin/bash
[ "${BASH_SOURCE[0]}" != "$0" ] && return
cd ${0%/*}
export OPENWRTROOT="$PWD"
export PATH="$OPENWRTROOT/staging_dir/host/bin:$PATH"
make -C tools/mtools prepare
$OPENWRTROOT/scripts/feeds update -a
$OPENWRTROOT/scripts/feeds install -a

openwrt-packages:

#!/bin/bash
[ "${BASH_SOURCE[0]}" != "$0" ] && return
cd ${0%/*}
export OPENWRTROOT="$PWD"
export PATH="$OPENWRTROOT/staging_dir/host/bin:$PATH"
./scripts/feeds update -a
./scripts/feeds install -a

The lede repository provides a more extensive build environment setup, including additional tool preparation steps, while openwrt-packages focuses on package management and installation.

Pros of immortalwrt

• More comprehensive and actively maintained project with a larger community
• Includes a full OpenWrt distribution, not just packages
• Offers improved performance and stability optimizations

Cons of immortalwrt

• Larger project scope may be overwhelming for users only seeking specific packages
• Potentially higher resource requirements due to additional features and optimizations
• May have a steeper learning curve for newcomers compared to simpler package collections

Code Comparison

immortalwrt:

./scripts/feeds update -a
./scripts/feeds install -a
make menuconfig
make -j$(nproc) V=s

openwrt-packages:

git clone https://github.com/kenzok8/openwrt-packages
cd openwrt-packages
./scripts/feeds update -a
./scripts/feeds install -a

Summary

immortalwrt is a full OpenWrt distribution with extensive features and optimizations, while openwrt-packages is a collection of packages for existing OpenWrt installations. immortalwrt offers a more comprehensive solution but may be more complex, whereas openwrt-packages provides a simpler approach for users who only need specific packages. The choice between the two depends on the user's requirements and level of expertise in OpenWrt development and customization.

Pros of helloworld

• More focused on specific networking tools and protocols (e.g., Shadowsocks, V2Ray)
• Regularly updated with the latest versions of included packages
• Lightweight and streamlined for easier integration

Cons of helloworld

• Limited scope compared to openwrt-packages, which offers a broader range of applications
• May require additional repositories for a complete OpenWrt setup
• Less documentation and community support due to its specialized nature

Code Comparison

helloworld:

include $(TOPDIR)/rules.mk

PKG_NAME:=shadowsocks-rust
PKG_VERSION:=1.14.3
PKG_RELEASE:=1

PKG_SOURCE_PROTO:=git
PKG_SOURCE_URL:=https://github.com/shadowsocks/shadowsocks-rust.git
PKG_SOURCE_VERSION:=v$(PKG_VERSION)

openwrt-packages:

include $(TOPDIR)/rules.mk

PKG_NAME:=luci-app-ssr-plus
PKG_VERSION:=186
PKG_RELEASE:=1

PKG_CONFIG_DEPENDS:= \
	CONFIG_PACKAGE_$(PKG_NAME)_INCLUDE_Kcptun \
	CONFIG_PACKAGE_$(PKG_NAME)_INCLUDE_NaiveProxy \
	CONFIG_PACKAGE_$(PKG_NAME)_INCLUDE_Redsocks2 \

Both repositories provide valuable resources for OpenWrt users, with helloworld focusing on specific networking tools and openwrt-packages offering a wider range of applications. The choice between them depends on the user's specific needs and preferences for their OpenWrt setup.

Pros of OpenClash

• Focused specifically on Clash integration for OpenWrt
• More frequent updates and active development
• Detailed documentation and user guides available

Cons of OpenClash

• Limited to Clash functionality
• May require more manual configuration
• Potentially higher resource usage due to specialized features

Code Comparison

OpenClash:

local clash = require "luci.model.clash"
local uci = require "luci.model.uci".cursor()

function action_start()
    clash.start()
end

openwrt-packages:

local sys = require "luci.sys"
local uci = require "luci.model.uci".cursor()

function action_restart()
    sys.call("/etc/init.d/package restart")
end

Summary

OpenClash is a specialized repository focusing on integrating Clash with OpenWrt, offering frequent updates and detailed documentation. However, it's limited to Clash functionality and may require more manual configuration. The openwrt-packages repository, on the other hand, provides a broader range of packages for OpenWrt but may not offer the same level of specialized features for Clash integration.

The code comparison shows that OpenClash uses a dedicated Clash module, while openwrt-packages uses more general system calls for package management. This reflects the specialized nature of OpenClash compared to the broader scope of openwrt-packages.