I 90% agree. The origin story for this project is my collaborator exclusively uses an iPad and wanted to program with LÖVE. He tried a bunch of tools for this,

I 90% agree. The origin story for this project is my collaborator exclusively uses an iPad and wanted to program with LÖVE. He tried a bunch of tools for this, and found various sharp edges in integrating a workflow out of multiple apps while dealing with iOS limitations. The 10% I disagree on is a use case that all modern environments ignore that I think is very important: helping outsiders make changes to the programs they use. Open source projects have a way of gradually diverging the development experience from the user experience. The best way I've found to avoid this slippery slope is a very hard line: developing at least small changes should require exactly the software needed to run the app, and nothing else. In this case, that's LÖVE. The design constraint I bring to this project is: it's built in LÖVE and so I know LÖVE is installed on the system. How can I make changes to this project using just LÖVE and nothing else? My current best answer is https://git.sr.ht/~akkartik/driver.love https://git.sr.ht/~akkartik/driver.love which lets you make changes to this app and other apps I've built as they're running. (Unfortunately my design constraint is currently only satisfied on desktop devices. iOS considers LÖVE to be the first-class app and won't let two copies of a first-class app run simultaneously. So you're stuck making changes to your app on a computer and then transferring it to your mobile device somehow.)