Lmst

I'm gonna settle it once and for all:

the tc39 should adopt the F# style for pipeline operator.

No questions asked.

#FunctionalProgramming #JavaScript #TC39 #ECMAScript #ECMA262 #FP #PipelineOperator

Every so often I check to see if CSS anchor positioning is ready. Almost there in Safari/Firefox. :blobcateyesR:

Popover API already makes things so much cleaner, so hopeful all the anchor implementations ship in a stable shape. Chrome's seems to work pretty great from testing my use cases with various menus.

Updating legacy code this weekend to match the spec 1:1 so the JS can be dropped after release.

#tc39 #javascript

During tonight's AmsterdamJS #Meetup Special Edition with #TC39 Members (1800 CET), I will share the history of the #JavaScript Decorators proposal, which is now in Stage 3 of Ecma TC39's standardization process www.meetup.com/amsterdamjs/...

AmsterdamJS Special Edition: A...

Updating some older Typescript 4.x code to TypeScript 5 latest. Decorator heavy code, so nice to get it all refactored to ESDecorators Stage 3 syntax. Definitely an improvement, especially having `context.addInitializer`.

One minor headache in that I also had to update the webpack/ts-loader version to latest after noticing issues in the transpiled output.

#TypeScript #TC39

#Mozilla Standards Positions. This page tracks Mozilla's positions on open Web and Web-related specifications submitted to standards bodies like the #IETF, #W3C, #WHATWG, and #Ecma #TC39. Please remember, this isn't a commitment to implement or participate; it's just what we think right now. See dev-platform to find out what we're implementing. https://mozilla.github.io/standards-positions/

#Development #Proposals
TC39 advances a few JavaScript proposals · Three features are ready to join ECMAScript https://ilo.im/162h89

_____
#TC39 #EcmaScript #JavaScript #WebDev #Frontend #Backend

Highly recommended article by @ryancarniato on #JavaScript Signals and scheduling of async funcs.

I had my own share of problems (in Lit) with the #TC39-#Signal proposal, but failed to blog about it so far. Glad others recognize it could be too early to standardize…

Scheduling Derivations in #Reactivity:

https://dev.to/this-is-learning/scheduling-derivations-in-reactivity-4687

Anybody on #TC39 want to champion an ECMAScript proposal? Before I write a whole explainer document I’d like to make sure it isn’t wasted effort.

In short: Symbol.call, a well-known symbol, which can be used as a method name to make an object callable. Prior art: #Ruby’s call(), E’s run (), C++’s operator(). Allows your class’s instance to act as a Functor Object, and eases use of Method Object pattern. Gives us a way to make callables have their own “this.”

#JavaScript #JS #WebDev

class Frobnicator {
constructor(x, y) {
this.x = x
this.y = y
}
[Symbol.call](z) {
return z * this.#product
}
get #product() {
return this.x * this.y
}
}

const ten = new Frobnicator(2, 5)
console.log(ten(3), "thirty")

Twice a year, due to a very old system, many assumptions, user expectations, and a bright mind that decided to set a database in Europe/Amsterdam TZ, we have to deal with at least a bug regarding time issues. I cannot wait for Temporal to be fully implemented in all the platforms.

#javascript #temporal #tc39

https://developer.mozilla.org/en-US/blog/javascript-temporal-is-coming/

Just noticed this #js behaviour found it interesting/surprising

```javascript
let o = {}
let i = 0;
o?.f?.(i++)
```

The value of `i` is `0` after this expression. I would have thought that the orders of evaluation would still lead to `i++` occurring even if the method call is short circuited. But `i++` never evaluates.

#js #javascript #tc39 #webdev

Updates from the TC39 meeting in December 2024
@gnumanth
https://dev.to/hemanth/updates-from-the-105th-tc39-meeting-3gkh

#ECMAScript #JavaScript #TC39

@deebloo I think the world would be better if instead of moving "browser features" to JS build tools we should put the same effort/time/resources into standardizing the server interface as it prepared to deliver HTML to the browser so that we could get a single coordinated SSR solution.

#tc39

Updates from the 104th #TC39 meeting #javascript https://dev.to/hemanth/updates-from-the-104th-tc39-meeting-14cp

"So please, I beg everyone influencing [JavaScript], when considering a new feature, please apply a higher bar than 'Wouldn't it be nice if we could also write it this way?'" https://scribe.rip/4e83096239b9

#JavaScript #TC39 #programming

TC39 advances 10+ ECMAScript proposals
@sarahgooding @SocketSecurity
https://socket.dev/blog/tc39-advances-10-ecmascript-proposals-key-features-to-watch

#ECMAScript #JavaScript #TC39

#Development #Outlooks
TC39 advances 10+ ECMAScript proposals · Prominent JavaScript features to keep an eye on https://ilo.im/160e65

#Proposals #TC39 #ECMAScript #JavaScript #Browser #WebDev #Frontend

The "on-topic" channel has now lost all relation to the topic #tc39

OH at plenary “if people would stop using the word orthogonality, that would be great” #TC39

The overall cognitive capacity of TC39 delegates is reflective of the last hour or two of the final day, day three. the off-topic channel has completely gone off the rails, and the on-topic channel is just barely hanging on. Contributions are constructive yet somehow also unhinged.

we're halfway through day two.

#tc39

Three proposals advanced to stage 4 in today’s @TC39 plenary, which means they are now stable and have or will soon ship in browsers and tooling! :tc39: :javascript: :ablobcatbongo:

Iterator Helpers, a massive quality of life improvement when it comes to using iterators. You’ll no longer have to spread an iterator into an array to filter it for example!
JSON Modules, which have long been supported by bundlers and can now be used natively in ESM
Import Attributes (formerly known as Import Assertions), the mechanism that JSON modules are built on top of but with a wider range of use cases

#js #javascript #ecmascript #tc39

#TC39

Client Info