plq

Joined 16 years ago

Karma

1,366

Submissions

411

Member since

Apr 2

github.com/plq [email protected]

View on Hacker News

Recent submissions

Comment · 17 days ago

> Quake II (a slight improvement over Quake)

That colored lighting, though.

Comment · 24 days ago

Both Firefox and Chromium have battle-tested cross-platform sandbox implementations, but I imagine it'd be laborious to integrate them as a third-party dependency to other projects. Why not spend resources on repackaging them in an easy-to-use SDK instead of reinventing the wheel?

Microsoft is already a Chromium contributor so it's not like they lack in-house expertise or something.

https://wiki.mozilla.org/Security/Sandbox

https://chromium.googlesource.com/chromium/src/+/HEAD/docs/d...

Comment · 1 month ago

Haha so this project speaks IRC, no less :) This is surely relevant then: https://www.mirc.com/split.html

Comment · 4 months ago

With Gerrit, you have the patch that lands on master and then you have the stages that that patch went through to get to that point, reviews on older versions of the patch, etc. all recorded in the web interface.

So maybe just switch to a code review tool and use its interface to converse with the bots?

Comment · 4 months ago

I don't get this. No I did not write that code but I paid money to eg. Anthropic to buy that code. To me it sounds like I own it just the same.

Comment · 7 months ago

ninja supports separate build groups and different max number of parallel jobs for each. CMake's ninja generator puts compilation and linking steps in their own respective groups. End result is by default `nproc` parallel jobs for compilation but 1 job for linking. This helps because linking can be way more memory intensive or sometimes the linker itself has support for parallelism. Most projects have only a handful of linking steps to run anyway.

Comment · 8 months ago

Certificates need expiration dates to be able to garbage collect certificate revocation lists.

Comment · 10 months ago

Sure but you have to learn to use it. I'm saying that just have AI generate a SvelteKit project instead and you'll get better mileage out of it.

Comment · 10 months ago

My impression is that tools that grew complex only because they want to serve every use case under the son got obsoleted by AI, and static site generators like Hugo are a good example.

Today, if I were setting up a blog to host just some text and images, a vibe-coded SvelteKit project using the static adapter[1] would easily solve every single problem that I have. And I would still be able to use the full power of the web platform if I need anything further customized.

[1]: https://svelte.dev/docs/kit/adapter-static

Comment · 10 months ago

Type inference is when you try to infer a type from its usage. ``auto`` does no such thing, it just copies a known type from source to target. Target has no influence over source's type.

https://news.ycombinator.com/item?id=11604474

Comment · 11 months ago

ICE meaning in-circuit emulator in this instance, I assume?

Comment · 1 year ago

The (non-existing) license doesn't say it was to be "published in the web"

Comment · 1 year ago

> What's stopping the rogue node from saving all your stuff forever?

Nothing. You must always have this in mind when posting online: It's impossible to ensure that data is deleted and gone forever.

Comment · 1 year ago

> Again, this just isn't true.

Again, it just is true.

More fs-related operations mean less kthreads available for others. More syscalls means more OS overhead. It's that simple.

Comment · 1 year ago

More system calls mean more overall OS overhead eg. more context switches, or as you say more contention on internal locks etc.

Also, more fs-related system calls mean less available kernel threads to process these system calls. eg. XFS can paralellize mutations only up to its number of allocation groups (agcount)