Upgrade to PRO for Only $50/Year—Limited-Time Offer! 🔥
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Node conf ar 2018.
Search
Willian Martins
October 19, 2018
Technology
0
560
Node conf ar 2018.
Willian Martins
October 19, 2018
Tweet
Share
More Decks by Willian Martins
See All by Willian Martins
Empirical Observations on the The Future of Scalable UI Architecture
wmsbill
0
150
Além do else! Categorizando Pokemóns com Pattern Matching no JavaScript
wmsbill
0
870
De volta ao Futuro do JS: As próximas features e propostas incríveis
wmsbill
0
100
Back to the future of JS II: Beyond what we can foresee
wmsbill
0
130
A, B, C. 1, 2, 3. Iterables you and me.
wmsbill
0
97
Back to the future of JS II: Beyond what we can foresee
wmsbill
0
120
Back to the future of JS.
wmsbill
0
11
Back to the future of JS
wmsbill
1
80
Back to the future of JS
wmsbill
2
280
Other Decks in Technology
See All in Technology
乗りこなせAI駆動開発の波
eltociear
1
1k
Edge AI Performance on Zephyr Pico vs. Pico 2
iotengineer22
0
110
[JAWS-UG 横浜支部 #91]DevOps Agent vs CloudWatch Investigations -比較と実践-
sh_fk2
1
240
大企業でもできる!ボトムアップで拡大させるプラットフォームの作り方
findy_eventslides
1
610
今からでも間に合う!速習Devin入門とその活用方法
ismk
1
550
re:Invent 2025 ~何をする者であり、どこへいくのか~
tetutetu214
0
160
re:Invent2025 コンテナ系アップデート振り返り(+CloudWatchログのアップデート紹介)
masukawa
0
320
Playwright x GitHub Actionsで実現する「レビューしやすい」E2Eテストレポート
kinosuke01
0
460
コミューンのデータ分析AIエージェント「Community Sage」の紹介
fufufukakaka
0
450
Overture Maps Foundationの3年を振り返る
moritoru
0
160
LLM-Readyなデータ基盤を高速に構築するためのアジャイルデータモデリングの実例
kashira
0
220
モバイルゲーム開発におけるエージェント技術活用への試行錯誤 ~開発効率化へのアプローチの紹介と未来に向けた展望~
qualiarts
0
660
Featured
See All Featured
Art, The Web, and Tiny UX
lynnandtonic
303
21k
Designing for Performance
lara
610
69k
Designing Dashboards & Data Visualisations in Web Apps
destraynor
231
54k
VelocityConf: Rendering Performance Case Studies
addyosmani
333
24k
The Invisible Side of Design
smashingmag
302
51k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
46
2.6k
Become a Pro
speakerdeck
PRO
31
5.7k
A Tale of Four Properties
chriscoyier
162
23k
GraphQLの誤解/rethinking-graphql
sonatard
73
11k
Build The Right Thing And Hit Your Dates
maggiecrowley
38
3k
Large-scale JavaScript Application Architecture
addyosmani
515
110k
Thoughts on Productivity
jonyablonski
73
5k
Transcript
¡Hola!
https://github.com/tc39/proposals
v. NodeConf Ar
@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?
@wmsbill What is this?
@wmsbill What is this?
@wmsbill this inside a function Browser - window NodeJS -
global object
@wmsbill this with new operator
@wmsbill this with new operator
@wmsbill this with strict mode
@wmsbill this with strict mode
@wmsbill Setting this value Function.prototype.call Function.prototype.apply Function.prototype.bind new operator Object
member function
@wmsbill Setting this value
@wmsbill How to make this predictable? Reasoning the value of
this is tricky Function.prototype.bind Arrow function () => {}
None
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 Unary syntax
@wmsbill Binary 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 (not in the initial spec anymore)
@wmsbill Partial application syntax
@wmsbill With arbitrary parameter
None
@wmsbill Partial application in template string
@wmsbill Partial application in template string
None
@wmsbill The . . . token Spread the unbound parameters
Useful when you want to bound first or last parameter
@wmsbill The . . . token
@wmsbill The . . . token
@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)
https://medium.com/@wmsbill https://twitter.com/wmsbill
[email protected]
https://www.smashingmagazine.com/2018/10/taming-this-javascript-bind- operator/
¡Gracias!