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
Back to the future of JS
Search
Sponsored
·
SiteGround - Reliable hosting with speed, security, and support you can count on.
→
Willian Martins
July 03, 2018
Technology
92
1
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Back to the future of JS
This is an extended version of my talk I gave @ NodeJs Meetup in Berlin in July 2018
Willian Martins
July 03, 2018
More Decks by Willian Martins
See All by Willian Martins
Empirical Observations on the The Future of Scalable UI Architecture
wmsbill
0
160
Além do else! Categorizando Pokemóns com Pattern Matching no JavaScript
wmsbill
0
880
De volta ao Futuro do JS: As próximas features e propostas incríveis
wmsbill
0
110
Back to the future of JS II: Beyond what we can foresee
wmsbill
0
140
A, B, C. 1, 2, 3. Iterables you and me.
wmsbill
0
120
Back to the future of JS II: Beyond what we can foresee
wmsbill
0
140
Back to the future of JS.
wmsbill
0
11
Node conf ar 2018.
wmsbill
0
660
Back to the future of JS
wmsbill
2
290
Other Decks in Technology
See All in Technology
Oracle AI Database@Azure:サービス概要のご紹介
oracle4engineer
PRO
6
2k
LLMにもCAP定理があるという話
harukasakihara
0
320
小さく始める AI 活用推進 ― 日経電子版 Web チームの事例/nikkei-tech-talk47
nikkei_engineer_recruiting
0
250
2026 TECHFRESH 畢業分享會 - 開發日常大解密!從領域驅動到企業級上線
line_developers_tw
PRO
0
920
FDE という解 ― 暗黙知と明示知をつなぐ、伴走型エンジニアリング ―
otanet
0
150
非定型業務をAI slackbotで自動化する ~ 社内要望を自動壁打ちするbotを作った ~/automating-ad-hoc-work-with-ai-slackbot
shibayu36
0
640
Oracle AI Database@Google Cloud:サービス概要のご紹介
oracle4engineer
PRO
6
1.5k
Claude Codeをどのように キャッチアップしているか
oikon48
12
7.4k
RAG を使わないという選択肢
tatsutaka
1
220
脆弱性対応、どこで線を引くか
rymiyamoto
1
380
日本 Fintech 未来予測レポート 2027〜2028年(手動編集版)
8maki
0
2.2k
Chainlitで作るお手軽チャットUI
ynt0485
0
230
Featured
See All Featured
Reality Check: Gamification 10 Years Later
codingconduct
0
2.2k
Leading Effective Engineering Teams in the AI Era
addyosmani
9
2k
Agile Actions for Facilitating Distributed Teams - ADO2019
mkilby
0
200
Building a Scalable Design System with Sketch
lauravandoore
463
34k
AI Search: Where Are We & What Can We Do About It?
aleyda
0
7.6k
Building the Perfect Custom Keyboard
takai
2
790
Data-driven link building: lessons from a $708K investment (BrightonSEO talk)
szymonslowik
1
1.1k
Designing Experiences People Love
moore
143
24k
Automating Front-end Workflow
addyosmani
1370
210k
世界の人気アプリ100個を分析して見えたペイウォール設計の心得
akihiro_kokubo
PRO
71
40k
Designing Dashboards & Data Visualisations in Web Apps
destraynor
231
55k
エンジニアに許された特別な時間の終わり
watany
107
250k
Transcript
Hallo!
https://github.com/tc39/proposals
NodeJs Meetup
@wmsbill What is this?
@wmsbill this in the global scope Browser - window Web
worker - self NodeJS - module.exports
@wmsbill this inside a function?
@wmsbill this inside a function?
None
@wmsbill How to make this predictable? Reasoning the value of
this is tricky Function.prototype.bind Arrow function () => {}
With .bind()
With Arrow
@wmsbill Calling a knowing function
@wmsbill Extracting a method from an object
None
@wmsbill Two syntaxes Unary : :context.method() Binary context: :method()
@wmsbill Binary syntax
@wmsbill Unary syntax
@wmsbill
@wmsbill
@wmsbill
@wmsbill Bind operator is good for virtual methods But relies
on this to be bound
@wmsbill Composing without this
@wmsbill
@wmsbill
None
@wmsbill Pipeline operator |> It is a syntax sugar for
function composition It creates a way to streamline a chain of functions
@wmsbill Pipeline operator |>
@wmsbill
@wmsbill
@wmsbill
@wmsbill Function with more params
@wmsbill Function with more params
@wmsbill Awaiting a function
@wmsbill Awaiting a function
@wmsbill Awaiting a function
@wmsbill Awaiting a function
@wmsbill Awaiting a function
None
@wmsbill Smart pipeline
@wmsbill Smart pipeline Two types bare style and topic style
() or [] are disallowed in bare style When () or [] is needed, topic style is used # token is subject to change
@wmsbill What about curry?
None
@wmsbill F# pipeline proposal Extends the minimal proposal with an
await step Await step waits for the resolution of the previous step
@wmsbill F# pipeline proposal
@wmsbill
@wmsbill Partial application f(…) arity = n; partialapp(f(…)) arity =
m; m < n
@wmsbill
@wmsbill
@wmsbill Partial application in ES Achievable by Function.prototype.bind .bind() binds
context and parameters
@wmsbill
@wmsbill What about currying? We can achieve partial application with
curry Curry ≠ Partial application Curry returns arity n-1
@wmsbill
@wmsbill Partial application with arrow function
None
@wmsbill Partial application proposal Creates two new parameters tokens ?
For single argument . . . for multiple parameters
@wmsbill Partial application syntax
@wmsbill With arbitrary parameter
None
@wmsbill The . . . token Spread the unbound parameters
Useful when you want to bound first or last parameter
@wmsbill The . . . token
@wmsbill The . . . token
None
@wmsbill Partial application + pipeline
@wmsbill Partial application + pipeline
@wmsbill Should I use all of it in production? These
proposal are in very early stage The adoption of one, may change the syntax/semantics of other Not production ready (yet)
@wmsbill Let’s talk about something more solid?
None
@wmsbill [].flatMap syntax
@wmsbill [].flatMap syntax
[].flatMap x [].map
@wmsbill [].flatMap x [].map [].map guarantees the same array size
based on input [].flatMap doesn’t guarantees same array length as input array It could be used as filtering
@wmsbill [].flatMap as filter
@wmsbill #smooshgate
@wmsbill [].flatten
@wmsbill [].flatten syntax
@wmsbill [].flatten syntax
@wmsbill [].flatten syntax
@wmsbill So what is the deal?
MooTools
@wmsbill #smooshgate MooTools is an 11 years old ancient lib
They implemented [].flatten with different behavior The implementation + Elements Enhanced HTML component breaks the compatibility w/ [].flatten
https://youtu.be/loqVnZywmvw
@wmsbill TC39 had two options Change flatten to another name
(like smoosh) Break the internet
Array.prototype.flatten
Array.prototype.flatten
https://medium.com/@wmsbill https://twitter.com/wmsbill
[email protected]
Dankeshön!