No that's what I mean. Assuming you have Composer installed, and are accustomed to a Composer-centric workflow, running a curl command and then a separate phar

No that's what I mean. Assuming you have Composer installed, and are accustomed to a Composer-centric workflow, running a curl command and then a separate phar file (albeit one containing Composer) is an unusual break from that. I'm guessing the embedded Composer may also ignore any locally-set Composer configuration on the dev's own copy of Composer. One assumes the Sculpin devs do like/appreciate Composer's functionality, since they embed it, but they've opted not to advocate direct use of its interface at all. I don't mean to be overly critical, it just struck me as somewhat bizarre.