WOOOO 2020

Migrated project to .NET 5
- The .NET Framework is dead. Long live .NET.
- I think it bundles the runtime but honestly I'm not sure. I'm sure you'll be better informed soon enough.
Pruned a bit of dead code
I added an automated build but NuGet doesn't want to play nice with C++/CLR projects with unmanaged dependencies.
- This means that the automated build doesn't work
- - I'll fix it one day I guess
Fixed uninitialized memory usage in ww2ogg which could, in ludicrously rare occasions, crash the .NET VM. The .NET Framework VM, anyway. You probably meant to total it, didn't you?
- I used to like .NET :(
- - tbh .NET 5 looks p rad
Removed Newtonsoft.Json, replaced with System.Text.Json or whatever they're calling it
- The "Generating PKG Database" phase has sped up quite dramatically as a result.
- This doesn't really have a pronounced effect on the "strings" or "transcript" databases.
- Can anyone explain this thing to me? I really doubt Bungo's engineering team is spending time coming up with bizarre text obfuscation algorithms... right? There's gotta be some kind of mathematical explanation for this or something. (Maybe SIMD tomfoolery? Seriously, someone help me understand this. Most of the .pkg format makes sense to me, except for this.)
- - I'm salty my dudes
- - Actually what really gets me are these Parallel.ForEach calls
- - - Did he not realize that this attempts to parallelize processing of over 300 packages? 300 parallel tasks sounds fast, right? RIGHT?!

Provide feedback