This saves hosting costs/overhead and makes it really easy for people to submit pull requests and for contributors to make changes that I don’t always have time for. It makes the project less dependent on me and more a community effort.
To move forward, sometimes you have to cut features. In this case I had to lose our compiler, a webtool that relied on server-side code to generate minified packages from php.js functions.
but some people think php.js should bundle all of it’s functions into one big file:
Not providing an all-in-one, downloadable, minified, ready-to-use .js file is going to kill php.js. You’ve abandoned windows users, and really any non-CLI junkie. While I am capable of compiling this myself, what a headache. You’ve introduced a barrier-to-entry that didn’t exist before, and by not existing, allowed for the following you now have. I highly suggest that you have this available for download, either here or on github, such that you can keep (and maintain) the momentum you worked so hard for.
I’d like to comment on that here. While I appreciate the sentiment, wether the project is being killed by these changes depends on how you look at php.js. To me, php.js is a resource:
- That enables fun experiments
This is what I feel php.js should focus on. Making functions. Making them better.
If - on the other hand - you think of php.js as a
..then yes, these changes are going to kill php.js.
I have limited time to spend on open source, and I want to spend it on things I enjoy and can believe in. Not on working to support use-cases that keep new developers from learning, or make the web slower. I’m sorry if this upsets folks but it really is my free time.
Luckily though for people with different views, I released php.js under MIT so it’s cool for anybody to fork this project and run with it.
If anything, knowing that the php.js repository will focus on the raw
makes this easier.