Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)AL
Posts
11
Comments
586
Joined
2 yr. ago

  • absolutely, hence why I put forward the idea of an API that would allow games to stop people from joining multiplayer matches or flag their highscores if sketchy hardware is involved! For Single Player games, who cares!

    But deep down we all know that this first and formost is a money grabbing scheme from micro$oft

  • Honestly I think that is great. It allows them to easily add stuff down the road. If they add a new gamemode for example that needs new voicelines - easy! Otherwise getting all the VAs in makes things way harder.

    That being said, for a singleplayer game that doesn't evolve being changed around all the time I would be a lot more critical.

  • No bro, Xbox isn't evil anymore. Phil Spencer is a good guy and Gamepass is the "best deal in gaming"./s

    On serious note there is some legit reason to do something like this. Things like the Cronos Max or Rapid fire controllers are a legit problem in multiplayer games because they are hardware cheats essentially.

    But they could have created an API that allows games to check if a unoffical device is detected if that is the reason.

  • This isn't any great C++ low level optimization but I have an Angular Project which contains a list that shows the live logs of various backend services and other things comming in through websockets (I keep up to 500K lines in memory). Essentially a extremly long scrollable list. First I obviously used lazy list which only renders the elements in view that are visibile instead of one that renders everything all the time. Secondly I removed as many html elements from each list element as possible, mostly divs that were just used to apply a css class.

    When it comes to JS code I got a huge performance improvement by replacing a bunch of pure array.map, array.filter, array.toSorted, ... method calls with a big ol for loop. These pure functions caused an insane memory churn because they create a shallow copy each time and doing that for an array with 500K entries caused the garbage collector to work overtime. Also the whole filtering and searching in the first draft was done every time new elements were added to the list via websocket for the whole entire list. I changed that so it only does it for new elements.

    Overall this allowed me to increase the number of logs kept in memory from about 20K (because then performance would start to dip) to now 500K.

  • No, Android itsself lacks the amibition to add anything meaningful. Desktop Mode, Customizable Quick Settings Toggle Area, actually useful battery stats, a more customizable battery saving mode would all be things I'd like to see but clearly aren't a priority.

    Also I really don't like Material U. Classic Material looked way better!