After a year using Node.js, the prodigal son returns

Grant Edwards grant.b.edwards at gmail.com
Fri May 6 09:45:13 EDT 2016


On 2016-05-06, Chris Angelico <rosuav at gmail.com> wrote:
> On Fri, May 6, 2016 at 12:49 PM, Michael Torrie <torriem at gmail.com> wrote:
>> On 05/04/2016 02:59 AM, Steven D'Aprano wrote:
>>> A year ago, Gavin Vickery decided to move away from Python and give
>>> Javascript with Node.js a try. Twelve months later, he has written about his
>>> experiences:
>>>
>>>
>>> http://geekforbrains.com/post/after-a-year-of-nodejs-in-production
>>
>> Very interesting.  Frankly Javascript sounds awful.  Even on the front end.
>
> https://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript
>
> JavaScript is terrible. Really, really bad. And because of that, it
> has the potential to sweep the world.

If your reasoning is correct, it'll never be able to overtake PHP.

I've never written anything over a hundred or two lines in JavaScript,
but for small stuff it seems OK -- though as others have noted there
are some oddly missing batteries that result in use of a lot of small
external libraries for things that any C, PHP, or Python user would
have expected to be in the standard library.

-- 
Grant Edwards               grant.b.edwards        Yow! I'm wearing PAMPERS!!
                                  at               
                              gmail.com            




More information about the Python-list mailing list