Sebastian Markbage: Minimal API Surface Area | JSConf EU 2014

Channel:JSConf · Length:24:28 · Published:2014-10-15 · Views:70747

Watch on YouTube

Summary

Sebastian Markbage explains how React is moving toward a minimal API surface by leaning on language features and patterns instead of dedicated framework APIs. He also touches on JSX and syntax proposals for future JavaScript.

Why HN recommends it

HN cites it as a statement of React's early design philosophy of keeping APIs small and understanding JavaScript itself.

I found this talk on the topic very interesting — HN, 2017

Web development · Software architecture & design

Subtitles (excerpt)

I'm Sebastian, that thing there is my last name. I live in California now, but, um, it's actually really nice to be back in Europe where Umlauds and accents are normal occur answers. Sorry for my bad voice, I think I'm allergic for bad API. I work for Facebook now, I'm not an evangelist, I just code stuff, I'm just some dude. I also represent Facebook on TC 39 on standards committee on ECMAScript. Don't worry, the bad parts are not mine, they're someone else's. I guess a lot of people here have a favorite library. There was your favorite library ‑‑ nothing? React that's a good call. (Laughing) do you guys use libraries for everything, like the same library, like utility library, like underscore in how many people use underscore? Cool. JQuery? Something like Angular High Level YUY? Oooo ... sorry, guys (Laughing) well, this is the great part about JavaScript, our community, if you look platforms like EEO, Andriod or proprietary. Do whatever the platform owner tells you that's right to do. There's a stock secret black box you can't touch, everyone tells you you can't do better than they did, which is not true, let's be honest, it's not true in the Java committee. We have a vibrant community of framework,

On Hacker News

That's indeed a very good advice. All abstractions have a cost and no abstraction is better than the wrong abstraction. I found this talk on the topic very interesting [VIDEO] — msangi, 2017-02
While underscore is indeed widespread, don't let libraries keep you from thoroughly understanding JavaScript: [VIDEO] — smhg, 2015-07
I am still not over the collapse of Gatsby (for reference i nearly joined the company in 2017, was saved only by my own character flaws). They rode the highs - being the default docs tool for React, and building a massive ecosystem of integrations you could install out of the box. But too many abstractions, divided goals between cloud and OSS, and the better stewardship/design of Nextjs brought i… — swyx, 2024-09
I'm a bit torn on the hooks feature since it seems like a great example of something that's easy but not simple [1], as well as going against React's prior principle of minimizing the API [2]. I'm glad the article also shows how to use the more traditional API as well, even if it is a bit more verbose. [1]: [LINK] [2]: [VIDEO] — iansinnott, 2020-12
I don't agree either. The first part of the argumentation is indeed based on the author's feelings. The second part I don't think is an issue for most real world use-cases (Objects, Strings and, to a lesser extent, Numbers). On the underscore (_.defaults) recommendation: let's set our goals straight [1]. Aim for a good level of JavaScript understanding. Instead of library knowledge to make up for… — smhg, 2015-07

Related videos