the size of the image concerns me:
kernel+boot 100MB, with C it could be 4MB.
kernel+boot+basicpackages 500MB, with C it could be 16MB.
Golang is designed to be static all-in-one packages for each application(e.g. microservices), when you run a lot of them in any given system, it becomes really large together.
I don't mind to use one or two go binaries in my embedded board, when I need a few of them, I am concerned about the storage size(possibly memory size as well).
a helloworld go binary is about 8MB, a C is about 20KB(shared libraries), go binary size adds up really fast due to the fact most do not use shared libraries even when there are many go binaries in the system.
The best solution would be to use BTRFS/ZFS with transparent compression (can use fast algorithms) or even SquashFS if you can deploy the entire app image mounted in a directory.
Wondering if they can achieve that.
Given this is what the README states, how can it be a GNU/Linux distribution?
It doesn’t include a shell or anything like coreutils either (GNU or otherwise).
You're taking a few F/OSS components (in this case the Linux kernel, the golang toolchain and some custom software) and you're assemblying them into a bootable system.
That's almost quite literally the definition of "gnu/linux distribution".
Anyone know if there a list of these types of frameworks anywhere?
https://github.com/gokrazy/gokrazy/issues/13
And if you read the issue, it's a bit understandable to not want to reimplement wpa_supplicant.