Reply to post: Re: I understand where the dev is coming from but ....

FUSE for macOS: Why a popular open source library became closed source and commercially licensed

bombastic bob Silver badge
Mushroom

Re: I understand where the dev is coming from but ....

Just like Micro-shaft, looks like Apple wants to "lock down" the kernel using *cough* certificates THAT YOU HAVE TO PAY FOR.

Nevermind the effect it has on OPEN SOURCE and FREEDOM TO USE YOUR OWN COMPUTER HOW YOU SEE FIT...

Also: besides being IRRITATING, it's a FALSE sense of security. Widespread cracking of _THAT_ is just a matter of time... and I doubt they're making any developer friends in the process.

[you could make the case of having a strong lock on a door; however, it's my opinion that putting a TOLLBOOTH ON THE PROCESS is _NOT_ the way to do it! That assumes that Apple _CHARGES MONEY_ to sign the drivers, just the way that Micro-shaft does]

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

SUBSCRIBE TO OUR WEEKLY TECH NEWSLETTER

Biting the hand that feeds IT © 1998–2020