"Fuck you, we're not paying": inside Unity’s Runtime Fee fiasco - Mobilegamer.biz
mobilegamer.biz
A major partner told John Riccitiello personally that it will not pay the Runtime Fee – and in the strongest possible terms.

A major partner told John Riccitiello personally that it will not pay the Runtime Fee – and in the strongest possible terms.

  • CommanderCloon@lemmy.mlEnglish
    11·
    11 months ago

    Isn’t that super annoying now that JS frameworks are so widespread? (React / angular etc.)

    • sugar_in_your_tea@sh.itjust.worksEnglish
      1·
      11 months ago

      A lot of sites are starting to use next.js (not sure if there’s an angular equivalent), which is essentially server-side React, and the frontend JS picks up where the server left off.

      If you want your articles crawled by search engines, you need some kind of default text representation. So you should be good most of the time blocking JavaScript if you mostly want the text content and are okay with some styling jank, and I don’t expect that to change anytime soon. But you’ll lose interactive features, so things like bank logins likely won’t work.

    • m_r_butts@kbin.social
      21·
      11 months ago

      Yes, it is. It’s a price I’m willing to pay. The web is a malicious hellscape now, and I’d rather just not see something than give in to 38 trackers, 14 ad engines, a megacorp’s federated login box, one or more captchas because they hate my VPN, etc etc just to see something that’s really not going to add any value to my life anyway.

      I do what I can with privacy addons, but is it really worth the time to figure out the bare minimum of what I need enabled so I can look at the Celebrity Baby Plastic Surgery Disasters website? I’d rather just click the back button and move on with my life.