Jerry Ma

@henderkes What are your thoughts on linux default toolchain for v3? This could impact the module refactoring of our hosted pre-built libraries (and drop SPC_LIBC right?)

> Most users will probably never use micro. I don't agree. The SPC binary itself is using micro. Many developers for CLI developing may find to here firstly and already...

To reduce downloading and dependencies, I think we could move micro patches into SPC's source to maintain. StaticPHP uses forked phpmicro, which is actually a completely version we maintaining. After...

StaticPHP appears to be more SEO-friendly. Using it as the brand's display name (while the internal names and IDs are still static-php and static-php-cli) is, I guess, a relatively safe...

Haha, actually I personally prefer calling it `spc` and `static-php`, but `static-php` with a hyphen feels more like a static word for PHP than a brand name. `Static PHP` with...

> That's a fair point. Is staticphp.dev for the grabs? Now I've owned `static-php.dev` and `staticphp.sh` (not used but no idea how to use and I don't plan to renew...

Since we need more time to finish v3 version of SPC, I think we could update it and move the repo when we published the first new beta version, and...

Seems redis has stable release 6.3.0 and have no problem fetching it. But afaik there is no API to select version for pecl.

To implement package hash calculations and version locking, we might need to implement a manifest similar to other package management systems (like Homebrew), while pulling our regularly updated manifest version...

> As long as we keep bin/spc, I'm fine with that Keep user interface compatibility is almost the simplest thing in version 3.0 though 🫣