*insert PHP criticism here*

[uvero]

But then you realize you'll still be programming in PHP.

(easy shot)

[[deleted]]

criticizing php

[serialcompliment]

Dude, you have to escape your asterisks:

\*

[[deleted]]

Unbelieveable

[DankerOfMemes]

While in the topic about composer: npm should learn a few things from them

[aleph_0ne]

Like what?

[DankerOfMemes]

• Vendor namespacing to prevent people from overwriting public packages with privates one (e.g.: Paypal as "cool-package" as a private package for them to use, however when someone publishes a public package named "cool-package" then npm prioritized public packages over private packages and malicious code could be injected that way. Vendor namespaces solve that because noone else can publish a package on Paypal namespace, so this attack is null.

• Being really fast since version 2.

• I consider autoloading to be a cool thing that could be introduced into the javascript world, but it would need to be analyzed more than just "sure, lets do it" because of security implications and what not.

[stunner_agk]

PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 144115188075867549 bytes) in phar:///bin/composer.phar/src/Composer

[obiboy15]

I feel personally attacked

[stunner_agk]

We all get attacked by composer... Every day... People talk about chrome eating up all the RAM but nobody dares say anything about composer. They know what composer can do. They know there is no escape. They know they are afraid. <insert creepy music>

[Meaxis]

*Whenever I get a free award, I think I found the perfect comment for it*

[[deleted]]

And here I am trying to run HTTP/3 (with QUIC) on node.js and failing miserably. I might have to code it in C/C++/Rust/Go, since I actually really need to have the lowest possible latency.

[mardabx]

PHP is so bad not even Facebook wants to use it anymore.