Internet Archive: Difference between revisions
→Website no longer usable without JavaScript (2023): more readable |
→Website no longer usable without JavaScript (2023): + minimalist browsers |
||
| (One intermediate revision by the same user not shown) | |||
| Line 75: | Line 75: | ||
Since 2023 however, large parts of the Archive.org website (including the home page, collection pages, and the search engine) can no longer be browsed at all without JavaScript, because the legacy HTML-based user interface was replaced with a Google Lit web app. As of April 2026, only individual item pages remain viewable without JavaScript.<ref>Before change: [https://ghostarchive.org/archive/3vxC8 2023-06-28]. After change: [https://ghostarchive.org/archive/sdLIp 2023-09-28]</ref><!-- Editor note: I also know this from personal experience, but given that archive.org/details was excluded from the Wayback Machine and Archive Today converts everything to static HTML, there is not much of a historical record available for these changes. User account pages (archive.org/details/@...) were made JS-only in March 2024, but I'll have to find a source for this. --> | Since 2023 however, large parts of the Archive.org website (including the home page, collection pages, and the search engine) can no longer be browsed at all without JavaScript, because the legacy HTML-based user interface was replaced with a Google Lit web app. As of April 2026, only individual item pages remain viewable without JavaScript.<ref>Before change: [https://ghostarchive.org/archive/3vxC8 2023-06-28]. After change: [https://ghostarchive.org/archive/sdLIp 2023-09-28]</ref><!-- Editor note: I also know this from personal experience, but given that archive.org/details was excluded from the Wayback Machine and Archive Today converts everything to static HTML, there is not much of a historical record available for these changes. User account pages (archive.org/details/@...) were made JS-only in March 2024, but I'll have to find a source for this. --> | ||
This made it impossible to | This made it impossible to browse the site on legacy systems that do not support modern web browsers, as well as minimalist web browser alternatives to the Google-Mozilla duopoly, and slowed down loading on modern web browsers because lots of code has to be executed before any content can appear on screen, putting the content at the end of the rendering path.<ref>{{cite web |title=Critical rendering path – Mozilla Developer Network |url=https://developer.mozilla.org/en-US/docs/Web/Performance/Guides/Critical_rendering_path |access-date=2026-04-18 }}</ref> | ||
==References== | ==References== | ||