Why does javascript-frameworks-resources.md mix resources?

[eshellman]

hoping to get some historical perspective from @vhf

Early on, a javascript frameworks resource list, including books, courses, tutorials, etc., was split off of the main free books list. At that time, there were no separate lists for courses, tutorials, etc.

7362e06

One result is that contributors are confused about where js-related resources belong.

Given the very different complexion of the repo now, does it still make sense to split off js frameworks?

Feedback from the community requested.

[vhf]

I created this file because I was getting a lot PRs from people trying to add their favorite JS framework documentation or example blogpost to the -books files. It was an easy way of channeling all JS non-book content to a single place.

~1 year later, @sindresorhus started the awesome project. Now that there are a bunch of good, well curated javascript lists, I'd say the need of maintaining a separate one in this repo doesn't make much sense anymore.

What I'd suggest is:

• Getting this repo better integrated in the awesome lists ecosystem, occasionally redirecting there people trying to add to this project things that are not books,
• Removing the JS separate lists we have here in favour of the awesome equivalents, potentially replacing the file content with a link as a manual, temporary redirection,
• More importantly, I wouldn't start adding things that are too far away from actual books to the books lists.

Which means that to the question

does it still make sense to split off js frameworks?

I would say for: Yes, it makes sense for them to be separate things. It doesn't make much sense to maintain these files here though, as long as they are not books.

Up to you obviously. :)