Explore >> Select a destination
|
You are here 
|
www.newosxbook.com | ||
| | | | |
newosxbook.com
|
|
| | | | | ||
| | | | |
worthdoingbadly.com
|
|
| | | | | I ran command line macOS tools, such as Bash and Geekbench, on a jailbroken iPhone by replacing iOS's dyld shared cache (all of iOS's code) with macOS's. However, graphical apps will never work: macOS's WindowServer won't start, since iOS's drivers are too different. | |
| | | | |
theevilbit.github.io
|
|
| | | | | After my recent blog post, my old mate @_Dark_Knight_ reached out to me and he asked me a question: "Do you typically callout user apps that allow dyld_insert_libraries?" And a few similar ones, and I will be honest, I had no idea what is he talking about, if only I understood the question :D Despite the fact that my recent blog posts and talks are about macOS, I deal much more with Windows on a daily basis, probably like 95%, and macOS is still a whole new territory for me. So I decided to dig into the question and learn a bit more about this. | |
| | | | |
dusty.phillips.codes
|
|
| | | I really appreciate Python's pathlib module for managing filesystem stuff. While I don't love the argparse module for command line parsing, I don't think it's worse than other available options. I usually choose it for my CLI scripts, since nothing else is good enough to overcome the inertia of using a third party library. Not many people seem to be aware that the two can very easily be combined such that argparse will return Path objects instead of strings that need to be adapted after you query them: | ||
