195 karma · joined May 6, 2021
The article stops short of proposing a clear plan for how to handle the opposite problem, though: Entrenched monoliths. Once a class (or other abstraction) has grown for long enough (e.g. perhaps someone has read this article and is trying to avoid unnecessary complexity of code structure), it can become very difficult to break it up.
[1, 2, undefined].filter(Boolean). // number[]
is interesting because it makes use of the fact that the types of individual array members are known at compile time. I can think of some times when I have dealt with arrays that are defined at compile time, but not where I've needed to call .filter on such an array. Is there a common use case here?
(I am asking these questions excitedly, not dubiously)
Interesting that the reply mostly implied that there wasn't much reason to worry, and that the future and dominance of web apps was still uncertain. But we are reading this email exchange now I think largely because of how well placed Bill Gates's worries were. I wonder how many technologies he and other executives lost sleep over that did not amount to anything in the long run.
Apparently he has attended both Lutheran and Episcopal churches: https://en.wikipedia.org/wiki/Garrison_Keillor
Where did you find the Episcopalian version of the quote?