@MarathonTheGame@falloutplays What about people who have already been banned for cheating in Destiny 2? Are they also prevented from playing Marathon? Seems like they should be.
@troyhunt@Ari_Hunt_@discord@Zendesk As part of the developer / application validation process, you have to submit an ID, so that is one reason why Discord would have them.
@DestinyTheGame Are the new portal armor sets adding to the existing sets or replacing them? For example, will Techsec armor still be dropping or will Smoke Jumper replace it?
@A_dmg04 @KrisssBart I would like to hear why prime engrams even exist at all. Given the massive power grind going from 200-550 in the first place, why do we even need a band of even harder grind at the end? Why not just let us grind all the way in the same why through the full power range?
@DestinyTheGame@destinytrack@GCXEvent@BungieLove@BungieStore As someone with a LOT of enhancement cores, it sure would be great if the stack size was increased. Was hoping to see something about that today while they were being discussed in today's article.
@aarnott@James_M_South I just wish I didn't need to ship a .NET Framework version of an MSBuild task to support Visual Studio, especially since it doesn't have any dependency isolation like it does via AssemblyLoadContext on .NET
@SimonCropp Don't reference the package if you don't have to (for multitargeting or to get features from a newer version than what comes in the box). That way you don't need to worry about updating it when there are security vulnerabilities in it!
@SimonCropp I suspect the people that worked on trimming weren't considering the idea that "I've added code to my assembly that I'm not using" as a valid reason to trim when you could just not put it in there in the first place.
@SimonCropp For your Polyfill library specifically, since it's a source package, if you're concerned about not including things that aren't used, you could add ifdefs that conditionally enable parts as needed vs just compiling it all in.
@SimonCropp Also, trimming is only supported for recent TFMs anyway, not for the TFMs you'd most likely want to use polyfills for. I doubt they'd do the work to enable it for .NET Framework, for example.
@SimonCropp Sure, but how big of an assembly are talking about here? It's hard to imagine that it's big enough to care about. Saving 10-100s of MBs? Sure. Saving a few KB? eh.