bonchicbongenre
Joined 6 years ago
Joined 6 years ago
https://github.com/codebicycle/videospeed
It has served me well for years and works on YT ads as well as other sites with similar players
Re rewtriting (3) though: does not the following suffice? "She must have been being watched".
I can imagine an argument that "She would have had to have" is not equivalent to "She must have" on grounds that the "have had" might suggest additionally that the past-ongoing-watching no longer occurs. I don't really think this flies, though, since the natural reading of "been being watched" already suggests to me that the watching was relegated to the past ("been" being interpreted as only connoting the past, not the "inclusive-or"-type interpretation "previously and perhaps presently"; much as "or" itself is - to my chagrin! - generally interpreted exclusively in standard parlance).
I couldn't think of how to simplify the "been being" though; that is a tough nut.
(To be clear, I'm not saying that I find this morally correct — I'm not sure how I feel about that aspect, honestly, except icky at the surface level. I more means that it seems retrospectively to me that, well, of course that's how it would go, given the incentive structure)
I primarily want to say how much I like the parent comment's writing. It is very evocative — "the tea sat tangibly in my stomach", eg, is the sort of description I'd expect in a well-written novel. Kudos nimbius.
Separately, I fully agree w/ the above point about a 2:100 ratio being well too much. The tea shop from which I buy generally recommends ~2g loose for a 175ml cup, but I still find this to be too strong at anything except a minimal brewing time. I tend to use about 1g/cup, ie a bit over 0.5% by weight.
For me personally, the above is exactly correct. Logic is wonderful for me in large part because it's so far removed from tactile reality, though so ingrained in everything.
PDEs/analysis are way too applied for my taste; they as such don't give me the same escape into a world of pure thought (although of course they do provide this moreso than applied ML, or -- god forbid, for me -- web development would). Logic is seductive to me this way.
[0]: https://www.zsa.io/moonlander/ [1]: https://www.zsa.io/oryx/
I came away ranking dagster first, prefect second, everything else not close. IMO dagster wins fundamentally for data engineers bc it picks the right core abstraction (software defined assets) and builds everything else around that. Prefect for me is best for general non-data-specfic orchestration as a nearly transparent layer around existing scripts.
Ofc to each their own based on their usecase.