Live data from Hacker News

WoofWare.PawPrint, a Deterministic .NET Runtime

patrickstevens.co.uk

1–10 of 21 posts

Re: WoofWare.PawPrint, a Deterministic .NET Runtime

#5

[flagged]

Apparently the gRPC improvements to use shared memory when client and server are on the same, something common on network RPC not yet supported by gRPC, was done by Mark Russinovich, with agents.

https://github.com/markrussinovich/shmem

It is one example described on one of his AI talks at BUILD.

If the PR gets accepted, here is your AI contribution to core technology.

Re: WoofWare.PawPrint, a Deterministic .NET Runtime

#6
post #2

Something of a passion project. It's going to fail horribly if you try and use it, I'm sure, but it can already do some neat stuff!

[flagged]

because some software engineers enjoy shipping usable software more than writing the code needed to do so?

Re: WoofWare.PawPrint, a Deterministic .NET Runtime

#7

[flagged]

LLM rant aside, I think this comment is built on a fundamental misunderstanding of what this is. This kind of runtime is an advanced debugging tool for exploring extreme edge cases in a repeatable way, not the thing you’d run your production apps on.

Re: WoofWare.PawPrint, a Deterministic .NET Runtime

#8

Earlier quoted context omitted.

[flagged]

because some software engineers enjoy shipping usable software more than writing the code needed to do so?

What does that have to do with LLMs? There's morev to delivering value to the customer than just shipping code. We used to understand that technical debt was an existential risk to a project. I can't see how "code nobody understands" is not technical debt.

Re: WoofWare.PawPrint, a Deterministic .NET Runtime

#10
post #7

[flagged]

LLM rant aside, I think this comment is built on a fundamental misunderstanding of what this is. This kind of runtime is an advanced debugging tool for exploring extreme edge cases in a repeatable way, not the thing you’d run your production apps on.

I mean, if I'm in a situation in which I need more powerful debugging tools than what I already have available, then I kind of want to know those tools have been built with care. If I'm deep in the weeds of trying to deliver and I'm desperately reaching for something outside of the standard tool set, I'd like the person who made that tool to have crafted it in a dwarven forge under a pale moonlight. Not to have thrown to their hands and admit a tool with the intelligence of a smart working dog breed is smarter than them.
Post reply on HN