just_astounded

4 ms·

1.
by just_astounded 9y ago
If you like rsync and javascript, I wrote https://github.com/claytongulick/bit-sync which is kinda fun.
2.
by just_astounded 9y ago
Fancy!
3.
by just_astounded 9y ago
There are a lot of reasons, honestly, and it's great beer conversation, but from a high level: producing a concrete instance that invokes a constructor function with a shiny pristine 'this' to build on is a pretty great patte
4.
by just_astounded 9y ago
While it hasn't changed their minds, I do see the authors of the proposal actively discussing and engaging with the community. That's better than nothing, I suppose.
5.
by just_astounded 9y ago
I remember when Crockford released the fantastic book, JavaScript The Good Parts. I disagreed with some of his opinions in that book, like avoiding the use of 'new', but that book - more than almost anything else, helped me educat
6.
by just_astounded 9y ago
Until wasm has GC, we're not likely to see much in the way of compile-to-web outside of C, C++, or Rust.
7.
by just_astounded 9y ago
> So why complain? So it is your opinion that the community and users shouldn't give feedback on the design and direction of the language they use every day? That's an interesting approach to openness.
8.
by just_astounded 9y ago
Yeah, I've only been doing OOP for about 22 years, so I'm pretty new to it. The point was that the syntactic sugar isn't needed. The 'class' sugar actually obscures the power of prototypal inheritance, and imho, dis
9.
by just_astounded 9y ago
Don't we already have solutions (closures/WeakMap) for hard encapsulation? Seems like '#' just pollutes the language and isn't really needed.
10.
by just_astounded 9y ago
I think the concern is that if you look here: https://github.com/tc39/proposal-private-fields/issues/14 and other places, you'll see this massive push back from the community, yet the proposal is moving
11.
by just_astounded 9y ago
Agreed. We already had solutions for inheritance, etc... using prototypes, which are more powerful than classic OOP. Now we're in sort of a mess hybrid thing where issues like this are mostly unsolvable in a clean way.
12.
JavaScript TC39 implementing hashmark private class fields(github.com)
36 points by just_astounded 9y ago|76 comments