Unfortunately even Google started requiring JS, which was a huge attack against small browsers and the open web.

rodarima 3 hours ago | parent | next [-]

The Google index is still accessible from many other "proxy search engines" that still work without JS, one example is Startpage.

See the nice list from Seirdy for more details on search engines: https://seirdy.one/posts/2021/03/10/search-engines-with-own-...

▲

nicoburns 4 hours ago | parent | prev | next [-]

Yep, https://html.duckduckgo.com works well in such browser though :)

	▲	ksymph an hour ago \| parent [-]
		Also check out http://frogfind.com/, it automatically converts results into basic HTML.

▲

childintime 3 hours ago | parent | prev | next [-]

But does it require ES6? Javascript was quite minimal in the early days. It doesn't need a JIT, in fact I'd prefer it not to be.

▲

nicoburns 2 hours ago | parent [-]

The difficult bit isn't the core JavaScript support. There are a dozen engines packaged as libraries that can use for that. The difficult bit is supporting all of the hundreds of DOM APIs.

	▲	userbinator 21 minutes ago \| parent [-]
		Also the "undefined behaviours" used for fingerprinting and denying access to non-mainstream UAs even if they have JS support. If I remember correctly, YouTube was doing something like that.

▲

shevy-java 4 hours ago | parent | prev [-]

Google at this point kind of controls the www. Now, strictly speaking that statement is not true, but it now feels as if Google sits in so many areas that are important for the www; chrome is just the most obvious one.