"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.

  • smallaubergine
    1•1 year ago

    There’s crazy stuff like that on every website. Run a script blocker like noscript and it’ll open your eyes.

    • Ender of GamesEnglish
      3•1 year ago

      They aren’t talking about the website. They are talking about the article.

      • @[email protected]English
        0•1 year ago

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

        • @[email protected]English
          1•1 year 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.