It also requires a root launcher that runs code from the user ~/.hp1008 dir, so security is weakened.
It also requires a root launcher that runs code from the user ~/.hp1008 dir, so security is weakened.
https://github.com/Kuberwastaken/hp-laser-1008a-macos
Previous context I shared on X:
"Also some clarification on the "he's just using the linux driver in the VM" - not quite
This is one of the weirdest batch of printers HP made because it's a rebranded Samsung - it "comes" under HP's unified drivers system but specifically has Samsung's printer language so compatibility is extremely messy.
What this version does is take the Linux Unified Driver and extract just the relevant component, rastertospl, basically the codec that turns CUPS raster data into the Samsung SPL format the printer understands. That codec is then wired into macOS’s native CUPS stack, so printing happens through the system like a normal driver. There’s no Linux VM handling the actual print workflow and the entire process basically acting as a driver normally at system level.
In theory, yeah - rastertospl could be reimplemented from scratch. But that would be way more unreliable while turning this from a ~4-hour project into a ~4-day reverse-engineering project, when starting this, I really just wanted a working home printer and running a tiny compatibility applet in Docker just for that codec feels like a pretty reasonable compromise AND I get to not see my mac kernel crash if it messes up.
I didn't expect this to blow up this much lol, so I'll be experimenting with this further and am already in talks with the splix team to sort this specific version out"
Problem solved. New problem created.
New problem?
Justifying the use of AI to do something these people act like would magically get done if you were just slightly more patient. Or, if you put in 60+ hrs of time.
By contrast, the README is still lying about this being a printer driver.
You need a lot of clarifications, since the presentation is chaotic, the repo is chaotic and this is a marketing stunt with exaggerated language and promises.
for instance the 'windows' part is also entirely nonsensical as the printer works on a default mint installation w/o any issues. The "obscure" part is weird as you can just buy the printer online as well.
- https://en.wikipedia.org/wiki/Device_driver
Is using a VM running another operating system as part of a driver weird, yes. Is it still a driver? Also yes.
OP should probably add this to his list of accomplishments on LinkedIn...
I bought some cheap host-managed SATA drives the other day that the BIOS can't see and Windows won't recognize. I asked Claude to write a Windows app so I can use them, and it resisted at first, but then gave up and wrote it and they now work great.
It had to implement the entire stack of bare-metal drive functions over SATA and a whole new filesystem to go with it.
The "only built for Windows" is also a little dubious. Technically I suppose HP could have just intended it as a Windows printer, but the driver clearly already exists in CUPS, which Apple also uses, so porting the driver isn't an unreasonable thought.
I am sooo tired of this AI generated slop.
Though I'm not convinced it actually is. OP said the same the first time around, and I don't think actually understands what they (or rather Claude) is doing. The HN comment here claiming they updated it, clearly written by Claude, doesn't inspire much confidence.