2 ms·
I'm sympathetic to your position, but right now your comment doesn't carry much information. Why are they the right tool for the jobs? Which reasons are those?
by icebraining 7y ago
I'm sympathetic to your position, but right now your comment doesn't carry much information. Why are they the right tool for the jobs? Which reasons are those?
- bilekas 7y agoNot to offer information, I'm just objecting to the stance they seem to make that : "Hey we're solving the 'API' requirement problem' when there really is no problem.. If your backend only communcates with an SPA and nothing else, then yup, this is a good tool for that job.
- hatch_q 7y agoActually this doesn't solve the core API challenges that SPAs have - versioning and compatibility. Clients will simply run outdated frontend code. Imho this is more trouble than worth as it will bring all the problems that we had with WSDL. If i'd do a SPA that has 'node' backend, i'd just use typescript to model the API and you can have shared models and compile-time type safety.