Upgrade to PRO for Only $50/Year—Limited-Time Offer! 🔥
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Back to the future of JS
Search
Willian Martins
July 03, 2018
Technology
1
81
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
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
98
Back to the future of JS II: Beyond what we can foresee
wmsbill
0
120
Back to the future of JS.
wmsbill
0
11
Node conf ar 2018.
wmsbill
0
600
Back to the future of JS
wmsbill
2
280
Other Decks in Technology
See All in Technology
AI 駆動開発勉強会 フロントエンド支部 #1 w/あずもば
1ftseabass
PRO
0
400
プロンプトやエージェントを自動的に作る方法
shibuiwilliam
13
11k
5分で知るMicrosoft Ignite
taiponrock
PRO
0
390
re:Invent2025 コンテナ系アップデート振り返り(+CloudWatchログのアップデート紹介)
masukawa
0
390
LLM-Readyなデータ基盤を高速に構築するためのアジャイルデータモデリングの実例
kashira
0
260
2025年 開発生産「可能」性向上報告 サイロ解消からチームが能動性を獲得するまで/ 20251216 Naoki Takahashi
shift_evolve
PRO
1
200
WordPress は終わったのか ~今のWordPress の制作手法ってなにがあんねん?~ / Is WordPress Over? How We Build with WordPress Today
tbshiki
1
810
AWS Security Agentの紹介/introducing-aws-security-agent
tomoki10
0
300
AIの長期記憶と短期記憶の違いについてAgentCoreを例に深掘ってみた
yakumo
4
410
AI駆動開発における設計思想 認知負荷を下げるフロントエンドアーキテクチャ/ 20251211 Teppei Hanai
shift_evolve
PRO
2
420
ログ管理の新たな可能性?CloudWatchの新機能をご紹介
ikumi_ono
1
850
regrowth_tokyo_2025_securityagent
hiashisan
0
250
Featured
See All Featured
Connecting the Dots Between Site Speed, User Experience & Your Business [WebExpo 2025]
tammyeverts
10
730
Docker and Python
trallard
47
3.7k
Building a Modern Day E-commerce SEO Strategy
aleyda
45
8.3k
Navigating Team Friction
lara
191
16k
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.6k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
286
14k
Balancing Empowerment & Direction
lara
5
800
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
46
2.6k
The Cult of Friendly URLs
andyhume
79
6.7k
StorybookのUI Testing Handbookを読んだ
zakiyama
31
6.5k
Unsuck your backbone
ammeep
671
58k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
122
21k
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!