I like to take a look at /compiler/src/dotty/tools/dotc to whet my appetite from time to time [2].
[1] https://github.com/lampepfl/dotty [2] https://github.com/lampepfl/dotty/tree/master/compiler/src/d...
I like to take a look at /compiler/src/dotty/tools/dotc to whet my appetite from time to time [2].
[1] https://github.com/lampepfl/dotty [2] https://github.com/lampepfl/dotty/tree/master/compiler/src/d...
So e.g. if I go and view Russian dashcam videos they're going to automatically play more of them, even though I've shown no prior interest in that topic.
Having two systems for recommendations would introduce a lot of UI complexity, so I can see why they didn't go for that, and why the recommendations are consequently tuned for people who are actively watching videos on some topic right now.
For example, Russian dash cams to Russia at night to the Russian sleep experiment creepypasta, to horror games to video games in general, if that is what the user tends to watch.
I know this has graph theory written all over it and the shortest-distance problem has wreaked havoc for centuries, but I think with enough resources Google/YouTube could find a good compromise in this situation.
If I had to use a Lisp-like language, I'd choose Clojure so I can interoperate with the JVM. (I use Scala already, so I could interoperate with that, too.)