I think there will be many opinions on this. Here is mine.
As the default mind setting, I always find backward compatibility and graceful protection. As a rule, I believe that a site should be able to fulfill its main goal: to deliver content (content is for sale).
However .. what if the aka content target provides some kind of functionality, such as an online calculator or a drawing application. Then the user already needs to expect things like javascript to be included. In these cases, I will gladly make the design / layout of things easier using javascript. Think of a site like jsfiddle: who would be interested if this site didn’t display it correctly because javascript was disabled .. No one.
Regarding SEO: I think there are a lot of things. If you sell apples and you own the apples.com domain, you are pretty much set up anyway. Again, content is being sold, so most engines try to index it.
In addition, on this (terrible) day and Internet age, the most popular search engines will filter and rank the search results for the user. Therefore, if you want to optimize your site for a search engine. then for whom are you trying to optimize the personal bubble (search results)?!? .
I more believe that it has been semantically encoded, supported, and has a fairly stable foreseeable future (instead of having to restore the same thing over and over again, every 6 months or so). Simply put: make the kernel / base "simple" enough to "always" display in a useful way, and then add spice using javascript and css-edge technology to give this text.
Gitaarlab
source share