dcrazy

4 ms·

31.
by dcrazy 1mo ago
There’s a big gap between spec’ing an SoC by configuration code, and designing one from the ground up. That difference amounts to who, if anyone, gets the credit for being competitive with Apple.
32.
by dcrazy 1mo ago
If that second link is an in-game map, it is far from accurate to the real world. Unless it’s from a timeline in which Golden Gate Park is connected to the Presidio, and half of SF has fallen into the ocean.
33.
by dcrazy 1mo ago
The photogrammetry appears to be from Apple Maps.
34.
by dcrazy 1mo ago
Congratulations, you’ve rediscovered mainframes.
35.
by dcrazy 2mo ago
MCP is essentially just a convention for APIs that standardizes the concept of a “resource”. It spares the LLM a lot of work figuring out what the “things” are in a problem domain, and how various endpoints relate to those “things”.
36.
by dcrazy 2mo ago
Critical to the story, he wasn’t an employee. He’s a rideshare driver, and therefore an independent contractor. That gave him the flexibility to just stop accepting rides for years, but it also meant he had no legal job protection or intern
37.
by dcrazy 2mo ago
A push containing 100 commits is more expensive than a push containing 1 commit.
38.
by dcrazy 2mo ago
I wasn’t being completely serious with my suggestion, but I was thinking of a totally PAYG model. Monthly plans could come with credits, like they already do for Actions.
39.
by dcrazy 2mo ago
The root cause analysis is separate, but linked to from the blog post: https://www.githubstatus.com/incidents/zkxwbgr0cnmx It is specific and technical.
40.
by dcrazy 2mo ago
Pay per issue and commit. Buy 1,000 commit credits at a time. Might force people to review their slop before pushing it.
41.
by dcrazy 2mo ago
But then people like OP will claim that the capacity concerns are a lie manufactured to support an unjustified move to Azure.
42.
by dcrazy 2mo ago
I don’t owe you anything, much less a separately sourced counterargument. You openly admit that your opinion is not based not on GitHub’s proffered statements but on your self-admitted assumption that GitHub is actively lying in an attempt
43.
by dcrazy 2mo ago
Baseless accusation made from a position of zero information.
44.
by dcrazy 2mo ago
You’re torturing your own logic to make Azure the villain here. And it also sounds like you lack experience with capacity exhaustion. Things fail slowly, then suddenly.
45.
by dcrazy 2mo ago
> We installed as much hardware as available power allowed in our existing data centers while accelerating our migration to Azure. And from the RCA [1]: > The immediate cause of the failure was network saturation on load balancers in
46.
by dcrazy 2mo ago
The article clearly states the module was not shipped back to the customer.
47.
by dcrazy 2mo ago
Playing with the example, the controls points don’t feel any more intuitive to work with than traditional cubic Béziers. They still exhibit annoying behaviors near the endpoints, though they don’t tend to “explode” like traditional cubics.
48.
by dcrazy 2mo ago
Eh? “Generate an approximation and refine it algorithmically” is a well-known technique.
49.
by dcrazy 2mo ago
What proprietary models does Cursor offer? Do they have any of the infrastructure to develop, train, and refine a frontier model?
50.
by dcrazy 2mo ago
I wonder if the author asked an LLM to turn his Black Hat talk track into a blog post. I can’t imagine prompting an LLM to produce a post this organized and fact-dense (if stilted in tone) would be any quicker than just writing it up myself
51.
by dcrazy 2mo ago
Ultimately, yes, this seems to be a memory controller register that should not be exposed to ring 0 or above. Ring -1 needs DRAM, so it tells the memory controller to give it some blocks. The memory controller hands back a “physical” addres
52.
by dcrazy 2mo ago
I got suspicious but decided it wasn’t AI. The “Foo is the bar.” sentence construct is coherent with the overall “through the looking glass” tenor.
53.
by dcrazy 2mo ago
The blog post answers your question directly: > For example, you might install network drivers to support your Windows programs. You might choose this option instead of installing them globally because you don’t care about networking for
54.
by dcrazy 2mo ago
I love Raymond’s periodic peeks into how Windows/386 and later were not just shells atop DOS shells, as they are often derided.
55.
by dcrazy 2mo ago
What did the software engineers hope to learn from this tour?
56.
by dcrazy 2mo ago
I can’t believe I have to say this, but… not all dogs bark at strangers. This is highly breed- and dog-dependent.
57.
by dcrazy 2mo ago
That’s the opposite bet from what the bar owner placed.
58.
by dcrazy 2mo ago
I’m not a lawyer, so I can’t give you an authoritative explanation of the difference between insurance and gambling. But I would guess one factor is that the insurance payout is somehow tied to the actual loss. Kalshi is clearly not an insu
59.
by dcrazy 2mo ago
It’s not a bad thing to reinforce our intuition against the risk of incorrect anthropomorphization.
60.
by dcrazy 2mo ago
Insuring against loss. I just looked up the official name; it’s called prize indemnity insurance. In the case of those “make a free throw from half court and win a car” competitions, the risk is a known value: the prize sponsor’s wholesale

More ›