Youtube comments of Jeff Huffman (@tejing2001).

  1. 481
  2. 196
  3. 171
  4. 135
  5. 72
  6. I'd love to see a comparison between how much it would cost to deal with the eventual effects of climate change vs how much it would cost to reduce CO2 emissions quickly. Essentially view the reduction of CO2 emissions now as an investment, and (probabilistically) determine what its interest rate looks like. Is it a good investment? or will it actually disrupt our society less to let things go for a while? I'm all in favor of pushing nuclear past the NIMBY problem and switching to it over coal. CO2 aside, it's far safer, and with higher marketshare it would become yet safer and likely a lot cheaper as things get streamlined and more R&D goes into improving designs. With better designs, the amount of nuclear waste produced can be made extremely small, and you can even avoid ever needing to handle it at all. I'm also all in favor of manufacturing hydrocarbon fuels using atmospheric CO2 and nuclear energy. It needs more R&D, but it has a huge potential to deal with CO2 emissions without drastically changing our society and the way we do things. Renewables like solar and wind? ... not a fan. They need large amounts of grid energy storage of some sort, which isn't really feasible with current technology or anything on the horizon. They take tons of land area away from nature, and they take lots of manufacturing to make all those solar panels/wind turbines, and energy storage devices too (and all that manufacturing often releases CO2), and all that equipment needs to ultimately be disposed of when it breaks down, which is yet another source of environmental issues. Not to mention repairing and maintaining such a large amount of equipment takes a lot of human effort and isn't actually all that safe.
    52
  7. 33
  8. 26
  9. 26
  10. 24
  11. Karsten Hoff: Actually the storm at the start didn't bother me. True, martian atmosphere is very thin, but wind speeds are higher, so as I understand it the actual dynamic pressure isn't that much lower than what you get from winds on earth. Combine that with the low gravity and it sounds pretty plausible that a once-in-a-decade storm, say, would have enough wind force to tip the ascent rocket. What bothered me about the martian was how people didn't think about obvious issues until so late in the game, and how they ignored fairly obvious alternatives to their choices. How can they not start thinking about whether the mav can intercept the hermes until AFTER they've committed to the plan and the hermes is already on its way to do the hyperbolic flyby? Also, blowing the front hatch near the end seems like a stupid risk given that they still had more fuel. They can sacrifice some of the fuel allotted for the capture burn into earth orbit, so long as they still have enough that they stay bound to earth (and that's way more than enough delta-v). They would end up in some higher elliptical orbit around earth instead of a nice circular one, but it's not much harder for nasa to get a resupply vessel to them (than it would have been anyway) so long as they're actually gravitationally bound to earth. Also, given that they had the maneuvering backpack thing, why was disconnecting from the tether not even an option? Yes, it's risky, but it's way better than mark poking a hole in his suit.
    20
  12. 19
  13. 19
  14. I think you've missed a lot of the issue with systemd (not that I blame you... most people who hate systemd express themselves very poorly). To preface this, I use systemd. I'm just not entirely happy about it, and still on the lookout for something that sets off fewer warning flags in my head. Systemd (the project, not just the init system) takes an approach to low level system management that assumes monoliths are good. Using systemd tends to be an all-or-nothing affair for the most part (not systemd-boot, but that's the exception, more than the rule). If you use one part of systemd, you kind of end up having to use the rest of it, too. The pieces all interlock without understandable, stable interfaces between the components to allow interchanging them. Functionality sprawls across the interconnected pieces, and the sheer quantity of obscure features is downright disturbing to anyone who understands the value of the unix philosophy, and bothers to really look at what's going on. Systemd-init also has a couple of really excellent ideas at its core. The event/transaction system it uses to manage services has changed how people think about ongoing state in their systems in general, and given them a much more powerful language to express how they want their system to behave. The idea of treating many different sorts of system state with the same concept of "units" has a lot of power. The dependency relationships that are possible among units, though not very consistently structured, are very expressive, allowing you to ensure things you had no hope of ensuring before. Having an "init" for each user allows user-level configuration to gain these same benefits as well. It's no wonder it took over, despite the issues. So I use systemd. It has some really nice features, and the cost of using anything else is just really high right now. But I continue to keep my eye out for a solution that gives similar benefits, but is more modular, keeps the agility to replace components fairly painlessly, and avoids lock-in and feature creep.
    17
  15. 13
  16. 12
  17. On the subject of infinity: Strictly speaking, none of rigorous mathematics deals with actually infinite constructs. You fundamentally can't. You can, at most, allow infinitely many possibilities with a finite description of which possibilities are allowed. It's just a matter of how honest you are about what you're really saying. Coming at things from a more constructive perspective often illuminates a little better what supposedly infinite constructs are really about. And playing at the edge of them leads to interesting conclusions which are often misunderstood to say more than they really do, like how observations about the logical contradictions inherent in supposing you can "pair up" possibilities from 2 finitely-describable spaces leads to the declaration that there are "multiple levels of infinity"... which is a much bigger statement, and doesn't really make any sense. The error was in identifying the philosophical notion of infinity with those equivalence classes of "pairable" spaces in the first place. The same goes for non-standard analysis with its "actual infinitesimals". They're no more "actually infinitesimal" than any other "infinite" construct in mathematics. What makes them different from limits is that they're *actually numbers*, not that they're "actually infinitesimal". "What if we could make limits fully behave like numbers, instead of only mostly? And maybe some other stuff like dirac deltas while we're at it?" I'm all in favor of that, and I think it can definitely lead to more intuitive ways of teaching and understanding calculus.
    11
  18. 7
  19. 7
  20. 7
  21. 7
  22. 6
  23. 6
  24. 4
  25. 4
  26. 4
  27. 4
  28. 3
  29. 3
  30. 3
  31. 3
  32. 3
  33. 3
  34. 3
  35. 2
  36. 2
  37. 2
  38. 2
  39. 2
  40. 2
  41. 2
  42. 2
  43. 2
  44. 2
  45. 2
  46. 2
  47. 2
  48. 2
  49. 2
  50. 2
  51. 2
  52. 1
  53. 1
  54. 1
  55. 1
  56. 1
  57. 1
  58. 1
  59. 1
  60. 1
  61. 1
  62. 1
  63. 1
  64. 1
  65. 1
  66. 1
  67. 1
  68. 1
  69. 1
  70. 1
  71. I think the fact that GPLed software can't feasibly be sold actually constitutes a "bug" in the GPL. The explicit allowance of sharing the software should perhaps be limited to only those who have bought a license (this would have to be worded in such a way that redistribution through distro package managers was clearly allowed). The other freedoms the FSF defines could all still be protected in a copyleft manner, and the license could automatically "convert" to full GPL after a set amount of time (initial suggestion: 10 years, though it would probably vary depending on the software). I think it's a reasonable compromise between the freedom of the end user and the need to pay for the development. We could call it something like "user serviceable software." It might catch on among more open-minded commercial software creators. You could also implement license-reminder systems, which, unlike DRM, wouldn't be designed to control what you can do, but just to help prevent accidental violation of the license, by requiring the user to make an actual action signifying that they believe the system is in error and they actually have a license in order to override it. (This would also be important if it was distributed through distro package managers, since users could easily mistake it for free software if they weren't paying attention) Somewhere in this set of ideas I think we can get a solution that actually works for the whole society. Right now, open source software developers are giving their talents away as a kind of charity, and I don't think that's a viable way for software in general to work for the whole society, but we should have a path that is, and is also ethical in regards to how it treats the end user.
    1
  72. 1
  73. 1
  74. 1
  75. 1
  76. 1
  77. 1
  78. 1
  79. 1
  80. 1
  81. 1
  82. 1
  83. 1
  84. I know I'm raising a raising a dead thread here, but I've found a good solution to this problem on nixOS (it should also work when using nix + home-manager on a non-nixOS distro): References (most recent first, but the reasoning of why to do this is explained best in the original one) https://elis.nu/blog/2020/06/nixos-tmpfs-as-home/ https://elis.nu/blog/2020/05/nixos-tmpfs-as-root/ https://grahamc.com/blog/erase-your-darlings I think I prefer having grahamc's approach with snapshots rather than the tmpfs route, since I don't really want to take up system memory, but the idea is this: Delete everything every boot (maybe even more often)... EXCEPT what you have personally decided you want to keep. Using home-manager allows you to declaratively create your static dotfiles from a single central configuration file which you can comment all you like, and follow DRY principles with (it is, in fact, written in a full-fledged programming language), but for the data actually saved and/or manipulated by programs, you can instead add that a file or directory should be redirected to your permanent store. This means that a necessary part of installing and using any piece of software is determining where it saves information, deciding whether you want to save that information, and if so, changing your home-manager configuration to redirect that to your persistant directory, of course with comments to remind you, in your own terms, what program/purpose you're saving it for. Any program that silently adds files to your homedir will just get them obliterated, and so anything that IS there is either something you ran quite recently, or you have a comment about what it's for in your home manager configuration. A nice side effect of this is also that you know your backups work. As long as you back up your persistent area, you're essentially loading from a backup every time you boot. If some state you care about isn't getting backed up, you're going to know it pretty quick.
    1
  85. 1
  86. 1
  87. 1
  88. 1
  89. 1
  90. 1
  91. 1
  92. 1
  93. 1
  94. 1
  95. 1
  96. 1
  97. Sorry for the wall of text, I've had this on the mind for a while and just had to say it. Why postulate many worlds at all, when you can think in terms of knowledge, probability, and correlation? The density operator (wave functions only represent pure states, and thus aren't a sufficiently complete description in my view) represents your knowledge about a system, much like a classical probability distribution (and in fact diagonal density operators are classical probability distributions over the basis states. Also, by choosing an appropriate state basis, any density operator can be made diagonal). The difference from classical probability distributions is that there is no assumption that there are any density operators that make every property of the system definite simultaneously (this is the key idea, take some time to think it over), which also means it's no longer possible to do away with the probability stuff and deal with a single fully definite state instead, since those don't exist. You still get determinism though, in the sense that no information is created (or destroyed, for that matter) through time evolution. Entanglement is just correlation (so no action at a distance), superposition is a result of your knowledge about the system not being applicable to the question at hand (rather than your lack of knowledge, like classical uncertainty), wave function collapse is the change to your knowledge that results from interaction (much like the classical probability distribution for what hand of cards you were just dealt "collapses" when you look at the hand). It's also worth noting that both decoherence and wave function collapse are a result of interaction of the system with things that aren't being modeled, namely the environment and yourself, respectively, so the apparent creation/destruction of information in how we think about those processes isn't real (no "dice" involved, even in measurement). The No Cloning theorem just says that when you run an object through a perfect copier, the outputs will be perfectly correlated (nawww, really? copiers do that?) (and you'll need raw materials about which you have maximal information in order to make the copy too). The No Communication theorem is no surprise since nothing about this whole perspective involves action at a distance. And so on. Once you accept that there are no probability distributions that make every property of a system definite, everything else falls into place quite intuitively. You lose the expectation of definiteness of reality, sometimes called "realism" (that your questions have definite answers, even though you don't know them), but this is a much smaller sacrifice than it might at first seem, since you still have the expectation of coherence of reality (that if you and I have incompatible knowledge about reality, one of us is wrong).
    1
  98. 1
  99. 1
  100. 1
  101. 1
  102. 1
  103. 1
  104. 1
  105. 1
  106. 1
  107. 1
  108. 1
  109. 1
  110. 1
  111. 1
  112. 1
  113. 1
  114. 1