HNHacker News
TopNewBestAskShowJobs

nearbygoogler

15 karma · joined January 30, 2023

submissionscomments
nearbygoogler··on Programming book authors: put all the code in the book
I don’t know, still seems feasible. High quality full page images can be printed at ~2500x3500 pixels per page [1] (random print shop from the internet, but representative AFAICS), and that’s just what printers recommend for human readable images, they can produce images easily to 1200 DPI.

In another example, take the Machine Identification Codes (MIC) tracing dots that basic home printers can produce [2], (I bet the publishing industry could do much better to produce a high density grid.)

These dots have a stated diameter of 0.1 mm, and on an 8”x10” area one could get a grid of 80x25.4x25.4x(1/0.1mm)x(1/0.1mm)= ~5.1M dots.(wikipedia claims larger spacing, but that must be the protocol, printing itself allows for highly precise positioning) And that’s just for one color. Use CMYK (you could imagine a sub-project to design a 8bit color based dot scheme) and compression, and even with ECC losses I can see a few MB of encoded source per page being possible. And writing that decoder would be a great exercise!

[1]: https://www.docucopies.com/image-resolution/

[2]: https://en.m.wikipedia.org/wiki/Machine_Identification_Code

nearbygoogler··on Programming book authors: put all the code in the book
1. Print the source code in a micro-barcode in a physical appendix.

2. Make the first exercise in all books be to code a simple barcode image interpreter. And just include the walkthrough and source as typed text.

You should be able to get a few MB on a page easily. Future proof as long as there are cameras on phones.

nearbygoogler··on Google I/O 2023
I’m with you on the dongle issues, it’s a tremendous pain to find consistently working equipment that allows charging, in-line mic, and durability.

That said, I hate BT more and have been using the same Bose QC20 wired earbuds and Belkin adapters for 4+ years. There are semi-decent options out there.

nearbygoogler··on [dead]
And of course search and remove for any other public dev copies of the site. Good luck!
nearbygoogler··on [dead]
Be sure to request that the old version of your website be removed from Google search. Hint: old.yourdomain still shows the person.