News for hackers. Stuff that matters.
Re:Rebuilding our tech stack for the new facebook.com by pier25 on Friday May 08, 2020 @12:41PM (#23116684)
> as little as possible

I just opened FB with the cache disabled and it downloaded 5.85MB (19.76MB uncompressed).

Most of it happens after the page has rendered, which is great, but that's a lot of stuff. There are 13.74MB of uncompressed JavaScript.

Re:Rebuilding our tech stack for the new facebook.com by throwaway43423 on Friday May 08, 2020 @01:26PM (#23117205)
For reference, vscode ships as 13.3MB of uncompressed JS. (Not including builtin extensions, but that wouldn't add much)
Re:Rebuilding our tech stack for the new facebook.com by panta on Friday May 08, 2020 @01:01PM (#23116920)
Stealing data about the users as accurately as possible requires more code than one would think.
Re:Rebuilding our tech stack for the new facebook.com by dylkil on Friday May 08, 2020 @01:46PM (#23117439)
>Stealing data about the users

its not stealing when the users agreed to it

Re:Rebuilding our tech stack for the new facebook.com by infogulch on Friday May 08, 2020 @01:51PM (#23117506)
Using a website does not imply informed consent.
Re:Rebuilding our tech stack for the new facebook.com by xd1936 on Friday May 08, 2020 @02:25PM (#23117867)
No, but signing up for an account and agreeing to the Terms of Service does. The not-logged-into homepage is 1.3mb. Still not tiny, but definitely not the same as the web app.
Re:Rebuilding our tech stack for the new facebook.com by AlexandrB on Friday May 08, 2020 @03:31PM (#23118521)
No it doesn’t. Informed consent is not the same as shoving a ToS/EULA in front of someone who may not have the legal or technological education to understand it or its consequences.

From the Wikipedia definition[1] of informed consent (in medicine):

> An informed consent can be said to have been given based upon a clear appreciation and understanding of the facts, implications, and consequences of an action. Adequate informed consent is rooted in respecting a person's dignity. To give informed consent, the individual concerned must have adequate reasoning faculties and be in possession of all relevant facts.

What tech companies do is obtain the minimum legally required consent - and sometimes not even that. This may be legal, but it’s far from ethical.

[1] https://en.m.wikipedia.org/wiki/Informed_consent

Re:Rebuilding our tech stack for the new facebook.com by ianmobbs on Friday May 08, 2020 @04:47PM (#23119266)
Fortunately, Facebooks ToS[0] is not full of legalese or jargon, and I'm sure anybody with enough technological education to sign up for Facebook can understand it too.

[0] https://www.facebook.com/terms.php

Re:Rebuilding our tech stack for the new facebook.com by Endlessly on Friday May 08, 2020 @08:45PM (#23121122)
Quick read of it and it is obvious that document likely cost millions for Facebook to produce and with the aid of countless hours of legal professionals who in sum likely have 1000s of years of legal experience.

Claiming the average person is able to understand scope of that document— and the likely 1000s of internal documents related to it, and the 100s of thousand pages of related legal code and case law is a stretch.

Document also does not disclose Facebook is subject to secret court orders, gag orders, etc.

— and that doesn’t even begin to cover the knowledge required to understand the related technology and the impact it might have on the users.

Re:Rebuilding our tech stack for the new facebook.com by LadyCailin on Sunday May 10, 2020 @05:50PM (#23136588)
Huh. Sex offenders aren’t allowed to use FB.
Re:Rebuilding our tech stack for the new facebook.com by schkkd on Friday May 08, 2020 @01:08PM (#23117007)
That's pretty much size of a mobile app. But the thing with web apps is that they are downloaded every time and hence the outcry.
Re:Rebuilding our tech stack for the new facebook.com by speedgoose on Friday May 08, 2020 @01:31PM (#23117276)
They aren't though. You have a cache.
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.
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.
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.
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.
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.
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?
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.
Re:Rebuilding our tech stack for the new facebook.com by mgraczyk on Friday May 08, 2020 @04:06PM (#23118882)
Not so, refresh the page to see how large the second download is (much smaller)
Re:Rebuilding our tech stack for the new facebook.com by bzb3 on Friday May 08, 2020 @01:01PM (#23116928)
With a standard 4G/FTTH connection that's less than one second of download time.
Re:Rebuilding our tech stack for the new facebook.com by edhelas on Friday May 08, 2020 @01:07PM (#23116992)
Everyone have 4G and Fiber, and a Core i7 and 16Gb of RAM :) Seriously…
Re:Rebuilding our tech stack for the new facebook.com by bzb3 on Friday May 08, 2020 @01:09PM (#23117010)
That's not what I've said, and I somewhat agree with the original point, but this trend of wanting to cater to the lowest denominator rubs me the wrong way.

Some guys think the web should be usable with a 50€ smartphone on GPRS, and I say no, because there's a middle ground.

Re:Rebuilding our tech stack for the new facebook.com by nromiun on Friday May 08, 2020 @01:15PM (#23117083)
How about just caring for the real world instead of the numbers provided by the internet provider? Those download numbers are for the best case scenario. And unlike broadband 4G is not reliable at all.
Re:Rebuilding our tech stack for the new facebook.com by pier25 on Friday May 08, 2020 @01:17PM (#23117102)
> because there's a middle ground

So where's your middle ground?

Re:Rebuilding our tech stack for the new facebook.com by pathseeker on Friday May 08, 2020 @01:49PM (#23117473)
>Some guys think the web should be usable with a 50€ smartphone

You went to the other extreme though. Most people in high-income countries don't even have FTTH.

Re:Rebuilding our tech stack for the new facebook.com by saagarjha on Friday May 08, 2020 @01:48PM (#23117463)
Have you read anything about Facebook’s emerging markets? They want to cater to those people themselves!
Re:Rebuilding our tech stack for the new facebook.com by ukyrgf on Friday May 08, 2020 @04:52PM (#23119326)
The web should be usable on a 28.8k modem from the mid 90s. Why wouldn't it be?
Re:Rebuilding our tech stack for the new facebook.com by buboard on Friday May 08, 2020 @01:33PM (#23117296)
There is absolutely no excuse. The app is not doing protein folding, its merely showing text!

Surprise, many many ppl use facebook in crap laptops, fb is popular with everyone.

Re:Rebuilding our tech stack for the new facebook.com by bzb3 on Friday May 08, 2020 @01:42PM (#23117400)
No, it's not merely showing text. Facebook does a thousand things more than show text. You could argue those features don't belong in Facebook, but you can't argue that features are supposed not to take up any space, because that's unrealistic.
Re:Rebuilding our tech stack for the new facebook.com by sopromo on Friday May 08, 2020 @04:13PM (#23118932)
If I have to download 5mb of js for every page I visit on my phone I would be out of data in less than 15 days.