Had my first encounter with \v doing an import of a legacy database just a few weeks ago. The data was passed on to us in a batch of XML-files. For some reason our XML parsing library would just ignore the rest of the file when it came to the \v character. Took me some time to find the culprit.
Edit: The \v character had somehow made it into one of the descriptions for one of the user profiles.
There's a 30/70 split for most online music services (both streaming and purchase). The major labels negotiate to get a better deal, but for most artists there's a distribution fee of 30%. I don't have the details for the Apple Music agreement, but I know both Spotify and Tidal takes a 30 % cut of the revenue. I expect Apple Music to follow the same revenue split as iTunes.
Also: Spotify's freemium model pays out about 1/20 compared to Tidal premium-only model. If Apple Music is a consumer success, it (and other premium-only services) will be a much more attractive option for artists than Spotify.
I fiddled with an SPA for personal finance, and I used the js file API in combination with a <input type="file" /> to load a local file and Papa Parse [1] to parse the CSV. You could do all this stuff client side, then push the non-sensitive information (like spending category, date and amount) to your API.
There's a lot you can do frontend and keep your backend simple/stupid. If you host the data in Google Drive or Dropbox, you wouldn't be responsible at all for the potentially sensitive information.
Not sure what you meant with _most folks_, but I'm under the impression that most people on mac, who use the Terminal on a daily basis, use homebrew as their package manager.
To me, this was annoying. I was interested in "trying" the product, i.e. seeing what kind of questions I would have to answer. You should just highlight empty, required fields when the user hits submit.