Re: Coudn't agree more
"Hahaha. You're going to pay to access these sites right?"
Indirectly, yes - indirectly because the payment might, for example, take the form of me buying something being sold via the site versus, say, going somewhere else and buying that something.
"You know, actual hard currency that the developers who would then have to actually spend time writing and maintaining these summaries of every individual JS file they're using"
How positively evil of me. Next thing you know, I'll be expecting developers to put comments in their source code, or something crazy like that.
"I love the admission that you can't be bothered using Noscript - but you'd stop and read the summaries of every individual JS file"
Way to twist what I said into something I didn't. Go you.
I said detailing those scripts would encourage me to do so. It would be a positive step by the developer, and make me feel more positive about using the site, and gives me the opportunity to make a more informed decision.
I'm intrigued, as well, how the fact that I use NoScript can be interpreted as me saying I can't be bothered to use NoScript. I guess you're suggesting that I can't be bothered to look at the menus - but the menus are next to useless for deciding which scripts are necessary, which are frills, which I'd rather not trust, and so on. All they do is tell you the domains in question and give you the option of allowing or denying them. That is not an informed choice.
"before reading a blog post?!"
Poor example, but I'll take it on the chin because I should really have specified commercial sites: It's commercial sites on which I'm more inclined to want to make an informed choice about what scripts are in use and what they are doing.
When it comes to things like blog posts and basic/more static sites, I'm much less worried about what the Javascript is doing - because I'm much less likely to be inclined to enable it for those sites anyway. Which itself neatly counters your opening paragraph and your objection to all these poor web developers having to spend time writing their summaries, without getting anything in return to pay the rent: these web developers/site owners aren't being paid much, if anything (myself included), but by the pure magic of the types of site, they don't have to worry about JS declarations.
Having said that:
1) many (most?) will likely be using CMSs developed by others, who may very well be making good money doing it - and it's these people who could build that functionality into those CMSs. (They're more likely to know what the systems use, too, than Joe Blogger who is using it for his site.)
2) those websites will quite often work without Javascript; it might be less functional, but IME they are usually still readable, so it becomes irrelevant.
"Sites that require Javascript to work properly require Javascript to work."
Except when they don't, and the Javascript is there due to cluelessness - where javascript is used for basic functionality like links.
"Other websites are available. ;)"
Well done for basically telling me what I said when I said I can look elsewhere if a site doesn't work without Javascript.