looks like it exists under playByPlay using different terms.
seriously considering just porting the old perl code to parse the json and update the tuples for 2019-2020, since i had to do some to get the games for each day.
will probably do it when i enter the 2021 data, then i'll retrospectively update the old data with this new approach (2019-2020). maybe just update existing entries with this data.
pulling the xml-based stuff anyways (2021, already entering 2020 >_>).
annoying af. i don't see the benefits. maybe json is tighter than xml. less files sure (probably storage savings too), but the tuples don't seem particularly more informative than before.
my hope is that parsing json in perl will be much faster than xml. it very well may be.
looks like it exists under playByPlay using different terms.
seriously considering just porting the old perl code to parse the json and update the tuples for 2019-2020, since i had to do some to get the games for each day.
will probably do it when i enter the 2021 data, then i'll retrospectively update the old data with this new approach (2019-2020). maybe just update existing entries with this data.
pulling the xml-based stuff anyways (2021, already entering 2020 >_>).
annoying af. i don't see the benefits. maybe json is tighter than xml. less files sure (probably storage savings too), but the tuples don't seem particularly more informative than before.
my hope is that parsing json in perl will be much faster than xml. it very well may be.