commit 916319d79d1fc44e04a4602a6df704c45ac5b3a3
parent 4e5a4bed68356a29fdbbeb2b2f134075cf431508
Author: Ville-Matias Heikkila <viznut@low.fi>
Date: Fri, 10 Nov 2023 13:32:52 +0200
some small changes
Diffstat:
16 files changed, 16 insertions(+), 16 deletions(-)
diff --git a/Operating_systems.mdwn b/Operating_systems.mdwn
@@ -1,4 +1,4 @@
-When assessing operating systems, we should pay attention to:
+When assessing [[operating system]]s, we should pay attention to:
* [[TODO]]
diff --git a/Plan_9.mdwn b/Plan_9.mdwn
@@ -1,4 +1,4 @@
-**Plan 9** is a fully-featured, clean, compact and uniform operating system built as a successor to [[Unix]].
+**Plan 9** is a fully-featured, clean, compact and uniform [[operating system]] built as a successor to [[Unix]].
Plan 9 is not a product, it is an experimental investigation into a different way of computing. The developers started from several basic assumptions: that CPUs are very cheap but that we don't really know how to combine them effectively; that *good* networking is very important; that an intelligent user interface is a Right Decision; that existing systems are not the correct way to do things, and in particular that today's workstations are not the way to go.
diff --git a/Rust.mdwn b/Rust.mdwn
@@ -1,4 +1,4 @@
-[Rust](https://www.rust-lang.org/) is a programming language created in 2010. Rust is a statically typed, multi-paradigm general purpose language developed by Mozilla. It has applications for both "high level" programming tasks (such as web applications) as well as low-level systems programming code. The first stable release was in 2014. Rust has a number of advantages over C:
+**[Rust](https://www.rust-lang.org/)** is a programming language created in 2010. Rust is a statically typed, multi-paradigm general purpose language developed by Mozilla. It has applications for both "high level" programming tasks (such as web applications) as well as low-level systems programming code. The first stable release was in 2014. Rust has a number of advantages over C:
- Memory safety
- Modern semantics and language features
diff --git a/Smalltalk.mdwn b/Smalltalk.mdwn
@@ -1,4 +1,4 @@
-Smalltalk is an object-oriented, dynamically typed reflective programming language. Kay says their Smalltalk [[virtual machine]] for the 8086 was 6 kilobytes of machine code.
+**Smalltalk** is an object-oriented, dynamically typed reflective programming language. Kay says their Smalltalk [[virtual machine]] for the 8086 was 6 kilobytes of machine code.
* [ST-72 on the SqueakWiki](https://wiki.squeak.org/squeak/989)
diff --git a/Unix.mdwn b/Unix.mdwn
@@ -1,6 +1,6 @@
-**Unix** is a multi-user operating system whose development was started in
+**Unix** is a multi-user [[operating system]] whose development was started in
1969 by Ken Thompson and Dennis Ritchie, as well as an entire family of
-operating system derived from the original Unix. Since Unix is also a
+operating systems derived from the original Unix. Since Unix is also a
trademark that only applies to specific products, terms like "*nix" are
often used to refer to the entire family of Unix-compatible systems
(including [[GNU]]/[[Linux]]). In this article, we don't bother to respect
@@ -11,7 +11,7 @@ Unix was originally a mainframe-like [[time-sharing]] operating system
processing power and storage space. In order to keep the system small,
elegant and flexible, it was decided to have a set of "small and sharp"
tools that can interoperate with each other via input/output piping. At
-later times, Unix gathered bloat, and from the 1980s microcomputer point of
+later times, Unix gathered [[bloat]], and from the 1980s microcomputer point of
view it was already seen as a huge and complex OS for big computers.
The possibility to reimplement the system gradually, one tool at a time, was
diff --git a/human-scale.mdwn b/human-scale.mdwn
@@ -1,4 +1,4 @@
-Human-scale, or _Personal Mastery_, is defined in [Design Principles Behind Smalltalk](https://www.cs.virginia.edu/~evans/cs655/readings/smalltalk.html) as **comprehensible by a single individual**.
+**Human-scale**, or _Personal Mastery_, is defined in [Design Principles Behind Smalltalk](https://www.cs.virginia.edu/~evans/cs655/readings/smalltalk.html) as **comprehensible by a single individual**.
* If a system is to serve the creative spirit, it must be entirely comprehensible to a single individual.
* Any barrier that exists between the user and some part of the system will eventually be a barrier to creative expression.
diff --git a/index.mdwn b/index.mdwn
@@ -48,7 +48,7 @@ Around, nearby and beyond
* [[Communities]] that (may) have compatible goals and interests;
* More fine-grained [[properties]] of software built using permacomputing principles, and how they're shared by neighboring communities;
-* [[Damaged Earth Catalog|DEC]] covers concepts and movements related to permacomputing.
+* [[Damaged Earth Catalog]] covers concepts and movements related to permacomputing.
Community?
==========
diff --git a/kolmogorov_complexity.mdwn b/kolmogorov_complexity.mdwn
@@ -1,4 +1,4 @@
-The Kolmogorov complexity of an information object, such as a piece of text, is the length of the shortest computer program that produces the object as output. It is a measure of the computational resources needed to specify the object, and is also known as algorithmic complexity.
+The **Kolmogorov complexity** of an information object, such as a piece of text, is the length of the shortest computer program that produces the object as output. It is a measure of the computational resources needed to specify the object, and is also known as algorithmic complexity.
KU( x) = min { |p| | p ∈ Σ∗0, U( p) = x }
diff --git a/offline_first.mdwn b/offline_first.mdwn
@@ -1,3 +1,3 @@
-Offline first, like its name implies, is the design of [[software]] or [[hardware]] that does not depend on connectivity. It is also an important part of [[designing for descent|design for descent]].
+**Offline first**, like its name implies, is the design of [[software]] or [[hardware]] that does not depend on connectivity. It is also an important part of [[designing for descent|design for descent]].
According to Leslie Lamport (1987), "A distributed system is one in which the failure of a computer you didn’t even know existed can render your own computer unusable".
diff --git a/Power_consumption.mdwn b/power_consumption.mdwn
diff --git a/pseudosimplicity.mdwn b/pseudosimplicity.mdwn
@@ -1,4 +1,4 @@
-In mainstream computing, ease of use is usually implemented as superficial simplicity, as an additional layer of complexity that hides the underlying layers. Meanwhile, systems that are actually very simple and elegant are often presented in ways that make them look complex to laypeople.
+In mainstream computing, ease of use is usually implemented as superficial simplicity or **pseudosimplicity**, as an additional layer of complexity that hides the underlying layers. Meanwhile, systems that are actually very simple and elegant are often presented in ways that make them look complex to laypeople.
Feminist (cyberfeminist) critique of simple interfaces and invisibility of underlying infrastructure says this simplicity is just predisposition for mainstream or stereotype use.
diff --git a/right_to_repair.mdwn b/right_to_repair.mdwn
@@ -1 +1 @@
-The Right to Repair movement seeks to ensure that OEMs provide tools, [[software]] and [[instruction manuals|documentation]] to their consumers in order for them to perform their own [[diagnostics]] and [[repairs|repair]].
+The **Right to Repair** movement seeks to ensure that OEMs provide tools, [[software]] and [[instruction manuals|documentation]] to their consumers in order for them to perform their own [[diagnostics]] and [[repairs|repair]].
diff --git a/salvage.mdwn b/salvage.mdwn
@@ -1,3 +1,3 @@
-Utilizing only already available computational resources, to be limited by that which is already produced.
+**Salvage** refrest to utilizing only already available computational resources, to be limited by that which is already produced.
Figuring out how to make the best possible use out of the millions of devices which already exist. Salvage-friendly electronics are parts that are no longer manufactured, but that are available by the billions in landfills. Those who can manage to create new designs from scavenged parts with low-tech tools will be able to preserve electronics.
diff --git a/software_rot.mdwn b/software_rot.mdwn
@@ -1,4 +1,4 @@
-**Software rot** is generally thought of as degradation of the software due to a changing environment. For example, a program written a decade ago may no longer work with new versions of the libraries it depends on because some of them have changed without retaining backwards compatibility. This kind of thinking encourages a culture where software becomes [[obsolete|obsolescence]] unless it is constantly maintained.
+**Software rot** is generally thought of as degradation of [[software]] due to a changing environment. For example, a program written a decade ago may no longer work with new versions of the libraries it depends on because some of them have changed without retaining backwards compatibility. This kind of thinking encourages a culture where software becomes [[obsolete|obsolescence]] unless it is constantly maintained.
A better approach might be to talk about the reliability of the environment the software depends on. Would you build a house on a bog?
diff --git a/Technological_diversity.mdwn b/technological_diversity.mdwn
diff --git a/wishcycling.mdwn b/wishcycling.mdwn
@@ -1 +1 @@
-Wishcycling is when people place non-recyclable items in the recycling and hope those items will end up being recycled.
+**Wishcycling** is when people place non-recyclable items in the recycling and hope those items will end up being recycled.
