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
490
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
AGIについてChatGPTに聞いてみた
blueb
0
130
リンクアンドモチベーション ソフトウェアエンジニア向け紹介資料 / Introduction to Link and Motivation for Software Engineers
lmi
4
300k
【令和最新版】AWS Direct Connectと愉快なGWたちのおさらい
minorun365
PRO
5
760
『Firebase Dynamic Links終了に備える』 FlutterアプリでのAdjust導入とDeeplink最適化
techiro
0
140
Terraform Stacks入門 #HashiTalks
msato
0
360
Making your applications cross-environment - OSCG 2024 NA
salaboy
0
200
マルチプロダクトな開発組織で 「開発生産性」に向き合うために試みたこと / Improving Multi-Product Dev Productivity
sugamasao
1
310
BLADE: An Attempt to Automate Penetration Testing Using Autonomous AI Agents
bbrbbq
0
320
SSMRunbook作成の勘所_20241120
koichiotomo
3
160
100 名超が参加した日経グループ横断の競技型 AWS 学習イベント「Nikkei Group AWS GameDay」の紹介/mediajaws202411
nikkei_engineer_recruiting
1
170
AWS Lambda のトラブルシュートをしていて思うこと
kazzpapa3
2
180
AIチャットボット開発への生成AI活用
ryomrt
0
170
Featured
See All Featured
A Tale of Four Properties
chriscoyier
156
23k
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
47
2.1k
The Language of Interfaces
destraynor
154
24k
4 Signs Your Business is Dying
shpigford
180
21k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
26
1.4k
VelocityConf: Rendering Performance Case Studies
addyosmani
325
24k
What's new in Ruby 2.0
geeforr
343
31k
Side Projects
sachag
452
42k
Intergalactic Javascript Robots from Outer Space
tanoku
269
27k
Keith and Marios Guide to Fast Websites
keithpitt
409
22k
The Illustrated Children's Guide to Kubernetes
chrisshort
48
48k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
126
18k
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.