4 ms·
> I lost the argument and that org chose Knockout.js with JSPs instead. You can guess how expensive that "pragmatic" decision turned out. would have thought R
by 5350-uiop-1130 4y ago
> I lost the argument and that org chose Knockout.js with JSPs instead. You can guess how expensive that "pragmatic" decision turned out.
would have thought React was the boring or pragmatic option in this scenario...
- zero_shift 4y agoNot in late 2015, if you came from a Java background
- gedy 4y agoKnockout on top of JSP in a Java shop in 2015? That's very reasonable. React was not a good choice for everyone, esp then.