JSFoo is in its ninth edition this year. Talks at JSFoo 2019 will cover the following topics:
- Component architecture -- how different web components have been stitched together to build apps; outcomes on UI and performance as a result of architecture choices
- Deployment practices for front-end and how Kubernetes and CI/CD fall into this picture
- Developer experience (DX)
- Functional programming paradigms: ReasonML and ClojureScript
- Privacy and Content Security Policy (CSP)
- New developments such as SvelteJS
Speakers from Razorpay, CloudCherry, Myntra, Innovaccer, GitLab, Microsoft, Atlassian and Gramener will share their work and learnings on these topics.
JSFoo is a conference for practitioners, by practitioners. JSFoo 2019 is a conference for:
- Front-end engineers
- Senior software developers
- Team leaders and engineering managers
- Fullstack developers
- InfoSec professionals
##JSFoo 2019 details:
Dates: 27 and 28 September
Venue: NIMHANS Convention Centre, Bangalore
The following workshops have been curated for before and after the conference:
For inquiries about conference tickets, workshop tickets and any other details, call JSFoo on 7676332020 or email email@example.com
For tickets and sponsorships, contact firstname.lastname@example.org or call +91-7676332020. For queries about proposing talks, write to email@example.com
To SPA or not to SPA
SPA or Single Page Applications have become a huge trend in modern day web applications. Almost all the web applications written today use some kind of SPA framework whether it be Angular or React or Vue or something else. So the question then is do we really need a single page application for all use cases? Does single page application always help improve performance? Can we do without a single page application?
- What is SPA or Single Page Application?
- Drawbacks of a SPA
- Complex set of interactive components
- Tooling (babel, webpack, etc.) for browser to be able to handle it
- SEO unfriendly
- Extra effort to make it stateful
- High memory consumption
- Loading CSS and JS for large applications
- Breaks browser features
- Nothing works if JS is not allowed in browser
- When to use a SPA?
- Set of interactive components, constantly being updated separately
- Is your site more graphics-intensive?
- Real-time experience without page refresh
- Lots of state shared between screens
- How it fits for Facebook, trello, etc.
- Multi-page Applications
- It lets browser do the browsing
- Free SEO
- Better shareable links many times
- Hybrid Applications
- Combine best of both worlds
- Don’t SPA the entire web app
- How Github does it
- Conclusion: Love SPA, but understand when you need it
An open mind to hear some unfavorite things