520 karma · joined July 7, 2018
It's an argument over the doctrine of fair use, which has four parts:
1. What's the purpose of the use? Is it for educational purposes, or commercial purposes? (These aren't mutually exclusive, which is a confounder)
2. What's claimed to be copyrighted/creative in the original work? Is the creativity in question merely the phrasing of facts, or are there aspects of the original author's own creativity (for music, this one is probably irrelevant; it's obviously a largely creative endeavor, though I guess there probably exist certain hypothetical pieces of music for which it's harder to say)
3. How much of the work has been used? This is tricky; he probably teaches how to play entire songs, but the guitar part of any given song is a small piece of the overall work (and he probably uses very little, if any, of the copyrighted recording)
4. What's the impact on the value of the original work? In this case it's clear that there is essentially no negative impact – if anything, if you're learning to play a song, you're more likely to purchase or otherwise consume the original recording. This is also usually the most important factor in deciding fair use (from what I understand; I am not a legal professional, I just remember this from a paper I wrote in college for some course or other).
(edit: formatting)
This was such a passtime for me that 20 years later I remember the randomly-generated names of some individual soldiers who came through for me and turned a battle around when there seemed to be no hope.
Siegfried Krause, I applaud your sniper abilities to this day.
Every functor (in the standard library) is an endofunctor, but is also a functor to a specific flavor of full subcategory in Hask. It might be useful to support other flavors of subcategory, and I think there's some ongoing work on this in the SubHask module.
Oh, give a little space to me
away from me.
Please try not to sneeze in my eyes, corona.
Sanitizer isn't free
uh woe is me
couldn't get an N-95, corona.
Kids are home from school
and they're bugging me
stores are out of food, that's no good
there's none left for me
so I say:
"Why, why, why, why why" Ow!(I know nothing about it, just spitballing)
Currently it takes a shallow copy of the state output by each cell, meaning every value is going to be a primitive value or a reference. If it's a reference to mutable state, you're kind of on your own with respect to keeping reproducibility. I felt like this was a good compromise between strictly enforced reproducibility and practicality; if it turns out to be confusing we could consider deep copying the state, or having an option to do that (I could imagine it being pretty bad for efficiency in a lot of ML use cases, though).
We've had some better options contributed in the past couple of weeks, but as long as we're going to change it I didn't want to rush that. So we stuck with my questionable typographic treatment for the blog post.
(Edit: autocorrect typo)