Panel Discussion: The Future of JavaScript

Rate this content
Bookmark

FAQ

Maggie Johnson-Pinn's favorite upcoming proposal is 'records and tuples', which relates to her history with DateTime and the need for immutable constructs in JavaScript.

TC39, or Technical Committee 39, is the standards committee responsible for ECMAScript, which is the standard that defines JavaScript. It consists of a group of delegates from various organizations who collaborate to evolve the JavaScript programming language.

Maggie Johnson-Pinn works for Microsoft and has been an active participant in TC39. She is notable for originally bringing the temporal proposal to the committee.

The temporal proposal is an initiative brought to TC39 that aims to improve date and time handling in JavaScript. This proposal addresses the need for more robust and flexible date-time APIs in the programming language.

Standardizing JavaScript ensures uniformity and compatibility across different web browsers and devices. This uniformity allows developers to write consistent, reliable code that works universally, helping maintain the functionality and accessibility of the web.

Organizations can participate in TC39 by becoming a member of Ecma International, the standards organization under which TC39 operates. Membership requires a fee and allows an organization to become officially involved in the development and standardization of JavaScript.

A proposal in TC39 goes through several stages: Stage 0 (strawman), where the idea is introduced; Stage 1 (proposal), where the problem and solution are formulated; Stage 2 (draft), where the exact form of the solution is specified; Stage 3 (candidate), where the proposal is implemented in browsers for feedback; and Stage 4 (finished), where the proposal is officially part of the ECMAScript standard.

Updates on new JavaScript proposals can be found on the TC39 GitHub repository under 'proposals'. Each proposal is documented with its current stage, discussions, and updates, providing a transparent view of its progress.

Hemanth HM
Hemanth HM
Jordan Harband
Jordan Harband
Maggie Johnson-Pint
Maggie Johnson-Pint
Rick Button
Rick Button
39 min
10 Jun, 2021

Comments

Sign in or register to post your comment.
Video transcription, chapters and summary will be available later.

Check out more articles and videos

We constantly think of articles and videos that might spark Git people interest / skill us up or help building a stellar career

React 19 Panel Discussion
React Summit 2024React Summit 2024
27 min
React 19 Panel Discussion
Ryan Carniato
Evan Bacon
Sathya Gunasekaran
Tim Neutkens
Brooks Lybrand
5 authors
The Talk revolves around React 19 and the React compiler, highlighting its new APIs, optimizations, and impact on frameworks like Next.js. The React compiler has undergone multiple iterations, resulting in improved performance and alignment with developers' expectations. The integration of React with Next.js simplifies rendering and offers free optimizations. There is excitement about the opt-in approach of React Server Components and the potential of underrated features like suspense and transitions. Overall, React's influence on the JavaScript ecosystem and UI libraries is acknowledged and appreciated.
Panel Discussion: Future of React
React Summit US 2024React Summit US 2024
39 min
Panel Discussion: Future of React
Watch video: Panel Discussion: Future of React
Kent C. Dodds
Shruti Kapoor
Mark Erikson
Eli White
Mofei Zhang
Theo Browne
Tom Occhino
7 authors
We're going to be doing a future of React panel discussions. React 19 is in RC stage and we're excited to hear when it will be stable. The React compiler is here to stay and is the future of developer experience and tooling. React 19 brings exciting features like RSCs and consolidation of the framework. React's commitment to community and innovation is commendable. The React team values feedback and actively engages with the community. React's future includes supporting the community and enabling smooth migrations. There's a need to teach underlying concepts and educate AI systems. Teaching and adapting to React can be challenging. The React compiler changes default re-rendering behavior. Collaboration with Next.js and Vercel has been valuable for React's development. Appreciation for the community and partnerships with Vercel and Microsoft.
Standardizing Signals in TC39
JSNation US 2024JSNation US 2024
29 min
Standardizing Signals in TC39
I'll be talking about standardizing signals in TC39. Immediate mode wipes out the whole screen and writes a new one, while retained mode changes only what is necessary. Signals represent a cell of data that can change over time. The correct solution is to topologically sort dependencies and evaluate them in a coherent order. Standard signals allow for code sharing across frameworks and the creation of reusable infrastructure. The signal API is designed to be wrapped by different frameworks. Standards can achieve more portability and reduce the need to lock into specific ecosystems. The API includes a watcher, a set of signals being observed, with a synchronous callback made when the first member becomes potentially dirty. The speaker discusses how signals relate to state management libraries in React and mentions the potential for signals to become a web standard in the future.
Future Features of JS?!
JSNation 2022JSNation 2022
28 min
Future Features of JS?!
Top Content
Welcome to the future features of JavaScript, including proposals for array operations, throw expressions, records and TPUs, pipeline operators, and more. The talk covers the introduction of type assertions for imported files, non-mutating array operations, and the simplification of error handling. It also explores the concept of immutability with records and TPUs, and the use of the pipeline operator to simplify code. Other proposals include Map.implace, IteratorHelper, slice notation, type annotations, Array UNIQBY, number ranges, and the Function 1 proposal.