3
Nmeri17
174d

The Facebook web app (on mobile) is so incredibly garbage in a foul, vile way; no client would have accepted it if I was the one who delivered it. Its Twitter counterpart is fairly functional despite all the js fidelity. Some things still behave as you are accustomed to. Facebook tried to hijack ALL native browser capability and ended up releasing an abominable artifact that should be a disgraceful, stark, warning as to how horrid and insufferable the extremism of javaScript can get

You can't open links in new tabs. Sometimes you can "like", other times app that loaded sits still and unresponsive like a corpse. The most annoying part has to be absence of urls, so you can't reference anything. You can't even share posts ffs

Funny enough, this used to have an edge over the restrictive mobile app eg you could reuse profile pictures. You could share specific photos out of a set, etc. Now, it's painfully broken. It doesn't even compensate for it with passable ui. That too, looks amateurish. The only thing you can do on it now is scroll

Comments
  • 0
    @retoor
    Ladybird browser is not a well-known or widely used browser, so it is unclear what specific JavaScript engine it uses. However, most modern browsers use well-established JavaScript engines such as V8 (used in Chrome), SpiderMonkey (used in Firefox), JavaScriptCore (used in Safari), and Chakra (used in Microsoft Edge). Without more information, it is difficult to pinpoint the specific JavaScript engine used in Ladybird browser.
  • 1
    10 years ago the FB mobile app had 18,000 classes. Classes. Not lines of code. Classes.

    AI will replace those devs...
Add Comment