Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Veserv
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
26 ms
·
361.
▲
by
Veserv
1y ago
You cannot build a secure virtualization runtime because underlying it is the VMM. Until you have a secure VMM you are subject to precisely the same class of problems plaguing container runtimes. The only meaningful difference is that Linux
362.
▲
by
Veserv
1y ago
Assuming it did not disengage prior to hitting the pedestrian, no. If the pedestrian is on the ground near the car after the collision, it is very likely it will no longer be able to see the pedestrian and will drive over them: https:/
363.
▲
by
Veserv
1y ago
You have presented no evidence of dishonesty to justify your claim that "this specific individual has been dishonest". The only argument you have presented is asserting the person is dishonest, therefore they must have engaged in
364.
▲
by
Veserv
1y ago
Wow, still just making up random nonsense instead of taking responsibility for your false statements. The video footage in the report was not a "update". That is the original video footage of the tests that was released at the sam
365.
▲
by
Veserv
1y ago
So your argument was: > It was not engaged. But since that is now clearly false using the evidence you yourself presented you have transitioned to: "The raw video footage clearly demonstrates the claim of FSD colliding with the chil
366.
▲
by
Veserv
1y ago
Can you at least read to the end of the article you post as evidence before making demonstrably false claims? "Update: The Dawn Project has since released additional footage that doesn’t appear in its ad where we can see that they were
367.
▲
by
Veserv
1y ago
The "warning message" claim is a lie. The message that appeared on screen was "Supercharging unavailable - Add Payment method" as can be seen in this video [1], "Paid charging unavailable - Check unpaid balance"
368.
▲
by
Veserv
1y ago
Nope. That was a smear campaign. The "reporter" did not even watch the linked raw footage which shows that FSD was, in fact, engaged and that "reporter" was a Tesla promoter who referred $15,000,000 in sales and earned $
369.
▲
by
Veserv
1y ago
It is, in fact, illegal for a human to drive in California with vision comparable to the Tesla HW3 cameras. California minimum vision requirement to operate a vehicle is 20/40 vision [1] which corresponds to a arc resolution of 30 pixe
370.
▲
by
Veserv
1y ago
When it is objectively not a time travel debugger as prominently advertised, let us not stay mindlessly positive.
371.
▲
Self-driving Tesla fails school bus test, hitting child-size dummies
(fuelarc.com)
8 points
by
Veserv
1y ago
|
0 comments
372.
▲
by
Veserv
1y ago
Wow. It is not even a proper time travel debugger. I just assumed they were ingesting a proper time travel debugger log and driving a proper replay engine and just wrote a bad integrated trace viewer on top. That would at least be excusable
373.
▲
by
Veserv
1y ago
That is exactly how trace viewers have been used with time travel debuggers for literally, and I do mean literally, over 20 years. You click a point in the trace, you jump to that point in time. That has been the standard integration for de
374.
▲
by
Veserv
1y ago
This is just a trace viewer. Except the trace visualization is vastly less dense than any standard trace viewer and seems to provide no meaningful execution time information. Compare to chrome://tracing https://www.chro
375.
▲
by
Veserv
1y ago
One of the main problems is that the apportionment of liability is lossy. It is fairly easy to determine that a collective, as a whole, is liable for some action. However, it is very hard to determine the culpability of any specific individ
376.
▲
by
Veserv
1y ago
Time travel debugging on embedded ARM has been available for over 20 years via trace probes [1]. The category namer of time-travel debugging, TimeMachine, (hence time-travel debugging in contrast to other attempted names such as reversible,
377.
▲
by
Veserv
1y ago
I presented a conditional calculation using numbers contextually-relevant to a forum run by a company that funds US tech startups. IF you are such a company, THEN you only need very minor productivity improvements to justify such a pric
378.
▲
by
Veserv
1y ago
Ugh, it appears I was not utterly pedantic enough even though I did, quite clearly, make my statements conditional in a way far beyond what is normally expected when talking about generalities that any normal person would assume are meant
379.
▲
by
Veserv
1y ago
If you have a US employer who is unwilling to spend 8 k$ on software engineering productivity then they are pennywise, pound foolish. It literally costs 10x that for a single junior engineer. And, as I pointed out, the net productivity im
380.
▲
by
Veserv
1y ago
Well, if you have a Google L5 making ~365k [1] then it would need to make them ~2.2% more productive overall to be worth it when just considering direct pay. If we consider a Google L3 at ~187k then it would need to make them ~4.2% more pro
381.
▲
by
Veserv
1y ago
I do not understand how the implementation [1] and claimed performance make any sense. In try_protect() (page 11) they only issue a load with acquire semantics (L-LS after load). The hazard pointer store, which is the actual guard, is not o
382.
▲
by
Veserv
1y ago
Domestic solar is a rapidly decreasing fraction of total solar deployments [1]. Not because it is not growing exponentially, but because grid-scale is much more exponential with no signs of that changing. [1] https://news.ycombin
383.
▲
by
Veserv
1y ago
The difference between a flame graph and a trace visualization is that a flame graph is a aggregate/summary visualization. It helps visualize total runtime attributed to functions. It is like the difference between seeing the mean of a
384.
▲
by
Veserv
1y ago
That speculation is trivially incorrect. ARM had a revenue of 3.2 G$ in 2023, 2.7 G$ in 2022, 2 G$ in 2021.
385.
▲
by
Veserv
1y ago
Any price advantage, even if we assumed a fully mature ecosystem with equivalent processors and systems available, is massively overstated. ARM had a total revenue of just ~3.7 G$ in 2024 over ~29 billion chips [1]. In contrast, Qualcomm, j
386.
▲
by
Veserv
1y ago
I think I was quite clear on my position. > In the case of Waymo, we have some tentative supporting evidence from this and other studies Waymo has run. However, that is still insufficient, even ignoring the lack of audits by non-conflict
387.
▲
by
Veserv
1y ago
I think I was pretty clear. > You do not get to counter-argue: “What matters is the rate of cases per mile driven” without actually presenting that number with supporting evidence. Otherwise the only sound conclusion is the default presu
388.
▲
by
Veserv
1y ago
For which any such system must be assumed unsafe until proven safe and the burden of proof lies with the manufacturer to present sound, robust, transparent, third-party audited evidence. You do not get to counter-argue: “What matters is the
389.
▲
by
Veserv
1y ago
Flame graph, as in a display of sampled call stacks growing upward organized per level to aggregate like call stacks, is almost certainly their invention. Why they chose that over the much more common visualization of downward call stacks t
390.
▲
by
Veserv
1y ago
He did not baselessly claim a critic was a pedophile. He baselessly claimed the first foreign rescuer called to the scene [1], who called in his friends who successfully navigated and mapped the caves and found the kids, a pedophile. [1] h
More ›