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
Fluent Conf 2013 Summary
Search
Sponsored
·
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
Guille Paz
July 27, 2013
Technology
0
120
Fluent Conf 2013 Summary
Progressive Enhancement and History API on Twitter.
Guille Paz
July 27, 2013
Tweet
Share
More Decks by Guille Paz
See All by Guille Paz
The Road to Node
pazguille
0
260
No me robes el Scroll!
pazguille
0
270
User First
pazguille
1
210
#OfflineFirst
pazguille
3
6k
ES6 in Production
pazguille
10
3.2k
No me hagas esperar!
pazguille
1
200
CSS Sprites vs. Data URIs
pazguille
0
450
Hello, Style Guides!
pazguille
0
280
Decoupling your JavaScript
pazguille
0
190
Other Decks in Technology
See All in Technology
AI実装による「レビューボトルネック」を解消する仕様駆動開発(SDD)/ ai-sdd-review-bottleneck
rakus_dev
0
160
Everything Claude Code を眺める
oikon48
12
7.5k
社内レビューは機能しているのか
matsuba
0
150
OSC仙台プレ勉強会 AlmaLinuxとは
koedoyoshida
0
190
品質を経営にどう語るか #jassttokyo / Communicating the Strategic Value of Quality to Executive Leadership
kyonmm
PRO
2
540
AI駆動AI普及活動 ~ 社内AI活用の「何から始めれば?」をAIで突破する
oracle4engineer
PRO
1
110
CyberAgentの生成AI戦略 〜変わるものと変わらないもの〜
katayan
0
270
20260311 ビジネスSWG活動報告(デジタルアイデンティティ人材育成推進WG Ph2 活動報告会)
oidfj
0
350
Google系サービスで文字起こしから勝手にカレンダーを埋めるエージェントを作った話
risatube
0
190
ReactのdangerouslySetInnerHTMLは“dangerously”だから危険 / Security.any #09 卒業したいセキュリティLT
flatt_security
0
320
モジュラモノリス導入から4年間の総括:アーキテクチャと組織の相互作用について / Architecture and Organizational Interaction
nazonohito51
1
300
生成AIで速度と品質を両立する、QAエンジニア・開発者連携のAI協調型テストプロセス
shota_kusaba
0
190
Featured
See All Featured
Why You Should Never Use an ORM
jnunemaker
PRO
61
9.8k
AI Search: Implications for SEO and How to Move Forward - #ShenzhenSEOConference
aleyda
1
1.2k
Designing Powerful Visuals for Engaging Learning
tmiket
0
290
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
52
5.9k
A brief & incomplete history of UX Design for the World Wide Web: 1989–2019
jct
1
320
Making Projects Easy
brettharned
120
6.6k
Noah Learner - AI + Me: how we built a GSC Bulk Export data pipeline
techseoconnect
PRO
0
140
4 Signs Your Business is Dying
shpigford
187
22k
Why Our Code Smells
bkeepers
PRO
340
58k
SERP Conf. Vienna - Web Accessibility: Optimizing for Inclusivity and SEO
sarafernandez
1
1.3k
How STYLIGHT went responsive
nonsquared
100
6k
Building Adaptive Systems
keathley
44
3k
Transcript
Summary
None
None
None
Thanks!
Experiences along the time
What happened in 2010?
None
None
CORE functionality
User should be able to navigate between section of the
site
Navigation between sections should be fast
URLs should be accessible regardless of the client’s abilities
Make page navigation easier and faster
Render runs on Server and Client
Routing model on the Client (mustache)
Strong relationship between a URL and its content
#Hash Navigation (hashbang)
None
JavaScript is the core technology
2011
Optimizations available only on the Server
Multiples URLs
None
Multiples Requests
Bad page-load performance
2012
Moving the rendering to the Server
No more #!
Just one URL
Load only what we need
2013
Speed up navigation between pages
One view, two types of requests
Server
None
Client
History API
None
None
None
None
Hijax
Be like water
The End
Questions