Maybe we could tone down the JavaScript (2016)
1–10 of 237 posts
Re: Maybe we could tone down the JavaScript (2016)
#2And this is when I realized this article was written a long time ago. Now if you attempt read a text post on twitter you get nothing at all unless you execute javascript first. The entire screenshot would be red in 2021.
Re: Maybe we could tone down the JavaScript (2016)
#3Re: Maybe we could tone down the JavaScript (2016)
#4I used Huel's site earlier and it even had a splash overlay saying what it was loading, it was one reticulating splines away from being The Sims
Edit: ah it was posted in 2016, I don't think anyone (but do wish) cares about limiting their JS usage anymore
Re: Maybe we could tone down the JavaScript (2016)
#5>here is a screenshot of a tweet, with all of the parts that do not work without JavaScript highlighted in red And this is when I realized this article was written a long time ago. Now if you attempt read a text post on twitter you get nothing at all unless you execute javascript first. The entire screenshot would be red in 2021.
Re: Maybe we could tone down the JavaScript (2016)
#6Quoted post unavailable.
Re: Maybe we could tone down the JavaScript (2016)
#7Product Designer: "No system controls; we want our users to have the Full Brand Experience, therefore, custom controls." Also Product Designer: "Why don't our custom controls work as well as system controls?"
Re: Maybe we could tone down the JavaScript (2016)
#8Re: Maybe we could tone down the JavaScript (2016)
#9I honestly thought this attitude had died out with everything being Vue and React and all that I used Huel's site earlier and it even had a splash overlay saying what it was loading, it was one reticulating splines away from being The Sims Edit: ah it was posted in 2016, I don't think anyone (but do wish) cares about limiting their JS usage anymore
Re: Maybe we could tone down the JavaScript (2016)
#10Quoted post unavailable.