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 (ForumP...
Search
Jonathan Reinink
November 24, 2015
Technology
8
1k
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
140
How to open source a PHP package (phpDay 2017)
reinink
1
110
The formula to awesome docs (Lone Star PHP 2016)
reinink
0
920
The PHP Package Checklist (Lone Star PHP 2016)
reinink
0
270
Framework agnostic packages for the win (SkiPHP 2016)
reinink
1
260
Rethink image manipulations with Glide (ForumPHP 2015)
reinink
0
590
Rethink image manipulations with Glide
reinink
3
480
Enough about Classes, Let's Talk Templates
reinink
8
3.7k
Practical deployments for average projects
reinink
4
390
Other Decks in Technology
See All in Technology
VPC間の接続方法を整理してみた #自治体クラウド勉強会
non97
1
840
いまさらのStorybook
ikumatadokoro
0
110
AWS re:Inventを徹底的に楽しむためのTips / Tips for thoroughly enjoying AWS re:Invent
yuj1osm
1
570
Fargateを使った研修の話
takesection
0
120
Vueで Webコンポーネントを作って Reactで使う / 20241030-cloudsign-vuefes_after_night
bengo4com
4
2.5k
初心者に Vue.js を 教えるには
tsukuha
5
390
omakaseしないための.rubocop.yml のつくりかた / How to Build Your .rubocop.yml to Avoid Omakase #kaigionrails
linkers_tech
3
740
AWS CodePipelineでコンテナアプリをデプロイした際に、古いイメージを自動で削除する
smt7174
1
100
分布で見る効果検証入門 / ai-distributional-effect
cyberagentdevelopers
PRO
4
700
「最高のチューニング」をしないために / hack@delta 24.10
fujiwara3
21
3.4k
プロダクトエンジニアが活躍する環境を作りたくて 事業責任者になった話 ~プロダクトエンジニアの行き着く先~
gimupop
1
480
LeSSに潜む「隠れWF病」とその処方箋
lycorptech_jp
PRO
2
120
Featured
See All Featured
Testing 201, or: Great Expectations
jmmastey
38
7k
A designer walks into a library…
pauljervisheath
202
24k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
280
13k
StorybookのUI Testing Handbookを読んだ
zakiyama
26
5.2k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
37
1.8k
Gamification - CAS2011
davidbonilla
80
5k
Speed Design
sergeychernyshev
24
570
Fontdeck: Realign not Redesign
paulrobertlloyd
81
5.2k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
42
9.2k
Making the Leap to Tech Lead
cromwellryan
132
8.9k
Java REST API Framework Comparison - PWX 2021
mraible
PRO
28
7.9k
Thoughts on Productivity
jonyablonski
67
4.3k
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.