676 karma · joined September 10, 2008
Moore's Law. Use computers to make better computers. Exponential growth over more than 7 orders of magnitude and, although the growth rate is slowing, it hasn't run out of steam yet.
If AI eventually exhibits anywhere near that level of recursive self-improvement, godlike superintelligences lie in our future.
However, as the founders lost interest in the day-to-day operation of the company, any pretense of being more than just another soulless profit machine was discarded.
Well, from a high-level view the only way a cell can make more cells is to divide, and if it divides it either makes a copy of its genetic material first, or gives half of it to each daughter cell. So in that sense, they're the only two ways possible.
From a more detailed view, I wonder if the machinery of meiosis is evolutionarily the same in every sexually-reproducing species, or if it has evolved more than once. My guess is only once, because it has a specific sequence of events which is always the same.
There is a place for specialized notation and vocabulary. Exactly where that line should be drawn in programming has been an ongoing conversation since 1953 when John Backus proposed the concepts that would lead to the development of Fortran.
Exactly. As you say, we need to flatten the curve to keep hospitals from becoming overwhelmed, and we need to use the time to develop treatments to save the vulnerable when isolation eventually fails.
SHA-3 (originally named Keccak) is built on an entirely different foundation (called a sponge function), so it is unlikely that any attack against SHA-1 will be relevant to SHA-3. However, sponge functions are a relatively new idea, and weaknesses in the basic principles could conceivably be found in the future, as could weaknesses in the Keccak algorithm specifically.
Fabulous line. Is that attributable to anyone in particular?
Of course, that would require persisting in my current lifestyle in the face of a massive increase in wealth, which takes nontrivial self-discipline.
Of course, that's wealthy compared to most of the world.
2. No, I use syntax highlighting and indentation all the time. Trying to put words to my vague thoughts, I think the main issue is that, for example, in a let block the only indication of the meaning of all the items is the single function/macro name at the beginning of the block. Whereas in an algol-type language you have assignment operators in each item to indicate what they mean.
I do agree about homoiconicity. It's great for writing macros, and terrible for everything else. Of course, go too far in the other direction and you get perl, so... yeah.
Sounds like getting management to truly understand the concept of technical debt is the core problem.