My attitude to hacking proprietary software/protocols/hardware has always been:
this should be open/documented and it should be easy to produce software/hardware that interacts with it with no problem.
But it's not, so you can't blame me for getting out the crowbar and breaking in.
@foone It always frustrates me that the modern design mantra of modern hardware/software appears to be “we’ll streamline it all and tell you what the experience is that you want” rather than “here are some parts and a good first guess at a good interface, have fun!”
Especially when folks making the locked down/vertically integrated pieces of tech all cut their teeth on open ecosystems that enabled or even encouraged mucking about in internals.
@joepie91 @foone Just ask any random developer spaces (and how many) or tabs, or vim or emacs, and you get a ton of arguing over nonsense.
I think an even bigger problem is devs thinking there’s a right or optimal path (or even that one definition of optimal is better than another) then forcing that decision on users. Of course, then business folks come in afterwards and say “this also makes it easier to monetize!”