4 ms·
Web apps have been tilting more heavily toward the frontend (using a backend as an API/data layer), and I don't see that slowing down any time soon, so the fron
by lowboy 12y ago
Web apps have been tilting more heavily toward the frontend (using a backend as an API/data layer), and I don't see that slowing down any time soon, so the frontend is the way to go, IMO.
If we're targeting the frontend and assuming OP's friend has limited experience programming, there's a benefit to learning the same (flawed) language in both the back and frontend, instead of learning two languages. Even if that one language is flawed.
I've shared code between Node and the browser using Browserify [0], and it's pretty easy. Page size can take a hit if you use modules that are meant for the backend and have large dependency graphs, but even then it could be worth it.
[0]: http://browserify.org/ http://browserify.org/