1. 44
  1.  

  2. 11

    How is this not obviously satire? The very first bash command-line excerpt gave it away.

    1. 6

      I’m really confused, is this satire? How does an image appear in a source code file? I’m unable to verify any of these by looking at the project’s source code.

      1. 6

        I had to stop and work this out too. It’s a sad reality when you can’t quite work out whether some JavaScript developers really did decide to embed the entire Encyclopaedia Britannica in their library.

        1. 1

          Such an article that is not obviously satire (it doesn’t read as such to me) can give a lot of people the entire wrong impression about the projects listed.

          1. 2

            On the other hand, if people have trouble figuring out this is satire, maybe it doesn’t even give a wrong impression - as in, yes this is hyperbole but not far from reality so it reasonably approaches reality. So concluding that “this is madness” from such a satirical article is not completely wrong as reality is already “this is very close to madness”.

        2. 3

          It is.

          1. 2

            The node.js file from babel for reference: https://github.com/babel/babel/blob/master/packages/babel-core/src/api/node.js

            It’s a really well-done satire that many people will believe is true. Only thing, the twitter like part was the weakest part since you need twitter credentials to “like” stuff.

            I was hoping for a discussing on how to minimize the dependencies. Maybe agreeing on some meta-package included with all new npm releases containing the most commonly used libraries in one solid and well-integrated library.

            1. 6

              The twitter liking came close to making a very good point, but it’s a little opaque. The issue here is not just about bloat and wasted resources and slow startup times, but how well do you understand what it does? This is code that’s running, doing something, but what? Do you trust it?

              As satire, maybe the weakest part, but probably the most important lesson.

              1. 2

                When I started reading the article I assumed the author had used node’s request library to interact with twitter in the past and had their credentials saved in some kind of global cookie jar.

                The Encyclopædia Britannica one was the best though, I can seriously see that happening.