2 ms·
Perfect timing. I ordered a copy of "A Philosophy of Software Design" a week ago and it arrived yesterday. I'm going to start reading it tonight, but this is
by OhMeadhbh 2y ago
Perfect timing. I ordered a copy of "A Philosophy of Software Design" a week ago and it arrived yesterday. I'm going to start reading it tonight, but this is a nice preface, I bet.
Several months ago a friend encouraged me to look at Tcl again (independent of Tk.) Mixins, regexes, reflection. All stuff I didn't appreciate in the early 90s. And I had reason to look at Minix a few years back. Ousterhout definitely did some good work. I think he might have been just a little bit ahead of the rest of us.
- kragen 2y agoit didn't have mixins in the early 90s tcl's model of what data is doesn't accommodate general graphs, just trees. you can make a hash table but not a hash table of hash tables. on the plus side you won't have aliasing bugs like python's notorious matrix = [[0] * width] * height because its data model is so weak, you routinely resort to reflection to get things done, which makes it really hard to maintain tcl programs of any depth
- leetrout 2y agoIt is a phenomenal book for what it is. It was the required reading for the class I taught at UNC in 2019. I am teaching a workshop in September and bought a copy for every attendee because I believe it is that important for people to be exposed to his ideas and how he approaches things. I was also impressed with "Righting Software" and the premise of volatility based decomposition but it is not nearly as approachable as Ousterhout's book.