So great! We use Composer extensively and have dozens of tiny open-source packages we use for our many small Laravel apps. There were at least three points that will help us out significantly.
The information on composer was quite good and I did learn a few things. I'd argue that this level of talk would be better aimed at absolute composer newcomers, since there wasn't a lot of new information for more advanced or mid-level usage.
I'd also LOVE to have a slide with a table comparison of the different version constraint characters so you could see a side by side look at them, it was hard to grasp everything without that overall view.
I would second the other comment that if this is meant for a more advanced talk - some more information for application and package authors would be really useful.
In reviewing my session notes, and re-reading the abstract for the talk, Jordi did deliver in presenting exactly what he said he would present - version constraints, stability, and semantic versioning, plus a few additional tips when using Composer. I enjoyed the talk, but somehow, I came away feeling like I wanted more, even if I can't quite put my finger on what "more" means, in this case. Perhaps a clearer outline of where the talk is going before it gets there might help?
Topics in this talk I particularly appreciated: Jordi's clarification that the composer.lock file should be tracked in version control (and that it shouldn't be deployed!), reinforcement on how versions should be numbered, what a README file should include, and how to constrain package versions in your composer.json file. Some of the talk around tags, branches, and stability resolution were lost on me, but I'm not sure whether that is a reflection on the speaker, my own knowledge level, or both.
Lastly, I appreciated the list of resources I can look up in my own time for additional information.
Overall, a solid presentation. There's no better source than the creator of a utility!
Comments
Comments are closed.
Awesome talk that focuses on the important and often missed features!
Would have liked to see more content for package authors.
So great! We use Composer extensively and have dozens of tiny open-source packages we use for our many small Laravel apps. There were at least three points that will help us out significantly.
The information on composer was quite good and I did learn a few things. I'd argue that this level of talk would be better aimed at absolute composer newcomers, since there wasn't a lot of new information for more advanced or mid-level usage.
I'd also LOVE to have a slide with a table comparison of the different version constraint characters so you could see a side by side look at them, it was hard to grasp everything without that overall view.
I would second the other comment that if this is meant for a more advanced talk - some more information for application and package authors would be really useful.
cool talk
now i want to learn what composer is. i need to get out of my cave. maybe tomorrow.
In reviewing my session notes, and re-reading the abstract for the talk, Jordi did deliver in presenting exactly what he said he would present - version constraints, stability, and semantic versioning, plus a few additional tips when using Composer. I enjoyed the talk, but somehow, I came away feeling like I wanted more, even if I can't quite put my finger on what "more" means, in this case. Perhaps a clearer outline of where the talk is going before it gets there might help?
Topics in this talk I particularly appreciated: Jordi's clarification that the composer.lock file should be tracked in version control (and that it shouldn't be deployed!), reinforcement on how versions should be numbered, what a README file should include, and how to constrain package versions in your composer.json file. Some of the talk around tags, branches, and stability resolution were lost on me, but I'm not sure whether that is a reflection on the speaker, my own knowledge level, or both.
Lastly, I appreciated the list of resources I can look up in my own time for additional information.
Overall, a solid presentation. There's no better source than the creator of a utility!