• 0 Posts
  • 93 Comments
Joined 1 year ago
cake
Cake day: August 2nd, 2023

help-circle










  • Been playing it since release and I have to say I quite like it. The mtx is less intrusive than Dragon Age Origins’ DLC (no mention in game at all versus “There’s a person bleeding out on the road, if you want to help him please go to the store page”).

    So far, the game is a buttery smooth 60 fps at 4k max graphics + FSR3 w/o ray tracing except for inside the capital city (running 7800x3d with a 7900xtx). The only graphics complaint I have is the FSR implementation is pretty bad, with small amounts of ghosting under certain lighting conditions. There’s also a noticeable amount of input lag compared to the first game: not game breaking, but if you do a side-by-side comparison it’s pretty obvious.

    Sure the game has its issues, but right now this looks like something that I enjoy. Games don’t need to be masterworks to be fun (my favorite games are some old niche JRPGs that have been absolutely demolished by reviewers at the time), and right now I think it’s money well spent.








  • StarDreamer@lemmy.blahaj.zonetoAsklemmy@lemmy.mlDeleted
    link
    fedilink
    English
    arrow-up
    15
    ·
    edit-2
    6 months ago

    Nothing but effort. Nobody wants to constantly baby a project just because someone else may change their code at a moment’s notice. Why would you want to comb through someone else’s html + obfuscated JavaScript to figure out how to grab some dynamically shown data when there was a well documented publicly available API?

    Also NewPipe breaks all the time. APIs are generally stable, and can last years if not decades without changing at all. Meanwhile NewPipe parsing breaks every few weeks to months, requiring programmer intervention. Just check the project issue tracker and you’ll see it’s constantly being fixed to match YouTube changes.


  • StarDreamer@lemmy.blahaj.zonetoAsklemmy@lemmy.mlDeleted
    link
    fedilink
    English
    arrow-up
    22
    ·
    edit-2
    6 months ago

    An API is an official interface to connect to a service, usually designed to make it easier for one application to interact with another. This is usually kept stable and provides only the information needed to serve the request of the application requesting it.

    A scraper is an application that scrapes data from a human readable source (i.e. website) to obtain data from another application. Since website designs can update frequently, these scrapers can break at any time and need to be updated alongside the original application.

    Reddit clients interact with an API to serve requests, but Newpipe scrapes the YouTube webpage itself. So if YouTube changes their UI tomorrow Newpipe could very easily break. No one wants to design their app around a fragile base while building a bunch of stuff on top of it. It’s just way too much work for very little effort.

    It’s like I can enter my house through the door or the chimney. I would always take the door since it’s designed for human entry. I could technically use the chimney if there’s no door. But if someone lights up the fireplace I’d be toast.