For poetry, I think English has the advantage of Germanic and Latin roots. Such seems to offer some flexibility in tone.
The relative lack of conjugation and declension seems to hurt by constraining word order and reducing opportunities for sound similarity. Of course having rhymes be common also tends to reduce their impact.
Inflection (I think) is part of the cause of extra syllables, so has multiple impacts.
The length itself does seem to add something to the flow/lyricism, but I wonder if there is also a stronger sense of sound whereas English may be more a little more chaotic (not just having multiple roots but borrowing words more often).
One can look at abbreviations as being like pronouns with the antecedent sometimes being stored in a cultural context or being placed at first reference in a potentially longish text.
Like pronouns, the 'antecedent' may be unclear causing difficulty for the reader. However, pronouns and abbreviations can help communication and be convenient to the reader.
Acronyms have the advantage of being pronounceable and so treated more naturally as words.
Like jargon, when the context is a historical first reference rather than first reference within a text of moderate length, the meaning can be obscure to those not familiar with the context. (One of my college essays was faulted for using "inertia" in the physics sense, specifically that a body in motion tends to remain in motion which is contrary to the common use of inert/inactive/unmoving. It was a natural use to me, particularly for the image used, but it was wrong for the audience.)
Assuming familiarity is a common human flaw (xkcd: https://xkcd.com/2501 ). As has been mentioned this can also be used for in-group/expertise signalling. Yet density in communication does have value. (Math would certainly be tedious if every proof started from axioms.)
I agree that being unclear is bad, especially for mere convenience. On the other hand being verbose can be tedious and even insulting (by implying a lack of familiarity with matters obvious to the reader).
I thought the main problem with initialisms was not ambiguity but unfamiliarity. Yes, there are many AMAs and sometimes the local context is insufficient to remove ambiguity (in which cases the initialism might be expanded for clarity or context clues added). However, my experience has been more often that intialisms had no meaning to me (beyond immediate context) -- a vocabulary issue -- than my being uncertain which meaning was intended (ambiguity).
Specialized terms like the "Social Contract" can use capitalization to indicate a jargon use and the plain sense of the words does give some clues to the intent, but such can also risk a false sense of comprehension. The writer would actually be depending on the reader's familiarity with the jargon use.
(I wish Page Table Cache had been adopted instead of Translation Lookaside Buffer even though tee el bee seems to flow more more easily from the tongue. Besides being more complete -- a TLB also caches permissions and other page table entry information and could cache page directory entries -- "cache" has a modern jargon sense closer to the typical design and "lookaside" typically does not apply to L2 TLBs.)
Communication is difficult and taking the time to choose the very best writing is rare. Even with care, migration of word meaning or connotation can make a choice worse than alternatives (and the migration can be across cultures and not just across time).
From what I recall of the video, two people independently worked out the chemistry for cheaper aluminum. (I believe the video also mentions the source of the aluminum/alumininium name difference.)
I would not phrase the means of approaching best length as "edit out everything that's not 100% necessary" but as something more like "make every scene count/pull more than its weight". The former, to my mind, tends to associate with small goals and a pure utilitarianism that falls short of excellence. I doubt you meant anything like that.
I certainly agree that "Great scenes will server two or more purposes". A scene can advance the plot, display who the characters are and who they may become, foreshadow or rationalize future plot elements (or present red herrings), introduce worldbuilding depth, manage the emotional state of the audience (comic relief is a simple example), etc. I would not be surprised if a great scene can also so elevate other scenes that its relative greatness may be less obvious because it makes the whole greater than the sum of its parts in isolation.
I very rarely watch movies (even less often in a theater) and I do not have a drama or fiction writing background, but even a "little learning" about the theory hints that bulk is easier to achieve than extensive excellence.
When ARM moved to 64-bit the ISA was much more substantially reworked than for AMD's x86-64 transition (which mainly added modes and repurposed INCrement and DECrement to provide the REX prefix which provides a 64-bit size specification and one additional bit for register name specifiers; obviously the page table format also changed). I am not particularly familiar with AArch64, but I got the impression that the main retained cruft from 32-bit ARM was condition codes and the tradeoffs of providing condition codes would lead some not to consider such cruft. The use of four bits for almost every instruction to support predication was eliminated — which was a major cruft point for 32-bit ARM — and the legacy of shift and perform ALU operation orientation of the original ARM (which had timing slack from the slowness of instruction fetch) was de-emphasized.
AArch64 is accumulating cruft, perhaps particularly with respect to SIMD, but it is less crufty than x86-64.
ISA modularity/diversity can be useful for embedded systems, where the software is really firmware. If one is going to have to provide a diversity of compilation targets via either a common distribution format that is compiled to the local machine code or an app store that receives a software format that can be compiled to diverse, the best distribution format (to users or the app store) is likely to be significantly different than an encoding best for direct execution.
Some optional features can be hidden by system libraries (particularly when the main use of the feature is suitable for a separate accelerator). E.g., an instruction that performs a round of AES encryption could be hidden behind an encryption library. However, some uses of an AES instruction involve a very short "message" for which library overhead would be excessive or for which good enough software alternatives would be faster than actual AES.
Indexed memory accesses and conditional select/move, for example, are not really suitable to system libraries (or trapping to software even with a very fast trap handler).
ISA scaling is not necessarily a good design feature. An ISA optimized for the market targeted by ARM M Profile is unlikely to be optimal for future 16-wide decode high performance processors. E.g., if a context only has 16 registers, using 5-bit register specifiers is suboptimal even though it allows software to be "upward compatible" with a 32-register design.
While increasing dealer revenue is a plausible goal, it also seems plausible that reducing production cost could cause awkward maintenance. It is even plausible that only the bill of materials would be considered, though the feedback loop for increasing assembly cost is much tighter and less noisy that the loop of end-user dissatisfaction with maintenance issues.
Even within an organization, creating externalities from one department's perspective seems common enough.
Even if a decision maker is aware of the possibility of externalities and cares about a broader constituency (temporal or "spatial"), evaluating actual costs is an expense as is justifying that investigation expense and any mitigation/avoidance expenses to others in the decision web.
The PhD Movie introed with Richard Feinman's statement "I don't know anything, but I do know everything is interesting, if you go into it deeply enough."
Feinman was a curious character.
I suspect that with even a modest breadth of knowlegde a deep investigation of anything brings associations with existing knowledge (interest), unexpected connections and exceptions.
I think one should use ex/em units when setting a maximum width for readability. People with poorer vision will tend to prefer a physically larger font size. Pixels can also vary in size for different displays. (I am not a web developer but I do have poor eyesight and delay getting new glasses.)
By only testing one static branch, it is possible that the performance of the Intel Emerald Rapids predictor is not representative of a more realistic workload. If path information is used to index the predictor in addition to global (taken/not taken) branch history without xoring with the global history (or fulling mingling these different data) or if the branch address is similarly not fully scrambled with the global history, using only one branch might result in predictor storage being unused (never indexed). Either mechanism might be useful for reducing tag overhead while maintaining fewer aliases. Another possibility is that the associativity of the tables does not allow tags for the same static branch to differ.
(Tags could be made to differ by, e.g., XORing a limited amount of global history with the hash of the address.)
It is also possible that the AMD Zen 5 and Apple M4 have similar unused predictor capacity and simply have much larger predictors.
I did not think even TAGE predictors used 5k branch history, so there may be some compression of the data (which is only pseudorandom).
It might be interesting to unroll the loop (with sufficient spacing between branches to ensure different indexing) to see if such measurably effected the results.
Of course, since "write to buffer" is just a store and increment and the compiler should be able to guarantee no buffer overflow (buffer size allocated for worst case) and that the memory store has no side effects, the branch could be predicated by selecting either new value to be stored or the old value and always storing. This would be a little extra work and might have store queue issues (if not all store queue entries can have the same address but different version numbers), so it might not be a safe optimization.
The Triptych Proposals [1] cover a lot of common use cases for submitting information to a server and updating part of a page. Something like that should have been possible to implement early in web history (I perceive some similarity to frames).
Modern CSS (and some newer HTML features) also reduces the need for scripting.
I very much doubt that "Enabling scripting was a necessary step for interactive websites." (emphasis added). It may well have been the most convenient and fastest way to get the functionality to the most users. With Javascript each website could provide functionality without waiting for such to be implemented by all browsers.
However distribution of power also leads to more complex trust relationships (even if one is confident that sandboxing is effective). Independent implementation also leads to more complexity overall.
That video did not really include self-medicating (except as screen time can be self-medicating for boredom and tiredness); I tend to self-medicate anxiety by simple logic games (picmi, sudoku, kmines — all but the last also avoid failure) which wastes a lot of time. (Drinking water seems to be a somewhat less harmful form of self-medication; it has similar sensory benefits to eating — not as attractive as sweet, salty, fatty foods but it seems somewhat similar — and distraction but overdrinking water seems more difficult.)
I disliked _Always Coming Home_, substantially because it felt misandrous though the less optimistic setting probably also played a role (a post-industrial Earth with a rape victim as the "protagonist" and not a heroic victim who transforms evil and suffering into good). It did seem to be exceptional in literary quality, a strong extension of the divided story mechanism in _The Dispossessed_ (and _The Left Hand of Darkness_? — I do not remember how that novel was laid out). I did not listen to the audio produced for the books, so I did not receive the full experience, but the literary quality of the novel was excellent (in my opinion). (I especially liked the simple squirrel drawing, an odd bit of trivia to remember.)
(I thought the acknowledgement of life when killing a mosquito was an interesting cultural aspect.)
I did kind of wish that a monastic-like community (or university?) had been presented as seeking more benefit from the City of Mind. Unlike the tribe that asked how to make airplanes (which failed in their military objective), the monks/scholars would train to ask good questions, seeking to restore the land and encourage communication and cooperation among humans. Having even a small bunch of humans interested in such larger issues would have been more optimistic (and perhaps realistic as the existence of an actual Oracle might encourage some people to be scholars, making connections and asking questions). Of course, a ten volume novel would have been even less popular, and LeGuin clearly was motivated to write a more gritty novel.
When returning to Washington University in St. Louis, I was walking a few miles with some luggage. Someone offered to carry one piece with me to the dorm. It was only after reaching the dorm that I realized she was barefoot!
The relative lack of conjugation and declension seems to hurt by constraining word order and reducing opportunities for sound similarity. Of course having rhymes be common also tends to reduce their impact.
Inflection (I think) is part of the cause of extra syllables, so has multiple impacts.
The length itself does seem to add something to the flow/lyricism, but I wonder if there is also a stronger sense of sound whereas English may be more a little more chaotic (not just having multiple roots but borrowing words more often).