@ -4,7 +4,7 @@ Dusk OS is a work in progress non-[Unix](unix.md) extremely [minimalist](minimal
The project has a private mailing list. Apparently there is talk about the system being useful even before the collapse and so it's even considering things like [networking](network.md) support etc. -- as [capitalism](capitalism.md) unleashes hell on [Earth](earth.md), any simple computer capable of working on its own and allowing the user complete control will be tremendously useful, even if it's just a programmable calculator. Once [GNU](gnu.md)/[Linux](linux.md) and [BSD](bsd.md)s sink completely (very soon), this may be where we find the safe haven.
The only bad thing about the project at the moment seems to be the presence of some [pseudoleftists](pseudoleft.md) around the project, threatening political takeover etcetc. At the moment there's thankfully no [code of censorship](coc.md) :-) If the project gets more popular it will be forced. Hopefully [forks](fork.md) will come if anything goes wrong.
The only bad thing about the project at the moment seems to be the presence of some [pseudoleftists](pseudoleft.md) around the project, threatening political takeover etcetc. At the moment there's thankfully no [code of censorship](coc.md) :-) If the project gets more popular it will be forced. Hopefully [forks](fork.md) will come if anything goes wrong. In any case, [we](lrs.md) will be continuing our independent work that will probably yield a similar system, thought much later.
{ I'm not 100% sure about everything that will follow as I'm still studying this project, please forgive mistakes, double check claims. ~drummyfish }
@ -91,7 +91,14 @@ Using marbles (and possibly also similar rolling shapes, e.g. cylinders, disks,
**Basic principle** is that of a marble performing computation by going through a maze -- while a single marble can be used to evaluate some simple [logic circuit](logic_circuit.md), usually (see e.g. [Turing Tumble](turing_tumble.md)) the design uses many marbles and performs sequential computation, i.e. there is typically a **bucket** of marbles placed on a high place from which we release one marble which (normally by relying on [gravity](gravity.md)) goes through the maze and performs one computation cycle (switches state, potentially flips a memory bit etc.) and then, at the bottom (end of its path), presses a switch to release the next marble from the top bucket. So the computation is autonomous, it consumes marbles from the top bucket and fills the bottom bucket (with few marbles available an operator may sometimes need to refill the top bucket from the bottom one). The maze is usually an angled board onto which we just place obstacles; multiple layers of boards with holes/tunnels connecting them may be employed to allow more complexity. { You can build it from lego probably. ~drummyfish }
NOTE: Balls may be used to perform computation also in other ways than described here, very notable is e.g. the **[billiard ball computer](billiard_ball_computer.md)** (which also has a great advantage of performing reversible computation). However here we will focus on the traditional "marble maze" approach.
NOTE: Balls, or potentially other "falling/moving objects", may be used to perform computation also in other ways than we'll describe further on -- some of the alternative approaches are for example:
- The **[billiard ball computer](billiard_ball_computer.md)** (which also has a great advantage of performing reversible computation).
- Another possible idea is that of the falling object ITSELF encoding a value (likely just a bit), for example imagine some kind of arrow shape which itself represents either 1/0 by pointing up/down, changing its orientation as it passes through the gates (we would also have to ensure the orientation can't change spontaneously on its own of course).
- A bit can also be represented by presence/absence of the marble -- this is utilized e.g. by *binary marbles* (https://binarymarbles.weebly.com/how-it-works.html). For example the AND gate is implemented by one input marble falling into a hole, making a "bridge" for the other marble that then overcomes the hole and reaches output. Timing may play an important role as some gates (e.g. XOR) require dropping the input marbles simultaneously.
- ...
These approaches may be tried as well, however further on here we will focus on the traditional "marble maze" approach in which the marbles mostly serve as a kind movement force that flips bits represented by something else (or possibly indicate answer by falling out through a specific hole).
The **disadvantage** here is that the computation is **slow** as to perform one cycle a marble has to travel some path (which may take many seconds, i.e. in the simple form you get a "CPU" with some fractional frequency, e.g. 1/5 Hz). This can potentially be improved a little, e.g. by [pipelining](pipeline.md) (releaseing the next marble as soon as possible, even before the current one finishes the whole path) and [parallelism](parallelism.md) (releasing multiple marbles, each one doing some part of work in parallel with others). **Advantages** on the other hand include mentioned simplicity of construction, visual clarity (we can often make the computer as a flat 2D board that can easily be observed, debugged etc.) and potentially good extensibility -- making the pipeline (maze) longer, e.g. to add more bits or functionality, is always possible without being limited e.g. by friction like with gears (though usually for the cost of speed).
Under [capitalism](capitalism.md) technological minimalism is suppressed in the mainstream as it goes against [corporate](corporation.md) interests, i.e. those of having monopoly control over technology, even if such technology is "[FOSS](foss.md)" (which then becomes just a cool brand, see [openwashing](openwashing.md)). We may, at best, encounter a "shallow" kind of minimalism, so called [pseudominimalism](pseudominimalism.md) which only tries to make things appear minimal, e.g. aesthetically, and hides ugly overcomplicated internals under the facade. [Apple](apple.md) is famous for this [shit](shit.md).
@ -6,6 +6,8 @@ Music is an auditory [art](art.md) whose aim is to create [pleasant](beautiful.m
**[Copyright](copyright.md) of music**: TODO (esp. soundfonts etc.).
TODO: list of most LRS/suckless instruments
## Modern Western Music + How To Just Make Noice Music Without PhD
{ I don't actually know that much about the theory, I will only write as much as I know, which is possibly somewhat simplified, but suffices for some kind of overview. Please keep this in mind and don't eat me. ~drummyfish }
Permacomputing wiki is a computer [minimalist](minimalism.md) [pseudoleftist](pseudoleft.md)-infected wiki whose focus revolves around minimalist, ecology-friendly, [collapse](collapse.md)-ready computing; in many ways (especially when you take away the SJW fascism) the wiki is a lot similar to our [LRS wiki](lrs_wiki.md). It was started in 2022 and can now be accessed at https://permacomputing.net/, one of its famous users is [Viznut](viznut.md) (who allegedly coined the term "permacomputing" on his website in 2020). The wiki has some really cool stuff, but is sadly [toxic](toxic.md), with [code of censorship](coc.md) and is littered with pseudoleftist fascism (about half of bullet points in their site rules is just pseudoleftist copy pasta gospel lol). The wiki also seem to be dying. { One theory is that it was created as a rage reaction to our wiki and the activity was mostly fueled by anger which by now had possibly burned out :D ~drummyfish }
Permacomputing wiki is a computer [minimalist](minimalism.md) [pseudoleftist](pseudoleft.md)-infected wiki centered around so called [permacomputing](permacomputing.md) (a recent term that means basically "sustainable computing", focus on maximizing lifespan of technology, minimize its waste etc., inspired by [permaculture](permaculture.md)) that focuses a lot on minimalist, eco-friendly, [collapse](collapse.md)-ready computing; in many ways (especially when you take away the SJW fascism) the wiki is a lot similar to our [LRS wiki](lrs_wiki.md). It was started in 2022 and can now be accessed at https://permacomputing.net/, one of its famous users is [Viznut](viznut.md) (who allegedly coined the term "permacomputing" on his website in 2020). The wiki has some really cool stuff, but is sadly [toxic](toxic.md), with [code of censorship](coc.md) and is littered with pseudoleftist fascism (about half of bullet points in their site rules is just pseudoleftist copy pasta gospel lol). The wiki also seem to be dying. { One theory is that it was created as a rage reaction to our wiki and the activity was mostly fueled by anger which by now had possibly burned out :D ~drummyfish }
{ NOTE: Someone reached out to me pointing out permacomputing wiki focuses on new things and concepts while LRS just writes about Unix and "old" stuff -- that's true! Actually permacomputing wiki is awesome in this, it's just sad it's being plagued by ideological issues, but the "content" is really great. I wish I could write better about the "new", I just focus on what I personally do best, i.e. boomer stuff. But I will try to possibly change my direction a bit to focus on new ideas as well. Thanks to the reader for a kind email <3:-)~drummyfish}
