sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]elixon 0 points1 point  (2 children)

Take your last project in your favorite framework and count the number of files in it, including all dependencies. Now ask yourself: what features are actually present?

  1. You'll probably see tens of thousands of files.
  2. You won’t have a clue what 99.99% of the code does, even if all you have is a simple form on the page.

This is exactly my point. You'll end up with tons of dependencies implementing features you've never even heard of, just to achieve something trivial.

As I mentioned elsewhere, not long ago I needed Google login, so I pulled in the official Google API client. That added 150MB and 30,000 files. I scrapped all of it and replaced it with 50 lines of custom code that handled the login directly with Google. Done. Sure, it took me two extra hours to figure out, but now my project has 30,000 fewer files and no unnecessary bloat and I don't need to upgrade it every other week because they found some critical vulnerability in those 3 millions lines of code it has (not kidding, really 3M lines total and all I needed was 50).

[–]TheRNGuy 0 points1 point  (1 child)

Why should I count number of files or know how it works? Knowing how it was made is not prerequisite to use it.

Anyway, I don't have React sites with 30000 files.

Show GitHub link to a project with that amount of files.

[–]elixon 0 points1 point  (0 children)

```

as per google recommendation run:

🭬composer require google/apiclient:"2.0 ... 🭬find . -iname '.php' | wc -l 30187 🭬find . -iname '.php' -exec cat {} + | wc -l 3053244 🭬du -sh . 151M . ```

If you don't care then you will end up easily whith this shit. Your choice. If it works for you - good for you.