It may be that the launch of SAFE 1.0 is like DOS 1.0 was 34 years ago. DOS consisted of about 4 thousand lines of assembler code http://www.operating-system.org/betriebssystem/_english/bs-msdos.htm SAFE may not be too much more than that in lines of Rust code. DOS 1.0 and SAFE are/were decentralizers but Win 10 and Azure are certainly not that. The Open Surveillance model of Win 10 screams for SAFE. SAFE probably won’t take 34 years to reach its full complement and being based on the free(dom) software model it won’t have bundling issues and anti trust adding to its political architecture.
Given that the SAFE coin and SAFE distribution model are not separate from the SAFE network OS does that imply that the following seemingly inevitable features are apps or are they extensions of homogeneous SAFE(?):
SAFE Browser and SAFE Search (are these really separate apps or functions?)
SAFE Local device OS (there aren’t any client’s so is this separate?)
SAFE Distributed computing functionality & SDR Mesh (almost like a driver for the SAFE net OS)
SAFE verification of SAFE spec hardware (driver like)
I have a feeling that none of these are really separate apps. Does this mean in 5 years we will have a core SAFE with 35 thousand lines of Rust code with all of this functionality built in?
I don’t see any fat in any of the above. If your idea of the system was DOS then yes the Venn diagram would show you that search-browser functionality might be fat as your particular PC might not have a modem, but even the medium term viability of SAFE is diminished without tight integration of each of the above. With DOS you were safe is you weren’t plugged into a network. With SAFE your system is safe because it is intermingled with the elements of a network in a way that only you can disambiguate.