Neither, though the final result can be similar, but at project level, tinygo and pcz has very different approaches to achieve the final result:
- tinygo chose the hard path to write a llvm backed toolchain with some custom behavior that compiles Go code (using official std) to llvm targets.
- pcz chose the easy path to write a stdlib from scratch that compiles to desired targets using the official Go toolchain.
One major benefit of pcz's approach is you can import packages from the pcz std module like you do with any other Go package, the development experience can remain unchanged.
Neither, though the final result can be similar, but at project level, tinygo and pcz has very different approaches to achieve the final result:
- tinygo chose the hard path to write a llvm backed toolchain with some custom behavior that compiles Go code (using official std) to llvm targets.
- pcz chose the easy path to write a stdlib from scratch that compiles to desired targets using the official Go toolchain.
One major benefit of pcz's approach is you can import packages from the pcz std module like you do with any other Go package, the development experience can remain unchanged.