Readit NewsHere's my theory: they aren't concerned with the movies and TV shows shown in the video (which are presumably obtained legally as Jeff mentioned), but rather the brief use of what looks like [plugin.video.youtube] (https://github.com/anxdpanic/plugin.video.youtube) at about 12:10 in the video.
The plugin is an alternate frontend to YouTube, and as such, allows bypassing ads. He never mentions the plugin explicitly in the video, but I'm pretty sure that's what it is; he mentions YouTube and is clearly watching one of his own YT videos in Kodi. Just today, I noticed YouTube getting more aggressive in its anti-ad-blocking measures. They got really strict a year or two ago, backed off a bit, and seem to have ramped up again. My guess is that someone in management needs to show better numbers and is looking for ways to punish anyone even hinting at accessing YouTube without the obligatory dose of advertising.
Why should a platform allow sharing ways of violating its terms of service? Sure, any tech savvy person will be able to figure it out, but business are businesses.
Should supermarkets allow you to ressel coupons in their premises for a profit? Because he's 1. monetizing the video, 2. being sponsored by a third party in the video and 3. showing ways of circumventing the platform TOS.
He could remove that frame where he shows the yt plugin, but he's using this to farm engagement.
On top of that, there is no easy way to create a template. For example, I want an invoice template which I can reuse with different data. Theoretically, I can create a typ file for the template, and define the invoice as a function which I then call from a string with, say, json data. It seems great as web service, but not as a library I can use from, say, Rust.
And the type system is a bit confusing. I can define basic types like numbers or string, but when it comes to structs, they don't seem to have support for that.
I find it easier to create a handlebars template, and feed the HTML to headless chrome printing service, which will output a PDF for me. It's not scalable for high volume, but good enough for my needs (takes about 2-3 seconds to generate PDF).
Templates are just functions [0].
I think much of the frustration comes from typesetting being a harder problem than it seems at first. In general a typesetting system tries to abstract away how layout is recomputed depending on content.
Supporting contextual content -- cases where the content depend on other content, e.g. numbered lists, numbered figures, references, etc -- involves iterative rendering. This is evidentidly a complexity sinkhole and having a turing complete script language will bite you back when dealing with it. I recommend reding their documentation about it [1] where they explain how they propose solving this problem.
[0]: https://typst.app/docs/tutorial/making-a-template/
[1]: https://typst.app/docs/reference/context/#compiler-iteration...
It is not an experiment in how bad front end design can be pushed to be... Although that would be a fun blog post
The things that look like buttons (and are spans in the html code, not even anchors!) trigger non-local transitions (the left panel thing) when hovered... and they close the opened panel when clicked, so if I move my mouse to click on it the end result is a panel that flashes.
I need to keep ignoring the usual button affordance of being clicked and force myself to think they are tiggered on hover.
If this isn't bad UX I don't kown what it is.
Dead Comment
Dead Comment
There's an awful lot of money and power associated with operating systems and programming languages (obviously), and the resulting "realpolitik" of situations like these seem to get swallowed up in these discussions.
It makes sense for technical people to think that the technical debate is what essentially matters, but it usually never actually is.
I've found the way Linux has approached Rust in the last couple of years to be a tad confusing. Always cutting a hard line, suddenly Torvalds' opinion is quite wishy washy. Oh, we'll try it, who knows, what's the worst that can happen, type thing? What induced this change, one wonders.
[0] Well-written blog posts on the subject are very welcome, please share if you know one!
By not answering this questions and saying he doesn't want to have anything to do with the arguments, Linus simply decided that he doesn't want to solve the problem that only him can solve. The result is clear: R4L will fail if Linus decides that any maintainer can stop the "cancer" to spread and block Rust changes.
R4L implies that Rust will be present in the kernel and will need to be maintained. If Linus is ok with maintainers that have a deep/fundamental problem maintaining/coordinating the maintenance of Rust code, R4L will never happen.
I wish Jellyfin could catch-up with the compatibility level AirFlow has to offer.