Crash probably a couple seconds later, wouldn't rely on the video for the exact timing.
So it seems that ATC made an error by allowing the truck to cross, and then the order to stop wasn't communicated clearly enough. I wouldn't place much blame on the truck.
Edit: Looking at some other videos with that audio, I'm also not sure if the video I linked represents the time between communications correctly, transmission at 3:15 may have been right after the one at 3:02. Anyway, the best thing is to wait for the investigation.
IMO putting an important number in your post/comment, and not providing a source for that number, is also kind of low effort. If you verified the number before writing, you already had the source ready and you could just put it in the comment. If you wrote the number from memory, not checking if your memory is correct is low effort (but you can also warn the readers that the number is from memory, that's better). If you're intentionally misrepresenting what the number means in your comment (and giving the source would contradict the meaning of your comment), or just giving a number that "feels right" or a number that you know is wrong, then it's low effort and a lie.
I try to verify important numbers and facts in what I read, and seriously, there's so much fake or misrepresented info everywhere, on every political side, that it's depressing, and it makes me don't believe literally anything without a source, unless I verify it myself. Of course when someone provides a source, I often look into the source, and sometimes it turns out that the text misinterpreted/misrepresented the meaning of the source. On Wikipedia, I also check if what is written is actually in the source, because sometimes the editor writes his own opinion while only loosely basing the text on a source (or basing it on nothing).
Verification can take some time, and that's the effort passed from the author of unsourced claim to its many readers, unless they just trust it or ignore the claim.
When I write anything I try to include sources for important things. If I wouldn't include a source, and someone asked "Source?" I wouldn't think "what an annoying guy", I'd think "oh, I could have linked that in the first place". And I usually upvote "Source?" comments (unless it's a thing that anyone can check in 30 seconds). I usually double-check the facts in what I'm writing, and many times I almost wrote something from memory that wasn't true, but looking for a source saved me from that.
I haven't used them, but IIRC they maintain a constant voltage until they're discharged, when it instantly drops to 0. That may be a problem, because if your device has any battery indicator, it will show the battery as full until the end. Nothing will tell you that you need to replace the battery before the device powers off. That's why I decided not to buy them. My mouse knows when my alkaline AA battery is low and gives me a warning.
I use rechargeable CR123 batteries in my August smart lock that face this issue. The solution is to have a spare set and rotate/charge on a fixed schedule before they die. I have a quarterly calendar reminder to do so.
If you're not sure if there are any important world-writable files, then just check that? On Linux you can do something like "find . -perm /o=w". And you can easily make whole dirs inaccessible to other users (chmod o-x). It's only a problem if you're a developer who doesn't know how to check and set file permissions. Then I wouldn't advise running any commands given by an AI.
Careful, you’re talking to developers now. Chmod is for wizards, Harry. One wouldn’t dream of disturbing the Linux gods with my own chmod magic. /s
Yes, this is indeed the answer.
Create a fake root. Create a user. Chmod and chgrp to restrict it to that fake root. ln /bin if you need to. Let it run wild in its own crib.
Though why bother if you can just put it into a namespace? Containers can be much simpler than what all this Docker and Kubernetes shit around suggests.
How much smaller user base? Looking at some recent data, which may not be accurate (but they're required to publish user numbers in the EU at least), it looks like the user base may be only 0-20% smaller compared to 2022.
Seems that in the end it didn't work out well for them:
> The Hunts lost over a billion dollars through this incident, but the family fortunes survived. They pledged most of their assets, including their stake in Placid Oil, as collateral for the rescue loan package they obtained. However, the value of their assets (mainly holdings in oil, sugar, and real estate) declined steadily during the 1980s, and their estimated net wealth declined from $5 billion in 1980 to less than $1 billion in 1988.
One possible outcome is the remaining memory manufacturers have dedicated all their capacity for AI and when the bubble pops, they lose their customer and they go out of business too.
I wouldn't be too surprised to find at least some of the big ram foundries are deeply bought into the fake money circles where everybody is "paying" each other with unrealised equity in OpenAI/Anthropic/whoever, resulting in a few trillion dollars worth of on-paper "money" vanishing overnight, at which stage a whole bunch of actual-money loans will get called in and billion dollar companies get gutted by asset strippers.
Maybe larger makerspaces and companies like Adafruit, RasPi, and Pine should start stockpiling (real) money, and pick themselves up an entire fab full of gear at firesale prices so they can start making their own ram...
I think there's also option 3, v8 understands types and uses them for optimization, but handles wrong types gracefully.
I don't think any type of understanding TS would require changing ECMAScript spec. Would a TypeScript-understanding parser not be able to handle normal ECMAScript correctly? It could switch between two modes based on the file type.
For option 1 the speed of TS development is not an issue, as Chrome would only need to include some up-to-date compiler, and the TS files could specify their TS version. But doing TS compilation in the browser would only be a small nice thing for devs, for website users it would be a downgrade, as the page load would be slower because of the compiling and the larger file sizes (JS files can already be very big these days).
It's unclear whether you could build a JIT that meaningfully benefits from typescript types.
1. Hidden classes can't be created from TS interfaces because they don't represent the full data of the underlying object
2. You don't really ever want to compile code the first time you see it, because that takes a lot of memory and extra CPU cycles. By the time code has run enough to be worth compiling, you probably have enough profile data to optimize better than you could with data from the types anyway.
3. Many of the juiciest optimizations come from types that aren't representable in TS, like integers.
4. Including all the types for all your code and deps (literally all the .d.ts) is huge, and the size increase alone might nullify any performance benefit.
If you want proper run time type safety you’re going to need a language designed for that which Typescript never was. I write a bunch of Dart which I compile to Wasm and get proper run time type safety in the browser and it works great.
Timestamps from the video:
2:46 Truck requests crossing
2:51 ATC allows it to cross
2:53 Truck confirms
2:58 ATC: "Frontier 4195 stop there please"
3:02 ATC: "stop stop stop stop truck one stop stop stop"
3:15 ATC: "tower, truck one, stop, ..."
Crash probably a couple seconds later, wouldn't rely on the video for the exact timing.
So it seems that ATC made an error by allowing the truck to cross, and then the order to stop wasn't communicated clearly enough. I wouldn't place much blame on the truck.
Edit: Looking at some other videos with that audio, I'm also not sure if the video I linked represents the time between communications correctly, transmission at 3:15 may have been right after the one at 3:02. Anyway, the best thing is to wait for the investigation.
reply