181–190 of 241 posts
Unfortunately this is a very misleading article and headline. I don't doubt the end result - it's useful that it works, but it's not "natively" and, unlike what some people assume, Claude didn't write a driver. It basically used HP's existing proprietary driver in a Linux VM on macOS, and just bridged that to macOS. It also requires a root launcher that runs code from the user ~/.hp1008 dir, so security is weakened.
Unfortunately this is a very misleading article and headline. I don't doubt the end result - it's useful that it works, but it's not "natively" and, unlike what some people assume, Claude didn't write a driver. It basically used HP's existing proprietary driver in a Linux VM on macOS, and just bridged that to macOS. It also requires a root launcher that runs code from the user ~/.hp1008 dir, so security is weakened.
This comment should be pinned, and the fact that a misleading post continues to be on the first page blows my mind.
Unfortunately this is a very misleading article and headline. I don't doubt the end result - it's useful that it works, but it's not "natively" and, unlike what some people assume, Claude didn't write a driver. It basically used HP's existing proprietary driver in a Linux VM on macOS, and just bridged that to macOS. It also requires a root launcher that runs code from the user ~/.hp1008 dir, so security is weakened.
He could have done this with 10-15 minutes of googling instead of spending 4 hours prompting a LLM.
Unfortunately this is a very misleading article and headline. I don't doubt the end result - it's useful that it works, but it's not "natively" and, unlike what some people assume, Claude didn't write a driver. It basically used HP's existing proprietary driver in a Linux VM on macOS, and just bridged that to macOS. It also requires a root launcher that runs code from the user ~/.hp1008 dir, so security is weakened.
UPDATE: Noted, shifted to a 100% native MacOS version now :D 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…
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.
Earlier quoted context omitted.
Redditors actually believe this
Also, they seem to care about wasting electricity but doesn’t bat an eye of discarding a perfectly fine printer.
Unfortunately this is a very misleading article and headline. I don't doubt the end result - it's useful that it works, but it's not "natively" and, unlike what some people assume, Claude didn't write a driver. It basically used HP's existing proprietary driver in a Linux VM on macOS, and just bridged that to macOS. It also requires a root launcher that runs code from the user ~/.hp1008 dir, so security is weakened.
I do not want to call anyone names but the level of pedantry and gatekeeping in this comment and the replies is outstanding. I can hear Chuck McGill screaming "You're not a real driver!".
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.
Is this
Product market fit?
Earlier quoted context omitted.
Had a similar thought today - maybe we could finally get Linux drivers for more HW...
Well good news... er... the opposite actually.... >Additional Old Linux Drivers Face Removal Due To Noise From AI/LLM Coding Agents https://www.phoronix.com/news/Linux-Retiring-Moxa-Driver
I was able to (through heavy Claude use) successfully reverse engineer a golf cart motor controller that is programmable over USB, but only was supported by a Windows application. Claude walked me through using ILSpy on the .NET assembly, using Wireshark to capture the protocol over USB, and to completely map out all of the functionality in the Windows application. The output was a portable C library and CLI program…
Had a similar thought today - maybe we could finally get Linux drivers for more HW...