diff --git a/src/templates/src/fishbowls/oop/OOP.html b/src/templates/src/fishbowls/oop/OOP.html
index 7493dec..acb3bb1 100644
--- a/src/templates/src/fishbowls/oop/OOP.html
+++ b/src/templates/src/fishbowls/oop/OOP.html
@@ -460,7 +460,7 @@ The pinned messages are some "checkpoints" in the discussion; chapter markers of
-
1958-1966: A few different people gradually come up with the notion of structured data. Conventions for managing compound data made of multiple words in memory. If you have two points, you want their x and y coordinates close together and in the same relative order. Seems obvious, but wasn't! See http://akkartik.name/sketchpad-oo.png from the Sketchpad thesis [1].
+ 1958-1966: A few different people gradually come up with the notion of structured data. Conventions for managing compound data made of multiple words in memory. If you have two points, you want their x and y coordinates close together and in the same relative order. Seems obvious, but wasn't! See http://akkartik.name/sketchpad-oo.png from the Sketchpad thesis [1].
1960-1962: Ivan Sutherland works on Sketchpad. It presages many OO ideas, but they're all in the programmer's mind and prose (thesis) because the code is all machine code.
@@ -470,7 +470,7 @@ The pinned messages are some "checkpoints" in the discussion; chapter markers of
1973-1975: Abstract data types by Barbara Liskov. Ignore internal details of how objects are laid out in memory. Focus instead on a small vocabulary of operations that can be performed using them. Interfaces, basically.[4]
-1966-1975: Alan Kay coins OO after working on Smalltalk. (The first chapter of http://gagne.homedns.org/~tgagne/contrib/EarlyHistoryST.html is better than my history above.) "Did not have C++ in mind." However, we're only halfway done.
+1966-1975: Alan Kay coins OO after working on Smalltalk. (The first chapter of http://gagne.homedns.org/~tgagne/contrib/EarlyHistoryST.html is better than my history above.) "Did not have C++ in mind." However, we're only halfway done.
(edited)
@@ -525,17 +525,17 @@ The pinned messages are some "checkpoints" in the discussion; chapter markers of
@@ -1303,8 +1303,8 @@ Regarding (1), I personally believe this is much better solved with a well desig
Regarding (2), this is a weird linguistic typology thing which I doubt most people will even know unless they speak multiple languages. If you want to learn more about word orders in different languages, I recommend reading the following:
- *
https://en.wikipedia.org/wiki/Subject%E2%80%93verb%E2%80%93object_word_order
- *
https://en.wikipedia.org/wiki/Verb%E2%80%93subject%E2%80%93object_word_order
+ *
https://en.wikipedia.org/wiki/Subject%E2%80%93verb%E2%80%93object_word_order
+ *
https://en.wikipedia.org/wiki/Verb%E2%80%93subject%E2%80%93object_word_order
Regarding (3), this is purely a tooling issue. It comes down to two main aspects:
@@ -2202,7 +2202,7 @@ yes exactly, that's part of what I mean by "mere" (i.e. they're not wound up in
@@ -2874,8 +2874,8 @@ this is why I think mere methods and OOP are separate concerns. Having a nice .
By this statement, I mean that
artificially conforming to any/all relations between data and types to an artificial hierarchy of
agency is a form of naïve-Aristotelian metaphysics. Since there is no actual
agency in the programming objects, it is a partial fallacy (and as previously stated, category error). When trying to conform a program to have a particular structure when it does not naturally, the absence of a structure in a program in more useful than a bad structure.
-[1]
https://en.wikipedia.org/wiki/Category_mistake
-[2]
https://www.gingerbill.org/article/2020/05/31/progamming-pragmatist-proverbs/
+[1]
https://en.wikipedia.org/wiki/Category_mistake
+[2]
https://www.gingerbill.org/article/2020/05/31/progamming-pragmatist-proverbs/
@@ -4043,7 +4043,7 @@ Certainly though the term "design patterns" has come to exclusively mean "object
-Among other critiques, this approach causes some blind spots because you get trained to think in terms of nouns and deemphasize verbs: http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom-of-nouns.html
+Among other critiques, this approach causes some blind spots because you get trained to think in terms of nouns and deemphasize verbs:
http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom-of-nouns.html
@@ -4436,7 +4436,7 @@ Among other critiques, this approach causes some blind spots because you get tra