> "This transition has previously been presented as peaceful. However, our study indicates the opposite. In addition to violent death, it is likely that new pathogens from livestock finished off many gatherers," says Anne Birgitte Nielsen, geology researcher and head of the Radiocarbon Dating Laboratory at Lund University.
Mac equivalents to Windows Home and End are Cmd-ArrowUp and Cmd-ArrowDown. Fn-Left and Fn-Right are Mac-flavored Home/End, which don't move the text cursor, but scroll the text container, keeping cursor in its original place (although there's no distinction when viewing documents, e.g. in a web browser).
Fn-Left = scroll to top
Fn-Right = scroll to bottom
Fn-Up = scroll page up
Fn-Down = scroll page down
⌘-Up = cursor to top
⌘-Down = cursor to bottom
⌘-Left = cursor to start of line
⌘-Right = cursor to end of line
You can check Home is binded to scrollToBeginningOfDocument: and End is bonded to scrollToEndOfDocument: in /System/Library/Frameworks/AppKit.framework/Resources/StandardKeyBinding.dict.
You can overwrite it by creating ~/Library/KeyBindings/DefaultKeyBinding.dict.
Well from the (incomplete, as turned out) info I gathered it turned out that it was never standardised to begin with (unlike meta description, for example), so it did not even have to be "deprecated". (Like it ever meant something in the real world…) I am definitely for any obsolete mischief, so it brings me joy hearing there is vernacular continuity!
(As for external search engines,FWIR, in its heyday some search engines briefly regarded it quite respectfully, but eventually due to SEO spam they either started to ignore it, or took it as a negative signal, allegedly. But as pointed out in sibling comment, it still survives in Yandex, what is quite surprising plot twist for me.)
"Many search engines do not consider such keywords, because this feature has historically been used unreliably and even misleadingly as a way to spam search engine results in a way that is not helpful for users."
HTML 4.01 says the following:
"This specification does not define a set of legal meta data properties. The meaning of a property and the set of legal values for that property should be defined in a reference lexicon called a profile. For example, a profile designed to help search engines index documents might define properties such as "author", "copyright", "keywords", etc."
Ha, I stay corrected! Crawling back under rock to re-read WHATWG and historical W3C docs to fill the voids…
Note to self: Apparently, I mentally froze around 2009, so I have some decades to catch on. It seems the breaking point was after 2009 Hixie's WONFIX for adding keywords [0], at a time when both `keywords` and `description` were both swept aside into "MetaExtensions" [1]. The turning point I clearly missed came in 2010 [2] and got resolved through [3].
(from the article)
reply