Like yeah, this stuff might be irritating. Maybe you wanted pinker shutters. But who really cares? Imagine getting bent out of shape about the color of your shutters or having to put up curtains.
691 karma · joined January 14, 2019
Like yeah, this stuff might be irritating. Maybe you wanted pinker shutters. But who really cares? Imagine getting bent out of shape about the color of your shutters or having to put up curtains.
What strikes me as the issue is that he identifies literally anyone who may level any criticism at him as acting in bad faith: purely participating in a game of status and an inferior one at that.
Not only is it really unlikely that literally everyone who might have a different set of priorities than him is a crass social climber, but his need to describe them as such is immature, even if it were the case.
Despite its central presence in physics 101 the notion of force is actually not all that clearly present in fundamental physics.
Newton's innovation might be said to be the representation of gravity as a force, but even in the Principia he doesn't commit to the idea because of an intuitive rejection of the non-locality implied by such a conception. So the idea that gravity is a force of the same sort as you pushing on a cart full of apples (whatever _that_ is) was never a particularly strongly held idea. I'm not an expert on the history of physics (I have read the Pricipia in translation, though) and I suspect Newton, if questioned appropriately, might have himself admitted there are issues with the conception that go beyond just non-locality.
Even at the level of Lagranian physics in the contemporary style (which despite that description is hundreds of years old) the idea of forces has an ad-hoc quality to it. The description of a completely closed system doesn't really contain forces unless you explicitly include them in the form of lagrange multipliers for the constraints, and then the forces that you calculate are, in a sense, provided "externally" by processes outside of the system itself.
For instance, the easiest way to represent the motion of two particles held together by a perfectly rigid rod doesn't mention the force exerted by the rod to maintain that constraint and yet simulates the motion perfectly. If we are interested in how much force the rod must exert to maintain the constraint, we can add in a largrange multiplier, but what that quantity tells us is in a sense a summary of the non-represented physics of the rod itself, which is still excluded from the system. A force then is a kind of interface between that which you are considering in detail and that which is assumed to be part of the external world. If everything in the world were simulated, then nothing would deviate from its expected motion, and thus there would be no forces at all, since all a force is is a description of how something deviates from the path it would ordinarily take if not for the intervention.
On this view Newton's first law is much more important and fundamental than his second: objects always move in straight lines but we must take great care in understanding what a straight line actually is for a given physical system. Really, the seed of general relativity and the geometric formulation of field theories is right there in the first law. This explains why the second law is of so much less importance in modern physics.
I'm not a professional, just an interested failed physicist, so standard equivocations apply to the above.
This video by an actual professional hits on some of these ideas:
The problem with decoherence is that the underlying physics of the wave function is still profoundly non-local in the sense that regions of the wave function don't have a simple relationship with regions of physical space.
And yet, classically, the notion of locality pertains precisely to physical space and is deeply related to fundamental physics. In fact, locality is still fundamental to the formulation of quantum mechanical theories, even if the quantum mechanical description ends up having some non-local features. And there isn't any philosophical or physical intuition that resolves this disconnect.
Decoherence has a variety of other philosophical issues. In particular, it requires that we accept the idea of the wave function (something we never see or interact with directly, for which we have no direct evidence) as fundamental and real AND that we take our day to day experiences, upon which all of our physical sciences are based, as derived, perhaps even, in important ways, not really real. In any case, the actual theoretical terms in which decoherence actually resolves the measurement paradox aren't fully understood either mathematically or in terms of the fundamental ontological status of things.
In any case, quantum field theories are good at predicting stuff but almost certainly not descriptions of the true fundamental dynamics of the universe, given their known and relatively well understood divergences.
The sequence of diffs is much, much, more informative than the current state of the software.
The key differences is how traceable and repeatable the process is.
The best way to understand why I hate notebooks is to contrast them with my workflow: when I do data science, each step in the process is represented by a Makefile target which lists its products and its dependencies explicitly. All products are represented as concrete objects on disk (json, csv, figures, or serialized representations in some form).
If I need to do reporting, its typical for various targets to generate fragments of latex and for the report (a pdf) to explicitly document which fragments of latex and which figures belong in the report.
Them a simple `make report.pdf` is enough to generate the final result. If I change something I can explicitly see which pieces need to be rebuilt and how.
I also believe that the structure of a notebook, which mixes code and reporting, encourages bad software design practices like copy-pasting - it doesn't naturally encourage refactoring of shared code into libraries or anything like that. Most jupyter notebooks are just a pile of shit, basically. The big problem is that all the cells in a notebook share one, big, mutable, global state. This is wrong.
They also don't work well with git, which I view to be the absolute crux of any successful technical project.
I'm a data scientist and I hate them.
I, personally, hate it. Its depressing to see a technology so full of promise (seem to, anyway) regress. Become less magical, less useful. Its no wonder young people are skeptical of capitalism - it seems to literally be eating the goose. Not even the goose that laid the golden egg - just the goose, in hopes there might be a golden egg inside.
Ruby, in contrast, seems like an absurdly complicated concatenation of weird features and strange syntax. When I look at Ruby my eyes glaze over with all the unnecessary syntactic doodads and peculiar abstractions. Why anyone would want to complicate their lives with all that silliness is beyond me.
And yet Scheme languishes and Ruby, for a time, anyway, burned brightly. I'm clearly the weird one.