I value simple, efficient software that only uses as much energy as necessary. Which is trivial to fork & take in your direction. But which don't throw the baby out with the bathwater in regards to featureset (which is a matter of debate), accessibility, & inclusivity. The later two almost always asks nothing more of a dev than to use more complex dependencies.
There is a limited amount of renewable energy we can deploy, so everyone needs to get smarter about using it. Which we are!
Incidentally the main drive towards excessive energy use in computing is PROFIT! Surveillance advertising. DRM. SaaSS.
The other major drive is ideology. When so many would rather bundle Chrome (Electron) with their apps rather than learn native toolkits like GTK.
@alcinnz@floss.social i'm going so native programming that there isn't any toolkits or standards all the way down here.
but this is going to take a while , a very long while. while i learn.
@logan You've peaked my interest?
@alcinnz@floss.social making an operating system called 'Sauce'
there is literally nothing when you get this far down.
@logan Are you going to write your own kernel and everything? FYI Both FirefoxOS (mobile) and Peppermint (desktop) set out with similar design goals of fully integrating web apps with the local homescreen/ desktop.
@strypey@mastodon.nzoss.nz @alcinnz@floss.social yes i'm currently in the process of writing it actually.
@strypey@mastodon.nzoss.nz @alcinnz@floss.social also these wont be web apps like those other OSs , at least not initially.
they will not start up with any real internet connectivity but will use basically the same designs.
idk if you've ever seen those "desktops" made to run in the browser before but that's actually were this idea came from.
@tetrislife @logan @strypey I'm hearing differing architectural decisions, but yes, essentially same goal. Implementing a full OS from scratch which also happens to a browser.
@alcinnz@floss.social @tetrislife@qoto.org @strypey@mastodon.nzoss.nz
yes, sorry for the differing things as well.
it's hard to put in stone what i am only vaguely aware of.
the development of this operating system is mostly me just learning how they even work.
if I actually even get a working system out the other side than that's awesome but my actual goal is just to learn.
@logan Well, I'm sure you'll enjoy following me then! Btw I am planning to toot a higher-level summary of how CPUs & OSes work, once I've finished studying `sed`, `tar`, `xz`, & a pure-Haskell SVG implementation.
@alcinnz@floss.social @strypey@mastodon.nzoss.nz @tetrislife@qoto.org I have also accounted for things i could not currently know to the best of my ability in a not so obvious way.
I don't think anybody else would write their code like this.
you see everything is in this namespace 'Sauce'.
this is important because, at least hypothetically i can "side-step" my own kernel and implement some other kernel right along side my own kernels source code, assuming there is of course enough room in the ram.
@logan Making the rest of the OS independent of the kernel sounds wise. AFAIK GNU was originally written that way so it could use a proprietary UNIX kernel until HURD was ready. Because of that, when the Linux kernel became available, it could be easily swapped in for the UNIX kernel and the rest is history. If the BSD kernel has been released under a libre license before Linux was finished, GNU history could have unfolded quite differently.
@strypey If anyone wants to make their own OS primarily as a learning exercise or to explore alternate software architectures, I'd prefer you & others not to talk them out of it.
Certainly anyone doing this should be very aware of what a massive undertaking they're tackling and set their expectations accordingly. But it's still a worthwhile activity! Especially if you share your experience with others!
@alcinnz
> I'd prefer you & others not to talk them out of it.
Why would anyone do that? All experimentation is good experimentation (an ye harm none, yada yada).
> Especially if you share your experience with others!
... or pass on some relevant experiences of others as recorded in community histories. This was the intention of my posts in this thread.
