Is this not the job of the operating system or its supporting parts, to deal with audio from various sources? It should not be necessary to inspect the state of the OS your game is running on, to know what kind of audio you can playback. In fact, that could even be considered spying on things you shouldn't. Maybe the OS or its sound system does not abstract that from you and I am wrong about the state of OS in reality, but this seems to me like a pretty big oversight, if true. If I extrapolate from your use-case, then that would mean any application performing any playback of sound, needs to inspect whether something else is running on the system. That seems like a pretty big overreach.
As an example, lets say I change frequency in Audacity and press the play button. Does Audacity now go and inspect, whether anything else on my system is making any sound?
> Is this not the job of the operating system or its supporting parts, to deal with audio from various sources
I think that's the point? In practice the OS (or its supporting parts) resample audio all the time. It's "under the hood" but the only way to actually avoid it would be to limit all audio files and playback systems to a single rate.
That's the curse of the expert. You see many of the shortcomings, that someone less experienced might not even think about, when they go to social media and blurt out that AI is now able to fully replace them.
Oh but we can absolutely let all that food go to waste! In many places unbelievable amounts of food go to waste.
Actually, most software either is garbage or goes to waste at some point too. Maybe that's too negative. Maybe one could call it rot or becoming obsolete or obscure.
I would be very skeptical about Meta on top of running any reactor. Move fast and break things doesn't work out well in that area of business. Why don't they invest money into more renewables instead, to power their data centers? That seems a safer bet and choice.
I don't think I have ever had a system upgrade break my system on any Debian derived or Fedora I used. Also upgrades are not forced upon you like they are in Windows, with its dark patterns nudging you to upgrade.
I am also using GNU/Linux on laptops just fine, and the only issue is with battery life.
I think hardware-wise one needs to do some reading before buying, to check what is supported and what is not well supported. Other than that, I don't have issues. But then again I am also a strict on or off guy, who does not use things like hibernation or standby or whatever at all, so maybe I am dodging many bullets there.
> It's really surprising that this part is not more common.
I think it is because of low Emacs adoption and other editors not having enough support.
The problem with polyglot notebook workflow is probably, that you can only use it well for small data, or at least not big data, because who wants to have a million lines of output suddenly appear in the buffer, only to then read them as input for the next language ... That would be a tremendous amount of computational overhead. And if we didn't have that, we would need a way to pass a proper value from one language to the other.
What I also like is, that you can define code blocks that are used as formulas for spreadsheets (tables) inside the document. That's quite powerful too.
> (Even more niche is the noweb syntax for proper "literate programming". Which is mostly discussed about how awful it is to use in practice?)
I don't find it very awful to use. I have used that for working through computer programming books and it was fabulous.
Well, but I am not aware of anyone having come up with a good syntax to do babel things in Markdown. Markdown and Org Mode also set out to serve different purposes. For a quick and dirty text Markdown might suffice, but the babel stuff and spreadsheet stuff enable a lot of use cases that Markdown simply doesn't cater to. We already have the implementation of all these nice things in Emacs. If we were to replicate them for some markdown dialect, they would probably be done half-right, before someone actually manages to get literate programming right for various languages, including what code to translate to, how to wrap or not wrap the code that is inside blocks, sessions, output formats, etc. We might as well use what we have with Emacs. There is probably a way to call Emacs' functionality from outside of Emacs, to treat it as a library.
But not all is well with Org Mode syntax either. Many git hosters have only a very rudimentary implementation of a parser and writing a parser for it is not actually that easy. Its dynamic nature requires at least a 2 step approach of parsing and then later checking all kinds of definitions at the top of a file and further processing the document according to that. It's power comes at that cost. That's probably why we have so many Markdowns, but only one Org Mode (OK maybe a few, counting Vim and VSCodium plugins, that achieve a feature subset).
I will say though, that org mode syntax is much better suited for writing technical documentation than markdown. The only issue is, that not so many people know it or want to learn it, and I don't know a way to change that. Perhaps that effort to have the org mode syntax separately defined (https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Over...) by the same author will help creating more support for the format in various tools.
I agree you would need to specify the markdown to allow more implementations. https://github.com/jgm/djot Would make a good DSL inside languages, combine that with compile-time execution so that blocks can auto-recalculate and you have a more available mechanism than emacs/org in other languages.
Question about English for natives: "[...] have lagged behind [..]" would be the grammatically correct version of the heading, I think. Or is "to lag" without "behind" actually a correct use? Is it merely headline-speak, news-speak, to make headlines shorter and convey more information in fewer words?
In my western US dialect, it is abnormal to use it as a subject-verb-object (SVO) construct. I have to guess at intent.
For me, there are three idiomatic forms:
1. Using "lag behind" gives a target/reference as a prepositional relationship, not as an object of the verb "to lag".
2. Using "caused to lag" allows one to specify a causal agent, but again not as an object of the verb "to lag".
3. Using "lag" alone is a subject-verb construct, leaving an implicit target/reference from context expectations. A coach or supervisor might scold someone for lagging.
As a bit of a tangent, I actually wonder if the etymology of "to lag" is more Germanic than some people assume. The verb lagern has many uses for placing, storing, and leaving behind. It's where our English concept of a "lager" beer comes from too, referencing the way the beer is fermented in (cold) storage. If this linguistic connection remained fresh, we might think of an SVO construct of lagging as the opposite of the intent in this article. The leader would lag the follower by leaving them behind!
Lag as a verb does imply following behind, but it can also be a noun, such as in "a time lag".
Adding behind after lag as a verb is more of a "because it sounds good", perhaps as a subconscious way to emphasize the verb, but it isn't a grammatical requirement at all.
Leaving it off is almost certainly more to keep the headline short than anything else.
Both versions are grammatically correct. "Lagged behind" is common for everyday speech, while using "lagged" as a direct verb is a standard, formal way to describe data gaps in business or news. So yes, the headline uses just "lagged" to save space.
I'm not a native, but lived in the US for a quarter century. I think you're correct that that "lagged behind" is the correct version, but if you replaced "lagged" with "trailed" it would also be correct without the "behind". Language is very fluid and always evolving, so using "lagged" as one would previously have used "trailed" may soon be considered correct usage.
Note also that these aren't really questions of grammar (syntax) but meaning (semantics). Does "lagged" mean the same thing as "trailed" in this kind of construction? It didn't some decades ago, but maybe it does today. Or will tomorrow.
"Lagged" alone is valid, but it is slightly less clear. Because, while it would be atypical, "X lagged Y" could be read to mean that X caused Y to lag. "X lagged behind Y" removes that ambiguity.
As an example, lets say I change frequency in Audacity and press the play button. Does Audacity now go and inspect, whether anything else on my system is making any sound?
reply