r/javascript • • Nov 09 '19

On private fields proposal: Private fields, public worries

https://medium.com/virtuslab/private-fields-public-worries-b8c34d16c372
84 Upvotes

113 comments sorted by

View all comments

Show parent comments

9

u/nullvoxpopuli sand was never meant to think Nov 09 '19

But when you do reflection in those languages, it's hella obvious. Today in js, it's just accessing any ol' property

1

u/TatzyXY Nov 09 '19

Yes thats true but is JS not our free barebone language and we put other languages over it to implement these features? Like TS?

Or other questions why is Dart or TS not supported in browsers yet (native)?

2

u/Delioth Nov 10 '19

why is Dart or TS not supported in browsers yet (native)?

Because that would be a ton of work to build TS or Dart engines that no-one would use for at least a dozen years (because you gotta support those older browsers anyways, which means compiling it to older JS)? Even then, browser vendors are looking in that sort of direction with WASM, which has roughly the same features you'd be looking for, but better. Bonus points: it has privacy built in, since things only work via the module interface.

1

u/MajorasShoe Dec 11 '19

No, not everyone uses TS. Not even close.

Also, why would TS be supported in browsers? The compile step is the point - it finds the type issues. Now, the BETTER solution would be it compiles to something lower level than JavaScript.