Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Framework agnostic packages for the win (ForumPHP 2015)
Search
Jonathan Reinink
November 24, 2015
Technology
8
940
Framework agnostic packages for the win (ForumPHP 2015)
Jonathan Reinink
November 24, 2015
Tweet
Share
More Decks by Jonathan Reinink
See All by Jonathan Reinink
The formula to awesome docs (phpDay 2017)
reinink
0
120
How to open source a PHP package (phpDay 2017)
reinink
1
100
The formula to awesome docs (Lone Star PHP 2016)
reinink
0
830
The PHP Package Checklist (Lone Star PHP 2016)
reinink
0
250
Framework agnostic packages for the win (SkiPHP 2016)
reinink
1
220
Rethink image manipulations with Glide (ForumPHP 2015)
reinink
0
520
Rethink image manipulations with Glide
reinink
3
420
Enough about Classes, Let's Talk Templates
reinink
8
3.6k
Practical deployments for average projects
reinink
4
390
Other Decks in Technology
See All in Technology
On Your Data を超えていく!
hirotomotaguchi
2
660
Delivering Millions of Messages within seconds @ Duolingo
pelelgrino
0
350
VS CodeでAWSを操作しよう
smt7174
7
1.6k
Meta Quest 3 で動く桜マシマシ WebXR アプリを IBM Cloud Code Engine と Babylon.js で作った話
1ftseabass
PRO
0
120
DevOpsDays History and my DevOps story
kawaguti
PRO
9
2.5k
開発生産性大幅アップ!Postman VS Code拡張機能
nagix
2
370
非同期推論システムによるコスト削減と信頼性向上
koki_nishihara
0
210
開発生産性向上サービスを作るFindyが自分たちで開発生産性を爆上げした組織づくりの歩み / Findy's path to boosting its own development productivity 2024-04-17
ma3tk
3
630
TechFeed Experts Night#27 〜 フロントエンドフレームワーク最前線 (Svelte)
baseballyama
1
380
アクセシビリティを考慮したUI/CSSフレームワーク・ライブラリ選定
yajihum
2
1k
私が trocco を推す理由
__allllllllez__
1
210
ここが嬉しいABAC ここが辛いよABAC #再解説+補足編
masahirokawahara
1
270
Featured
See All Featured
From Idea to $5000 a Month in 5 Months
shpigford
377
45k
Stop Working from a Prison Cell
hatefulcrawdad
266
19k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
322
20k
Rails Girls Zürich Keynote
gr2m
91
13k
Mobile First: as difficult as doing things right
swwweet
216
8.6k
Git: the NoSQL Database
bkeepers
PRO
422
63k
Principles of Awesome APIs and How to Build Them.
keavy
121
16k
How to name files
jennybc
65
93k
Building Effective Engineering Teams - LeadDev
addyosmani
28
1.8k
How to Ace a Technical Interview
jacobian
272
22k
ParisWeb 2013: Learning to Love: Crash Course in Emotional UX Design
dotmariusz
104
6.6k
Into the Great Unknown - MozCon
thekraken
10
990
Transcript
None
Jonathan Reinink Software developer from Canada. Been writing PHP for
over 15 years. Marketing agency for over a decade. Started contract development this year. I <3 open source.
None
What exactly does framework agnostic mean?
Code that works independent of frameworks.
Framework agnostic does not mean framework intolerant.
Why framework agnostic?
Framework agnostic code is more reusable than framework specific code.
Reusable code is code we don't have to write.
I believe creating reusable code is key to the continued
success of PHP.
As software become increasingly more complex, our reliance on existing,
quality code increases.
I see a future where the various PHP communities more
actively share code with one another.
So, why then are we using framework specific code?
Because we sort of had to.
1994 - 2004: 2005 - 2012: 2013 - Future: Vanilla
PHP Frameworks Packages
1994 - 2004: The age of vanilla PHP
Rasmus started working on PHP sometime in 1994.
PHP was this new amazing tool that let us build
dynamic websites easily.
PHP became a career for many of us.
We started finding ways to write code better and faster.
PHP had a decent standard library, but pieces were missing.
Routing Templating Database Abstraction Validation Session Handling Error Management Authentication
Caching Request Processing Responses Sending
Developers starting writing new, focused PHP libraries.
But…we had no easy way to share them.
So we manually downloaded zip files.
Introducing PEAR: PHP first attempt at a package manager.
1. To provide a consistent means for library code authors
to share their code with other devs. 2. To give the PHP community an infrastructure for sharing code. 3. To define standards that help developers write portable and reusable code. 4. To provide tools for code maintenance and distribution.
PEAR had some issues...
The community gave up on PEAR. :(
2005 - 2012: The age of frameworks
Reusable code was packaged up into libraries called frameworks.
Frameworks were easy to download, and they just worked.
Frameworks came with almost everything needed for the average project.
Frameworks allowed us to get work done quickly.
2015 became the year of PHP frameworks. Symfony, CakePHP, Solar,
Agavi, ezComponents
But, what if the framework didn't have some other functionality
you needed?
Frameworks grew to accommodate a wide range of use cases.
We continued to download zip files. :(
Then everything changed.
2013 - Future: The age of packages
1994 - 2004: 2005 - 2012: 2009: 2012: 2013 -
Future: Vanilla PHP Frameworks PHP-FIG Formed Composer Launched Packages
None
“We're a group of established PHP projects whose goal is
to talk about commonalities between our projects and find ways we can work better together.” (PHP-FIG goal)
“To define standards that help developers write portable and reusable
code.” (PEARs goal)
Their very first recommendation was an autoloading standard called PSR-0.
The PHP-FIG continues to develop standards that make sharing reusable
code easier.
www.php-fig.org
None
Unlike PEAR, Composer got a LOT of things right.
Downloaded packages. Resolved their dependencies. Autoloaded classes.
Composer was exactly what PHP needed to solve it's code
sharing problem.
Composer was an overnight success, and became mainstream in 2013.
Packages starting popping up everywhere. It was amazing!
So, why are we still using frameworks?
In the age of packages, the purpose of frameworks is
changing.
Frameworks no longer have to be everything to everyone.
Frameworks are now the glue between reusable framework agnostic packages.
Need something your framework doesn’t offer? No worries, just: >
composer require the/package
Even frameworks are now being built using framework agnostic code.
Framework agnostic code also pulls communities together.
Framework agnostic code is good for package maintainers.
If you’re a maintainer of a framework specific package, please
consider making it framework agnostic.
This will require a change in thinking. We’ve been in
the age of frameworks a long time.
Offer framework specific support for your package using service providers.
None
phppackagechecklist.com
None
So, why framework agnostic?
BECAUSE IT CAN BE!!!
Thanks! Follow me on Twitter at @reinink. Rate this talk
https://joind.in/15278.