SebastianVerified account

@sebmck @rvagg I think my point still stands that TC39 as a collective is ineffective at translating reality into usefulness for non-browser

@sebmck @rvagg contrary, it can only see front-end “reality”, which translates into continual pain for those of us having to maintain node.

@fishrock123 @rvagg also the ecmascript spec is very clearly not browser focused. it's meant to be as generic as possible.

@sebmck @rvagg yeah right

@fishrock123 @rvagg what are you basing that off?

@fishrock123 @rvagg btw i don't really want to have this discussion if there's just going to be dismissal

@sebmck Apologies, it gets incredibly frustrating when a platform is handed stuff and expected to implement it, conflicting or not.

@sebmck There’s a a forward motion of filling ECMA with everything possible. 1) because that’s effectively what TC39 exists for now (..)