3 ms·
My experience with JavaScript is limited, but knockout is what I use because it's what makes sense.
by mgaunard 3y ago
My experience with JavaScript is limited, but knockout is what I use because it's what makes sense.
- chrisco255 3y agoKnockout is fine to use if your JS doesn't exceed 1000 lines or so. After that, in more complex apps, 2 way data binding becomes an absolute mess of side effects.
- recursive 3y agoI've used knockout in much larger apps than this. I still don't understand what side effects people are talking about when they say this. I don't love knockout, but I find it easier to debug than react. Mainly because stuff is synchronous, meaning the thing that caused the change is above the problem in the callstack. In react, a lot of stuff goes through an async work scheduler, so the originator of the problem is long gone.
- mgaunard 3y agoI've built frontends that are much larger than that (and I'm not even a frontend developer) and they all worked fine. If anything it makes it clear what's going on and when, which is important for the kind of stuff I do which has a lot of interconnected components which are constantly refreshing.