On: Practical File System Design: The Be File System (...

[dmolony]

Please put [PDF] in the title.

[beefhash → dmolony]

Normally HN does that automatically if a link ends in .pdf, but there's a GET parameter here (m=1) that prevented it from working.

[deathanatos → beefhash]

That HN doesn't parse out the path prior to checking if it ends in .pdf fills me with warm and fuzzies.

[savoytruffle → dmolony]

Out of curiosity, why is this still something people desire in a link? Can't any modern browser pretty much open a PDF as quickly easily as a web page?

[exikyut → savoytruffle]

Principle of least surprise. Web browsers primarily display web pages.

[zootboy → savoytruffle]

I personally have PDF rendering disabled in browser for security, just as I have JS disabled by default. So no, my browser cannot display a PDF at all.

[pinum → zootboy]

To be fair- if you turn off standard features, you can't complain when you get a sub-optimal experience.

[mulmen → pinum]

PDFs are a sub-optimal experience. Putting [PDF] in the link just saves me from wasting the time of clicking.

[jimktrains2 → savoytruffle]

Mobile will download and store on the device.

Web pages are quite large anymore and most can be larger than a PDF when delivering less content, so I don't know if there is a size issue anymore.

[pinum → jimktrains2]

iOS shows it inline. Android can do too; it usually starts a download instead but IMO that's the browser's fault (should default to embedded).

[jimktrains2 → pinum]

Is it really a matter of fault when the original question was 'who doesn't not 'why don't they'?

[Crontab → savoytruffle]

Personally, I feel it is simply good courtesy.