My M4 Max 128GB ... 90% of the time is like you say.
10% of the time, Windowserver takes off and spends 150% CPU. Or I develop keystroke lag. Or I can't get a terminal open because Time Machine has the backup volume in the half mounted state.
It's thousands of times faster than the Ultra 1 that was once on my desk. And I can certainly do workloads that fundamentally take thousands of times more cycles. But I usually spend a greater proportion of this machine's speed on the UI and responsiveness doesn't always win over 30 years ago.
If you take actions to deliberately weaponize your product against children in particular, whatever it is -- you shouldn't be surprised when liability attaches. That's what this verdict is about.
On the flipside, look at the success of TCAS. It doesn't have a perfect operational history. It hasn't completely eliminated midairs, either. But it took a relatively rare event and further reduced the frequency by about a factor of 5.
I wouldn't be so quick to rule out that there's some kind of relatively easy technological double check that could greatly reduce incidents. The fact that we've not gotten there despite years of effort to reduce runway incursions doesn't mean that it's not possible.
Yeah but TCAS works inside each airplane. ATC (and ground operations) require coordinating across multiple types of aircraft, at airports across the world, with high precision AND humans in the loop (there are A LOT of edge cases).
This is a REALLY hard problem that the US cannot solve alone. It would require extensive global coordination.
Not insurmountable, but this is not something you can easily roll out piecemeal. If even a single aircraft lacks the compatible equipment you're back to the existing system.
TCAS is fantastic - absolutely stellar example of effective automation.
But calling a replacement of major ATC functions with software a "simple fix" is a perfect illustration of why this is a bad idea. Nothing about human-rated safety-critical software is simple, and coming at it with the attitude that it is? In my view, as an experienced pilot, flight instructor, spacecraft operator, and software engineer, that thinking is utterly disqualifying.
Besides, there already are a lot of "simple" fixes in place for this problem, e.g. RWSL, which didn't prevent this accident.
I don't know. At some point, you need to do all the systems engineering. But "why not just ......" is a perfectly reasonable place to start looking at a problem and sometimes the answers really are that simple.
> Besides, there already are a lot of "simple" fixes in place for this problem, e.g. RWSL
It'll be interesting to hear why RWSL didn't help, as it is supposedly deployed at LGA.
Looks like RWSL did indeed warn for this accident. So maybe RWSL needs to be made more obnoxious (or just speakers in ground vehicles that blare when you're approaching a red RWSL threshold).
And, of course, training to really actually comply with RWSL.
There's a lot of similar history from early TCAS where it failed to save the day because of human factors, training issues, and tuning.
There are three categories of runway incursion types: operator/ATC error, pilot error, pedestrian/vehicle. Even if someone 'knows' that they need to "hold short runway 12", they can still have a brain fart and go through the hold short line.
Unless you want to argue that all vehicles taxiing have to operate (SAE Level 4) autonomously?
What you describe is a software Advanced Persistent Threat and not a "spy chip" as reported by Bloomberg. People have been reverse engineering firmware since forever, no any evidence of booby-trapped firmware was found or reported.
Us splitting hairs is moot: the claims of subversion - whether by sw or hw - were unsubstantiated and uncorroborated, and remain so to date.
Run continuously, non-delayed, but only sweep the order book at a random time every [1,2) seconds. Run for something like our current extended market hours.
Everyone gets the benefit of fast-enough execution and strong liquidity.
Crazy high-frequency gamesmanship goes away. Smart quantitative plays are still possible.
Diversifying away from NASDAQ-tracking index as a component of my investments will be extremely tax costly. Maybe more costly than the gavage (as the NASDAQ/SpaceX folks seem to be betting).
And most people won't even be informed that this is happening.
Large markets need to be run in the public interest...
> high-bandwidth, low-latency mesh network in a contested electronic environment.
Hard to win at jamming, when you're further away and the opponents are frequency agile.
1. They can use directionality more effectively to their advantage
2. Inverse square law works against you (unlike e.g. jamming GPS where it works for you).
3. They can be frequency agile, strongly rejecting everything outside of the 20MHz slice they're using "right now"-- and have choices of hundreds of those slices.
Fighters already have radars that they expect to "win" with despite that being inverse fourth power, a longer range, and countermeasures. They can send communications-ish signals anywhere over a couple GHz span up near X-band. Peak EIRP that they put out isn't measured in kilowatts, but tens of megawatts.
My concern is less total link loss than what happens under degraded or intermittent connectivity. If the wingman still depends on the manned aircraft for tasking or weapons authority, then the interesting question is how it behaves when the link is noisy rather than gone.
Sometimes something good (ATT). Sometimes something bad (this terrible age-verification thing that is a huge barrier to entry for small entrants and comes with massive state surveillance risk).
In the end, all the little people are just collateral damage or occasionally they get some collateral benefits from wherever the munitions land.
If ATT had been applied uniformly, sure. But Apple has exemption from its own rules. So, less trickle down benefit, and more tilting the playing field wildly in their favor. Its new advertising system is doing great!
I don't think the online advertising field is tilted "wildly in Apple's favor". Yes, Apple squeaked out one area of advantage, eliminating some crushing abuse by others in the process.
In a sane world, no one would have the kind of market power that so much hinges upon their competitive actions.
Personally I've lived in the world of "small entrants" and can see that but I think the average voter doesn't really understand that "just anybody" could have created an online service. That is, they think you have to have VC money, be based in Silicon Valley, have to have connections at tha pp store, that it's a right for "them" and not for "us".
> Cost of enforcement matters. The exact same nominal law that is very costly to enforce has completely different costs and benefits then that same law becoming all but free to rigidly enforce.
Hey, I really like this framing. This is a topic that I've thought about from a different perspective.
We have all kinds of 18th and 19th century legal precedents about search, subpoenas, plain sight, surveillance in public spaces, etc... that really took for granted that police effort was limited and that enforcement would be imperfect.
But they break down when you read all the license plates, or you can subpoena anyone's email, or... whatever.
Making the laws rigid and having perfect enforcement has a cost-- but just the baseline cost to privacy and the squashing of innocent transgression is a cost.
(A counterpoint: a lot of selective law enforcement came down to whether you were unpopular or unprivileged in some way... cheaper and automated enforcement may take some of these effects away and make things more fair. Discretion in enforcement can lead to both more and less just outcomes).
This is my problem with Americans and their "but the constitution" arguments.
The U.S. constitution has been written in an age before phones, automatic and semi-automatic rifles (at least in common use), nuclear weapons, high-bandwidth communications networks that operate at lightning speed, mass media, unbreakable encryption and CCTV cameras.
The problem is that "all sides" agree that if the constitution was written today, surprise, surprise, it'd totally agree with them; the gun control people are sure that the 2nd wouldn't cover military weapons, the gun lovers are sure that it would mandate tanks for everyone.
But since having 300 million people have a detailed, nuanced discussion about anything is impossible, everyone works at the edges.
I think their point was that a lot (but not all) of the existing argument boils down to “Well it should be that way because someone decided it hundreds of years ago” so if we are consciously starting again from scratch, ideally that specific argument no longer holds water. (I’d say we should instead use data based approaches, look at what has been successful in other countries, etc, although that’s slightly expanding the current topic.)
One big difference between the UK's historic constitutionalia and the US is that the UK generally recognises that we only do things a certain way because agreeing how to change them is too hard, while the US appears to think that they do things in their certain way because that's the right way to do them.
Specific examples for the UK: inducting politicians into the Privy Council in order to qualify them for security briefings, Henry VII powers, and ministers' authority deriving from the seal they're given by the sovereign. Which would almost make as much sense if it were a marine mammal as it does being a stamp.
The thing being, they work well enough. And if you want to replace them, you need to work out what to replace them with and how.
Modern democracy starts to make a lot more sense when you realize the driving principles are "what works easy enough" and "how do we prevent getting to the point of violent revolution".
10% of the time, Windowserver takes off and spends 150% CPU. Or I develop keystroke lag. Or I can't get a terminal open because Time Machine has the backup volume in the half mounted state.
It's thousands of times faster than the Ultra 1 that was once on my desk. And I can certainly do workloads that fundamentally take thousands of times more cycles. But I usually spend a greater proportion of this machine's speed on the UI and responsiveness doesn't always win over 30 years ago.
reply