3 ms·

> However as Javascript is maturing and branching out to server-side programming and at the same time the client side becomes more complex, you can't keep re-wr

> However as Javascript is maturing and branching out to server-side programming and at the same time the client side becomes more complex, you can't keep re-writing all your tools every couple of years, or even every 5 years. The client side becoming more complex is the reason why new tools keep being developed. > If you don't have that, you are going to be subject to increasing exponential costs that are going to weigh very heavily on the language. Soon, you'll need to spend almost all your resources just re-writing stuff. No one is forced to rewrite their code when a new tool is released.

deleted 10y ago
[deleted]
shakna 10y ago
> the reason new tools keep getting developed That's a bad reason. There's a solidly developed C library for dealing with HTTP, which is mature. libcurl. HTTP is developing, with WebSockets and the rest of the 2 spec. C developers didn't immediately ditch what they use and fragment the ecosystem. Curl got updated. Python has a mature library, which is much younger than curl, called requests. Python didn't fragment, they updated requests. Here's where I have the biggest issue: * Advice for C on which library to use, is probably still up to date 10 years later. * Advice for Python on which library to use, is probably still up to date 5 years later. * Advice for JavaScript on which library to use, is probably out of date 1 year later.