@stvfrnzl you can subscribe for notifications on the #tc39 proposals here https://github.com/tc39/proposals

Then you can use https://caniuse.com/ to track implementation status.

I have seen other websites in the past that provide feature by feature status... but can't find them right now.

A good overview of changes discussed at #W3C and #TC39 related to #WebComponents :

https://eisenbergeffect.medium.com/the-future-of-native-html-templating-and-data-binding-5f3e52fda259

We may even get native #Signals in #JavaScript !

I hope they get a better syntax for templates this time. IMHO directives or custom mini-languages introduce unnecessary complexity with [often] limited capabilities. Embedded JS should be used one way (#JSX) or another.

Updates from the TC39 meeting in May 2023
https://dev.to/hemanth/updates-from-the-96th-tc39-meeting-4goe
#ES_Next_News #ECMAScript #JavaScript #TC39

@leaverou This was an interesting rabbit hole to dive down. Fundamentally I feel like there is a contradiction here:

First, private fields are intended to provide true, unspoofable encapsulation of state.

Second, proxies are intended to introspect and intercept operations on an object.

These are inherently conflicting goals and you cannot provide either without violating the other. This means using private fields + proxies will fundamentally be broken, the question is just about *how* it's broken.

Seems #TC39 went with the first option. We can certainly debate which one is better, and it's always possible the second approach would have a better outcome. But in the end if we did go that route there would be just as many blog posts about "Proxies considered harmful" or "Private fields aren't actually private, so why are we bothering, just use TypeScript".

This really feels like a "damned if you do, damned if you don't" situation.

I started writing a #tc39 proposal for a Primitive Proxy. It's my first time doing this, so I'd like to know if you guys find it useful, and what questions/objections/suggestions you may have! #javascript
https://github.com/hugoattal/tc39-proposal-primitive-proxy

Updates from the TC39 meeting in March 2023
https://dev.to/hemanth/updates-from-the-95th-tc39-meeting-ne5
#ES_Next_News #ECMAScript #JavaScript #TC39

every time i see “using” in c# or “from foo import *” in python, i throw up a little in my mouth

then feel a little more thankful for #TC39

I'm really happy that the collections in JavaScript are getting better each iteration with helper methods for querying/transforming data. The Set methods look great for unioning, etc https://github.com/tc39/proposal-set-methods#proposal

#tc39 #javascript #js
```markdown

```

Updates from the TC39 meeting in January 2023
https://dev.to/hemanth/updates-from-the-94th-tc39-meeting-48mb
#EsNextNews #EcmaScript #JavaScript #TC39

The Decorators proposal for #javascript is really exciting. There are so many good uses for them logging, security, request handling, etc.

The proposal is worth a read if you are at all interested in the future of JavaScript.

https://github.com/tc39/proposal-decorators

#tc39 #ecmascript

@null
You might want to look at the JavaScript Temporal API that's at Stage 3 in #tc39. It's solves a lot of the date and timezone horrors:
https://tc39.es/proposal-temporal/docs/
#javascript

Have a new Blogpost about importing CSS from ESModules in 2023!

Check it out!

#tc39 #CSS2022 #CssModuleScripts #webdevelopment #webdev #webdevelopers

https://blog.codemonument.com/2022-12-07-css-imports-from-esm

At what point, do you think, will we finally be able to use document.createElement("svg")? #HTML5 #JavaScript #TC39

Updates from the TC39 meeting in November 2022
https://dev.to/hemanth/updates-from-the-93rd-tc39-meeting-2n8f
#EsNextNews #EcmaScript #JavaScript #TC39

The ECMAScript proposal “Set Methods for JavaScript” advanced to stage 3. It provides the following Set methods:

* .intersection(other)
* .union(other)
* .difference(other)
* .symmetricDifference(other)
* .isSubsetOf(other)
* .isSupersetOf(other)
* .isDisjointFrom(other)

https://github.com/tc39/proposal-set-methods
#ECMAScript #JavaScript #TC39

#introduction 1/2

Hello! My current Big Project is fixing #localization, making it easier for software and sites to communicate in various human languages. So I'm spending quite a bit of time in #unicode and #tc39 trying to shepherd along spec proposals so that we can fix this for everyone. Nowadays I even get paid for this, on account of being a staff software engineer on the l10n team at #mozilla.

I love to see more language features like those that came to F# and C# and even Java come to JavaScript like records and tulles. It’s currently at Stage 2 but I hope in some form or fashion that it moves on https://github.com/tc39/proposal-record-tuple

#javascript #tc39

#introduction
I am passionate about making software, knowledge, and information accessible to everyone around the world.

To this end, I'm a Staff Software Engineer at Google on the #i18n engineering team. I lead the team that builds ICU4X, the open-source, modular, portable i18n library in #Rust. I chair #TC39 TG2 for better i18n in #ECMAScript.

I built octave-online.net to make scientific computing more accessible.

I like #boardgames, #hiking, #curling, #classicalmusic.

RT @tabatkins@twitter.com

By the by, the Freenode fuckery has meant we've moved both the TC39 and WHATWG rooms to Matrix:
* #tc39-general:http://matrix.org
* #whatwg:http://matrix.org

🐦🔗: https://twitter.com/tabatkins/status/1398075087618596866

Love causing me some #tc39 drama