|
|
|
|
|
by drewcrawford
3486 days ago
|
|
The problem with Arch is that Swift relies quite heavily on Glibc so the work to port to alternate libc is very substantial. The other problem is that the mess basically starts there, e.g. Swift programs in practice also depend on Glibc and so after you kill the first turtle it's still turtles all the way down. You could build an Arch with Glibc, but why you would want to is not immediately clear. |
|