John Carmack pushes out unlocked OS for defunct Oculus Go headset

Post by asddubs » Fri, Oct 22, 2021, 5:10 PM UTC

tinco wrote: post #42

spicybright wrote: post #22

Earlier quoted context omitted.

Browsers evolve and break older pages. JS that requires requests as you interact with it will need an implementation of the server it uses (the subset and data of it's endpoints) How do you preserve that?

Browsers don't usually break older pages. The only time this happens when you rely on unstandardized features. At least, I have not noticed any page breaking in the past 15 years except for the ones I built using unstandardized API's.

Post by sorry_outta_gas » Fri, Oct 22, 2021, 5:11 PM UTC

rchaud wrote: post #5

nicolaslem wrote: post #3

> allowing for a randomly discovered shrink wrapped headset twenty years from now to be able to update to the final software version, long after over-the-air update servers have been shut down. This resonates so much with me. Each time I setup a new device that requires an Internet connection, I think about how we can enjoy booting 30 years old retro computers and how the next generation will not be able to do the sa…

The same is true of some of the best work being done on the web, such as the NYTimes interactive infographics. Because they are so JS-heavy, and reliant on CI/CD pipelines for deployment, on custom CMSes, there is no way to archive them in the way that static pages containing just text and images can be archived on the Wayback Machine. Heck, even Flash projects from 15 years ago still run fine when compiled on Ruffle…

Post by brundolf » Fri, Oct 22, 2021, 5:12 PM UTC

kbenson wrote: post #25

brundolf wrote: post #18

Earlier quoted context omitted.

Huh? JS can be cached and preserved just like anything else. Even the (presumably JSON or CSV) data could be cached, though I don't know if the Wayback Machine follows API endpoints by default

If it's dynamically updating based on a database of information that's not shipped to the app in it's entirety, you either have to hope you've somehow seen and preserved all the date from exploring the app, or accept that some data may be lost. > presumably JSON or CSV That's presuming a lot. Even if it's accurate for most/all NYTimes infographics today, it doesn't mean it's accurate tomorrow, and it isn't accurate t…

Post by tenebrisalietum » Fri, Oct 22, 2021, 5:13 PM UTC

spicybright wrote: post #22

brundolf wrote: post #18

Earlier quoted context omitted.

Huh? JS can be cached and preserved just like anything else. Even the (presumably JSON or CSV) data could be cached, though I don't know if the Wayback Machine follows API endpoints by default

Browsers evolve and break older pages. JS that requires requests as you interact with it will need an implementation of the server it uses (the subset and data of it's endpoints) How do you preserve that?

Post by cma » Fri, Oct 22, 2021, 5:17 PM UTC

ethbr0 wrote: post #17

eatonphil wrote: post #14

Earlier quoted context omitted.

Consulting CTO just isn't an arrangement I hear about very often. I'm surprised part-time (if that's what it is) CTO-ing works out long-term for a tech company.

Maybe it means "full time, but I reserve the right to not be CTO at a time of my choosing."