Hacker News new | past | comments | ask | show | jobs | submit login

Maybe an entire organization will spring from that to combat proprietary software :)



In case anybody doesn't get the reference, printer driver trouble is what initially motivated Stallman to come up with the idea of free software and ultimately the GPL and the FSF.


I can't believe the entire FOSS ecosystem essentially stemmed from printer issues, and we _still_ don't have a mainstream FOSS printer firmware that removes DRM and tracking dots (and whatever else they do nowadays) akin to OpenWRT, but for printers.

We have fully open source hardware AND software _3D_ printers capable of printing working guns, but we can't improve the process of squirting ink on paper so it's not universally abhorred?


It does always sound really crazy because in our minds 3D is more complex than 2D, but in reality 3D printing is actually really really simple, it's basically just 3 motors, a heat block, and an extruder, that's pretty much it.

Whereas 2D (inkjet) printing has all of the above (minus one motor), and actually comes with a few non-trivial non-printing related expectations as well, like loading and expelling a print surface (often many in one print), optionally flipping said print surface (and this requires that ink has dried as well) and colour processing to map computer colours to real-world colours.


It's actually even more complicated than that. Modern printers include a raster image processor (RIP) [1]. This specialized software converts vector graphics, text, and pixel-based images into a raster dot pattern that controls the print head. The individual dots that get printed can't be varied in size or brightness, so the variations in image tone are controlled by the density of the dots in the raster pattern. This is called halftone [2].

[1] https://en.wikipedia.org/wiki/Raster_image_processor

[2] https://en.wikipedia.org/wiki/Halftone


Yeah but those problems were all solved decades ago.


Maybe it's time for Framework to start doing printers too.


Firmware is the thing that Framework has failed the most at from day one to today. It's every bit as locked down as everyone else's only without the big guys quality control and updates so you get to live with bugs for the entire life of the hardware.

Their firmware updates are complete clown car. When they actually do one, the update process itself is just stupid fragile. Cross your fingers and clear your schedule for the next day in case you aren't lucky. You have a 10% chance of being left with a machine that probably still runs but works worse than before, and no ability to roll back.

I have a 11th gen intel board that is completely unusable after an update, but might possibly still be recoverable if I reinstall it into the laptop so it can use the laptop display instead of displayport. But I'd have to take my current 12th gen board out and then put it all back again after.

A Framework printer, if it matched a Framework laptop, would still have shit firmware, probably licensed from one of the majors, with all the same bad behavior, except with more bugs.


agreed their firmware is their biggest flaw

disagree it's all their fault, I've had 0 problems with my amd board on linux, and anecdotally that appears to be common on the forums, where intel is more painful.

That's one of the reasons I refused to invest prior to their amd board. I can't trust intel not to be toxic.

I'd still take a broken crappy printer from framework (assuming it's hackable, and not doom and gloom like you predict) over the status quo. I mean, I mainline linux because software being non-toxic is more important than polish will ever be to me.




Consider applying for YC's Summer 2025 batch! Applications are open till May 13

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: