| It's not meant to be just another Linux distribution. It will be whole new
system with Linux kernel at the core. It will be more in line with BSDs.
That's why static linking will make sense. Your updates are just rsync away. As I see it suckless.org community prefers 'linking' in form of shell scripts
or communication via pipes, ideally via system's VFS. You will get lean and minimalistic base system. If something will not share
same ideals it will not be in the base system (like glib[c]?, bash, Firefox).
It is possible that dynamic linking will be allowed in /emul chroot as stated
in 'Filesystem' page. I see sta.li as rock solid minimalistic base system, which you can use on it's
own (how I belive many suckless.org folks will use it) or as a base system,
that you can build upon. Even more than that, you will be able to use sta.li
components in generic distributions with ease, because of static linking. Go-lang is in my opinion next step for Bell Labs folks in lean development
for the masses. Don't take this too literally ;) Plan 9 [1] was first step,
but people did not want whole new system. Inferno [2] was next one, but VM
system was too much also. Go allows to use some of Plan 9 features in
edible form for the masses. Without requirement to install specific system
or VM to run your programs. That to some extent is what makes sta.li's ideals
similar to go-lang's. Development of sta.li is at slow pace, but many experiments are under
development [3]. Probably some of them will be included in sta.li.
Most probably sta.li will include X11, but we are seeing some developments with
Wayland [4]. [1] - http://en.wikipedia.org/wiki/Plan_9_from_Bell_Labs
[2] - http://en.wikipedia.org/wiki/Inferno_%28operating_system%29
[3]
- https://github.com/henrysher/sinit
- http://galos.no-ip.org/sdhcp
- http://git.suckless.org/dmc/
[4] - https://github.com/michaelforney/swc |