Skip to content

The Single-Page Application Dilemma

Avatar of William Pinaud William Pinaud

πŸ›° In the light of a beam of new concepts, paradigms, technological changes, user behaviour changes and social metamorphoses, the way we build lightweight applications like web applications changed.

Going through a standardized program like a browser and using standards like the W3C, IEEE, ISO or MIT provide. Under the shadows of "Big Tech" IT giants like Alphabet, Alibaba, Meta, Netflix, Twitter, LinkedIn, etc.

User habits have changed, lots of things are different now. Brave new world.
As I always say: now your mum is on her smartphone, checking bank accounts at 2 A.M. while your dad is binge-shopping on Wish. Your kids? They're now sending over tenths of thousands of HTTP requests per day.

πŸš€ The web is now made of over 100 million servers, connecting over 21 billion IoT/mobile devices. Networks still can't possibly be trusted, though 6G is being assembled, people expect things to work in planes at Mach 0.8, we started offering quantum computing as a service, and many places and people in the world have better access to smartphones than they have to food and water.

At the crossroads of a tenth of factors, some trends appeared. JavaScript everywhere, frontend frameworks, new web architectures, concepts, ideas, constraints, offline mode, etc. Among all those, single-page applications began to rise since they were first patented in 2003 and became very very popular... So do we think.

What are they? Why do we sell those? Are they really needed? What's behind all that hysterization? Who's in charge? Will you be able to maintain them? At what cost?

🌌 Well. You might be quite surprised about the answers. From transversal design to server-side rendering, from web components to Hotwire, from AJAX to service workers, from business biases to CV-driven development, from Stimulus and Turbo to Symfony UX, from jQuery to SvelteKit, we're going in for a little trip, so that we finally sit down altogether and take some time to talk about that elephant in the room (which, for once, is *NOT* PHP's).

β˜•οΈ In this talk we will:
β€’ Understand the paradigm shifts we faced over the last two decades
β€’ Decipher the Big Tech roadmaps and strategies and how they affect our choices and egos
β€’ See a little history of the web and its main evolutions
β€’ Unmask the real business reasons why SPA's are a thing
β€’ See how they're actually still useful in some cases
β€’ Review the tools we have at disposal to avoid using them
β€’ And finally, open our minds to new trends that need some debunking like this one

πŸ™Œ PS: if you're a frontend developer yourself, I do recommend you take some painkillers before attending the talk. That's a whole rollercoaster ahead of you. For the best. 😏

Delivered in English
Room:
Track Platform.sh

Friday, June 17, 2022 at 10:50 AM – 11:25 AM

Intermediate talk, some familiarity with the topic required.