Your example contradicts your point. Airliners are still subsonic after an extended period of time, and hence based on that past performance it's a good indicator (although not definitive) that they will remain subsonic for an extended period into the future.
In general, past performance is actually indicative of future results. It's not definitive, and some phenomenon are random, but the trajectory of technology over time is not some random fluke that just has coincidentally trended by random chance.
>Your example contradicts your point. Airliners are still subsonic after an extended period of time, and hence based on that past performance it's a good indicator (although not definitive) that they will remain subsonic for an extended period into the future.
There was a period in aviation development when it was widely assumed that speed will continue to rise. Just like in the development of CPUs there was such a period, quite recently.
That's a general argument but doesn't apply Anthropic's Lean formalization. There is already a well established Lean statement of the RH in Mathlib that has been pretty rigorously verified, so a proof of that statement is indeed a proof of RH. The only opportunity for failure is that there is a soundness bug in Lean itself which this formalization leverages. The answer to that is that there isn't one single Lean, there are multiple implementations of Lean and each of them have their own opportunities for bugs, so it's possible one bug is common to all of them and that this proof makes use of it, but that's incredibly unlikely.
Do you NEED 15M lines? No, it's almost certain this proof can and will be reduced, but the goal of an initial proof of a theorem like this isn't conciseness, it's to actually... prove the theorem.
Fermat's Last Theorem was initially proven in Lean in September and that proof required 13M lines, it has since been reduced to 2M lines and it will likely be reduced even further. Anthropic claims they can reduce it down to less than half a million lines by doing similar techniques to what software developers do... find common and reusable snippets and factor them out instead of repeatedly proving similar sub-theorems over and over again. There are also opportunities to replace lengthy sequences of explicit reasoning with automated tactics, reuse existing mathematical libraries including the Lean standard library, and reformulate arguments at a higher level of abstraction.
This is a subtle misunderstanding. As you approach the speed of light, physical processes including clocks or other time measuring devices appear to slow down relative to an observer. Exceeding the speed of light, at least as a conceptual generalization, doesn't mean that you end up going back in time and experiencing past events like Back to the Future, rather it would allow for future events to influence the outcome of past events, what is called retrocausality [1].
Retrocausality is not the same as time travel. With time travel it's as if you get to go back in time and reexperience things that happened in the past, which is not what faster than light travel implies. Retrocausality is more about things happening in the present that are influenced by future events, as opposed to causality where only past events can influence the outcome of future events.
Not sure how superposition has any role in this. Sound waves also obey the principle of superposition but sound travels faster downwind than upwind, even though the medium is the same in both directions. So superposition clearly doesn't establish that wave propagation speeds must be identical in all directions.
Sound is a longitudinal wave, the medium velocity is additive to the wave's propagation. Light radiates i.e. it does not require a medium to propagate.
Both longitudinal and transverse waves obey the principle of superposition, yet superposition alone tells us nothing about whether propagation speed is the same in every direction. You're introducing additional properties of electromagnetic waves to justify a conclusion that you originally attributed to superposition.
Superposition has nothing to do with this and does not give any insight into whether the speed of light is the same in all directions.
Usually when people are introduced to the issue of measuring the one-way speed of light, one of the first ideas that comes to mind is exactly what you suggest, and it's a very good first thought, but of course it doesn't work since implicit in your approach is an assumption about what the one-way speed of light already is.
As you "slowly" move the two clocks away from one another, the two clocks will no longer be synchronized due to time dilation, and so you need to account for time dilation, but in order to account for time dilation you need to already know what the one-way speed of light is.
I put "slowly" in quotes because why would it possibly matter whether you move clocks slowly or quickly? It's the principle of the matter that is at issue, not the practicality.
> As you "slowly" move the two clocks away from one another, the two clocks will no longer be synchronized due to time dilation, and so you need to account for time dilation, but in order to account for time dilation you need to already know what the one-way speed of light is.
That's why I said "slowly" so that the effect of the time dilation can be kept negligible. If you insist that you MUST account for it, get an additional clock that you move at a different velocity. It'll provide you another data point for the system of equations that you can solve to get the "c" value.
You can measure velocity precisely without any reference to the speed of light by timing how long (according to the clock itself) it takes for it to traverse a given length.
To make it even more watertight, do the experiment in an inertial reference frame with pre-accelerated clocks. Launch two clocks with arbitrary but different velocities along a race track. At the start of the track you have the pulse source along with the reference clock, you synchronize with it as your moving clocks cross the starting line.
Then you measure how long it takes for each moving clock (according to its measurement!) to cross the finish line. This will provide you enough data to solve the equation for the time dilation.
This article has a stronger statement: that it's impossible to measure one-way the lightspeed without doing clock synchronization or assuming that the unit length stays the same regardless of the direction it's traversed.
So in my example, the measurement stick that I'm using to mark the race track, might theoretically have different lengths if traversed from south to north or from north to south.
And I believe that this experiment is still possible to do, although not in the special relativity. You need to traverse the same path in a gravity field and compare the accumulated time dilation. It will depend on the absolute distance travelled.
Not just light, it's impossible to know if the speed of anything is constant in all directions. The so called one-way speed of an object depends on a synchronization convention used for clocks at different locations. Different conventions can produce different one-way speeds while leaving all other observable physical phenomena unchanged.
"A lede is the introductory section in journalism and thus to bury the lede refers to hiding the most important and relevant pieces of a story within other distracting information."
Burying the lead in the journalism would actually be burying the lead (like the metal) so they aren't even pronounced the same. Many people make the same mistake you do so this misconception proliferates.
Fog Creek of 2012 was a pretty different company from the Fog Creek in the early 2000s. While Joel was still technically in charge he had mostly delegated responsibities and spent almost all of his time working on Stack Overflow.
But was "early Joel" FogBugz any good? I heard that it wasn't from somebody who tried it. That unsuccessful trial was also the only time I heard of anyone using it.
Waaay back in 2007ish I got Fogbugz for the small 3-man IT team that we were. As a small team hacking away on an internal ERP and minimal other apps, it was actually refreshing. In my prior role I'd used BugZilla and it was ok, but Fogbugz seemed pretty sweet for a small team. I've now been plodding away with Jira for many years and it's just feature-bloated slowness I'd go back to FogBugz in a jiffy.
Ubuntu is the only Linux distro with an LTS release that has not patched this issue, so saying this is a problem with LTS distro kernels in general is categorically false.
A large number of security issues are not backported to stable or LTS kernels.
A patch containing a new feature which tangentially fixes a security issue is merged to mainline. It will not get merged into stable or LTS (by definition).
To the extent that you've made specific claims, they are false. It's hard to argue with vague claims about tangentially fixing a security issue but at any rate just looking over LTS releases, they absolutely and frequently do backport security issues to LTS releases. They don't do it for every security issue, but the idea that they rarely do it or only do it as part of a tangential change is once again... categorically false.
In general, past performance is actually indicative of future results. It's not definitive, and some phenomenon are random, but the trajectory of technology over time is not some random fluke that just has coincidentally trended by random chance.
reply