Hold on, (even though kicking JSON while it's down is funny) how do you make sure that the reply you've got is to the call you issued with this thing? Surely not pinky promise?
JSON's everything is "indefinite length". Also its implementations are wildly inconsistent [1] (is anyone going to read the code to figure out which is the blessed systemd parser?). Also it doesn't have integers. A lot of things with JSON will deteriorate into stringifying anyway, for example dates.
Comparing this to net neutrality just poisons the well when discussing NN. Internet service providers being able to arbitrarily adjust pricing based on data source stifles competition. Is there competition in the power supply industry where a client can pick their source? Well, aside from having their own generation. In this case transfer is the service and if one day huge demand cluster disappears the capacity for it is left to rust.
I don't think your point disagrees with mine. Charging based on demand is fine, requiring take-or-pay contracts when your request requires expensive grid upgrades is fine. Charging more because it's a datacenter as opposed to heavy industry, not fine. That's the part that mirrors NN.
But to directly answer your question, yes there is competition. In most states, Ohio being one of them, you can choose who provides your power generation. And since companies are shopping states for where to build data centers AEP has a lot of competition for delivery.
Excel chews up CSVs that it opens. I know this because an accountant checked each file our code produced using Excel before trying to import it into another program. We proofread our code before we realizing the problem was somewhere else. Shoulder-surfed the process, found the giant bug with a green X on it.
It's no better at exporting to CSV. I wrote a CSV parser a few years ago that had one set of logic for Excel CSVs and a completely different set for everything else.
Excel doesn't change CSV files when it imports them. If the imported file was being changed then the user was saving back to the same file they imported from.
The fact is the person was double-clicking a file in a list to view its contents and Excel was trampling it. Nobody in their right mind will waste time to open Excel first, use import feature, re-navigate to the file they were already looking at, and go through the import dialog just to see what's inside.
Trampling it to me implies that Excel was somehow modifying the contents of the file. Which it doesn't do by double clicking on the file and just viewing it. Do you mean that the data shown in Excel wasn't what was expected because of the auto data conversion?
Believe me, I was blown away just the same. And it's not like the accountant clicked a save button of a on-close dialog, no. Opening a CSV file was enough.
Introducing checkboxes somewhere in the bowels of settings adds more ways for things to go wrong.
What is the default? Do the defaults differ across versions? How do you keep it consistent across computers and installations? What if you actually need the function ad hoc?
This reminds me of CSV export. I haven't used Windows for a decade but I remember that if you wanted to change how decimal numbers were exported you had to change the locale and reboot the computer. To change a setting in Excel. That is insane. Sprinkling checkbox patches isn't too far from this.
