3 ms·

> According to who? FIG? According to the vast majority of authors of the most widely used and tested PHP libararies. > Are you aware that php has a built in

by jpnave 10y ago

> According to who? FIG? According to the vast majority of authors of the most widely used and tested PHP libararies. > Are you aware that php has a built in auto loader that supports namespaces and is written in C? You mean the autoloader builtins that composer uses under the hood already? This is better than a 1 line include how exactly? > Ah, the NPM/Composer golden brick road to development. Aka, the "I don't know what this is but I'm gonna lick it" approach to development I don't understand what you're saying here, everyone should be writing their own libraries from scratch? It has always been up to the developer to vet the dependencies they choose to include in their project. That applies to every language ecosystem, not just Node.

stephenr 10y ago
> According to the vast majority of authors of the most widely used and tested PHP libararies. So, FIG. "Group of developers say that groups' work is the best. News at 11." > You mean the autoloader builtins that composer uses under the hood already? No, spl_autoload is a working namespace aware autoloader. Composer uses a bunch of userland code. > I don't understand what you're saying here, everyone should be writing their own libraries from scratch? Did I say that? I've seen, multiple times the negative consequences of the current fad to rely on 25 separate, single-purpose 3rd party Libs, all of which are basic functionality that a well thought out library would give you, but with the added "bonus" of each relying on 20 other libraries to do basic things. > It has always been up to the developer to vet the dependencies they choose to include in their project. That applies to every language ecosystem, not just Node. Do the vast majority of developers know that? Because the ones I've had the "pleasure" of working with, definitely don't.

by jpnave 10y ago

stephenr 10y ago

> According to the vast majority of authors of the most widely used and tested PHP libararies. So, FIG. "Group of developers say that groups' work is the best. News at 11." > You mean the autoloader builtins that composer uses under the hood already? No, spl_autoload is a working namespace aware autoloader. Composer uses a bunch of userland code. > I don't understand what you're saying here, everyone should be writing their own libraries from scratch? Did I say that? I've seen, multiple times the negative consequences of the current fad to rely on 25 separate, single-purpose 3rd party Libs, all of which are basic functionality that a well thought out library would give you, but with the added "bonus" of each relying on 20 other libraries to do basic things. > It has always been up to the developer to vet the dependencies they choose to include in their project. That applies to every language ecosystem, not just Node. Do the vast majority of developers know that? Because the ones I've had the "pleasure" of working with, definitely don't.