Using a framework or not

Peter Fisher (11.Apr.2018 at 19:50, 10 min)
Talk at PHPSW: Lightning Talks, April 2018 (English - UK)

Rating: 5 of 5

For both the frontend and backend there are many frameworks that allow for the rapid and solid build of web applications. Many projects require the knowledge of a framework. In some cases this leads a developer to be more understanding of a framework instead of the language that the framework is written in.
Should every application be built using a framework and if not, when is it OK not to use a framework?

Who are you?

Claim talk

Talk claims have been moved to the new site.

Please login to the new site to claim your talk

Comments closed.


Rating: 5 of 5

11.Apr.2018 at 19:59 by Mr Andrius Bartulis (9 comments) via Web2 LIVE

Interesting talk. Lots of good points about both building your own framework and using an existing one.

Rating: 4 of 5

11.Apr.2018 at 19:59 by Lucia Velasco (34 comments) via Web2 LIVE

I love that you outlined a perspective that few people can or even try to coin (why a student would choose to learn a language in a framework).
Some of the points were excellent but they were not delivered succinctly. I liked the summary!

Rating: 4 of 5

11.Apr.2018 at 19:59 by Ian (7 comments) via Web2 LIVE

Good questions at the end and statements at the end.

Rating: 4 of 5

11.Apr.2018 at 20:00 by Rob Wilson (31 comments) via Web2 LIVE

Great talk by Peter. Pros/Cons of a framework has been a challenge with work and I'll be using his slides to help with the challenges I have with PMs. Some real world examples would have been good to show the audience, but as mentioned, the project should determine the framework ;)

Rating: 4 of 5

11.Apr.2018 at 20:01 by MattRink (9 comments) via Web2 LIVE

You successfully managed to explain the separation of developer ego and the needs of the project. Very insightful.

Rating: 5 of 5

11.Apr.2018 at 20:03 by Matt Adshead (7 comments) via Web2 LIVE

Yep yep yep yep.

Rating: 4 of 5

11.Apr.2018 at 20:04 by Paul alden (8 comments) via Web2 LIVE

Well informed and experienced talk about commonly encountered issues for new developers, kept short simple. Good work.

Rating: 5 of 5

11.Apr.2018 at 20:12 by Nicola Richardson (4 comments) via Web2 LIVE

Really clear, nice overview. Good slides too - supported the content well. Maybe stand a little closer to the screen next time, it was a bit distracting having so much distance. Thanks for the talk!

Rating: 5 of 5

11.Apr.2018 at 20:15 by Drew McLellan (15 comments) via Web2 LIVE

Well presented, and I really liked the pros and cons approach. About the right amount of content for the time -great job.

Rating: 5 of 5

11.Apr.2018 at 20:19 by Michael Bush (30 comments) via Web2 LIVE

Very good talk with lots of good points, maybe improve it by providing personal experiences

Rating: 4 of 5

11.Apr.2018 at 20:19 by David Lumm (7 comments) via Web2 LIVE

Balanced look at the pros and cons. Very timely, the tide is turning on chasing the new shiny, people are looking for stability and longevity.

Rating: 5 of 5

11.Apr.2018 at 20:22 by Mike Oram (28 comments) via Web2 LIVE

Fantastic talk, well reasoned, well paced, lots of information and opinions with good reasoning and balanced arguments. A pleasure to listen to.

Rating: 5 of 5

12.Apr.2018 at 08:34 by Kieran Potts (8 comments) via Web2 LIVE

A very big debate, well summarised. I'd add the point that you might consider an application framework as being an application's eventual destination, rather than its starting point. To put it another way, a framework comes about by the gradual imposition of constraints on an application's design. But that's a whole other talk, probably...

Rating: 4 of 5

12.Apr.2018 at 11:11 by Dave Liddament (69 comments) via Web2 LIVE

Good slides. Good delivery. Good content.

A few minor points for improvement:

A massive con for writing your own framework was missing: security. The major frameworks will have been reviewed for security problems and vulnerabilities by many people. Rolling your own it's just you. (Admittedly mistakes still happen e.g. recent Drupal bug).

Also for non trivial projects the business logic should be decoupled from the framework. Once you've decoupled code from framework the choice of framework (or not) becomes less of an issue. I feel this is not emphasised enough in the industry generally. Talks about frameworks should, IMHO, at least mention this in passing.

© 2019