[jgalt212]

> Web devs should make sites that work without javascript, so that turning on NoScript is also a solution.

Ideally, I guess that would be true, but from a development cost perspective and user interface perspective that is just not possible in 2015.

[grx]

For complex platforms I may see your point. But what about personal pages or blogs (including hosted like Wordpress)? Why do webdevs even remotely consider publishing an empty webpage in case the client does not run javascript?

What do you think my impression of your website is when all I see is a blank page or an endlessly spinning loading wheel?

[jgalt212]

Yes, I agree. For static content pages, the content should largely render and its content should be largely digestible whether or not the client's javascript engine is running.

That being said, an easy defense against webscrapers and content re-purposers is to make sure the client is running javascript.

Of course, there are ways around this, but I liken it to this scenario: If there are two similar houses on a block and only one has an alarm system, the cat burgler will choose the one without the alarm.