Rebuilding our tech stack for the new facebook.com

Re:Rebuilding our tech stack for the new facebook.com by the_other on Friday May 08, 2020 @02:34PM (#23117940)

Facebook release multiple times a day (or they did), so the browser cache is irreLevant.

[ Parent | on HN ]

Re:Rebuilding our tech stack for the new facebook.com by victorvation on Friday May 08, 2020 @05:28PM (#23119691)

As mentioned in the blogpost, they use code splitting and bundle hashing to actually maximize usage of browser cache.

[ Parent | on HN ]

Re:Rebuilding our tech stack for the new facebook.com by pier25 on Friday May 08, 2020 @04:03PM (#23118845)

If you have code splitting many chunks will remain the same.

[ Parent | on HN ]

Re:Rebuilding our tech stack for the new facebook.com by randall on Friday May 08, 2020 @03:26PM (#23118472)

There's a bunch of ways FB mitigates this.

[ Parent | on HN ]

Re:Rebuilding our tech stack for the new facebook.com by the_other on Friday May 08, 2020 @06:41PM (#23120336)

Thanks siblings, for letting me know about FB’s use of code splitting and how it helps caching.

[ Parent | on HN ]

Re:Rebuilding our tech stack for the new facebook.com by foota on Friday May 08, 2020 @03:06PM (#23118255)

I would bet that js bundling and splitting might prevent that from being true?

[ Parent | on HN ]

Re:Rebuilding our tech stack for the new facebook.com by speedgoose on Friday May 08, 2020 @02:48PM (#23118074)

Perhaps but thankfully not all webapps are like Facebook.

[ Parent | on HN ]