3 ms·
I'd say, more than anything, the benefit it provides is more personnel-related than anything. While there are definitely dedicated server-side and client side
by nkozyra 12y ago
I'd say, more than anything, the benefit it provides is more personnel-related than anything.
While there are definitely dedicated server-side and client side JS people, speaking the "same language" helps within teams and allows for some shared responsibilities.
That's appealing to large organizations with decent turnover.
- remon 12y agoI think you've touched upon the strongest argument for using JavaScript within a server stack. That said, that argument seems less strong for companies the size of Netflix, Yahoo, and so on. They don't exactly have problems recruiting top engineers. Curious stuff.
- nkozyra 12y agoRecruiting? No, absolutely not. But maintaining? I mean if you can move in and out of server and front side, that might build some lasting engagement with developers. It also encourages an ecosystem wherein almost any developer out there can work on either side for you.
- mtbcoder 12y agoIs that not essentially bending the entire server side stack to the will of the LCD developers because they are only familiar with JavaScript?