Recent submissions

Comment · 15 days ago
Comment · 2 months ago
Comment · 3 months ago
The incremental linking part sounds pretty hackish to me and I wonder what the price is in increased code complexity and maintenance effort. It also does not mention how it deals with the patching of debug information.
Comment · 4 months ago
Without nuclear, your country will remain vulnerable to:

4) renewable energy disruptions, e.g. supervolcano eruption, large meteor strike

Comment · 10 months ago
Separate compilation is one solution to the problem of slow compilation.

Binary patching is another one. It feels a bit messy and I am sceptical that it can be maintained assuming it works at all.

I think a much better approach would be too make the compilers faster. Why does compiling 1M LOC take more than 1s in unoptimized mode for any language? My guess is part of blame lies with bloated backends and meta programming (including compile time evaluation, templates, etc.)

Comment · 10 months ago
> Unfortunately you can't really statically link a GUI app.

But is there any fundamental reason why not?

> Also, if you happened to have linked that image to a.out it wouldn't work if > you're using a kernel from this year, but that's probably not the case ;)

I assume you refer to the retirement of coff support (in favor of elf). I would argue that given how long this obsolete format was supported was actually quite impressive.

Comment · 10 months ago
Wasn't there also DLL hell on Windows?

My understanding is that very old statically linked Linux images still run today because paraphrasing Linus: "we don't break user space".

Comment · 10 months ago
Shamless plug: http://cwerg.org

Pros: * uses Python and recursive descent parsing * separates front and backend via an IR * generates ELF binaries (either x86 or ARM) * meant for real world use

Cons: * more complex * not written in a tutorial style

Comment · 11 months ago
Comment · 11 months ago
What I am curious about: where zfs checksum failures the only symptom of the bad disks or where there SMART failures as well?
Comment · 1 year ago
Comment · 1 year ago
Each new decoder represents an increase in attack surface which is why not all video/audio formats supported by ffmpeg are enabled in Chrome. This is despite Chrome having ffmpeg as a depency. [caveat: this was the status quo when I last checked a couple of years ago]
Comment · 1 year ago
Comment · 1 year ago
I am puzzled that they not already have moved to the web. Also speaking off the cuff: what are the main reasons for using word documents in government? If it is mostly communication with other parts of the government or the public, shouldn't this be email which requires very little functionality compared to word.

I can see niche cases, like laws where you want change tracking or very long reports but that does not seem to apply to most government employees. Somehow I feel I missing something big, maybe there is a lot of automation built around word documents?

Comment · 1 year ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton