In order to load a custom OS you first must be able to unlock the bootloader ofthe device. The list of OEMs allowing that is sadly getting smaller and smaller and vendors are becoming actively hostile towards custom firmware development.
see: https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame
There's a common saying in Germany that applies.
Basically translates to: "Those Brits are crazy", but the literal translation would be: "The Brits are spinning" (yarn).
You can get a 2020 M1 / 2022 M2 Macbook air for ~400€, that will mop the floor with all new hardware in that price range released even today (completely fanless/noiseless btw.). It also has decent linux support via asahi and Apple will still probably provide 5+ years of macOS updates anyway.
It's arguably worse, because Samsung has full control over software, hardware, and firmware of their devices.
Even if MS would like to fix this mess, they can't.
I've made an update edit: Some hardware vendors fucked up when to send the key-up-sequence apparently so now every keyboard can behave differently. I don't know if this makes the situation better or worse.
nah, they just ran out of options, because they already used the press all modifier keys (HYPER) hack for the physical office key(I'd have to check how it handles key-up events, but I'd bet it does it correctly / distinguishable --> I think I'm on to something https://www.makeuseof.com/remap-caps-lock-to-hyper-key-and-double-shortcuts/ )
Defining a new keycode would've gotten them in trouble with their hardware partners, because that would be hard and break backwards compatibility, so they took the easy / stupid way out to implement this awesome new button, just to appease the marketing / product department. (conjecture)
This is just a result of the banality of evil / incompetence.
nope, the hardware / keyboard controller sends a complete key sequence instead of a distinguishable key-up and key-down event.
The OS can interpret that sequence as it sees fit, but you loose the physical key-up signal when you release the key with your finger.
afaik: the complete sequence is triggered when when the copilot key is pressed.
You'd intercept the F23-up immediately --> no way to detect when the physical key is released.
In order to load a custom OS you first must be able to unlock the bootloader ofthe device. The list of OEMs allowing that is sadly getting smaller and smaller and vendors are becoming actively hostile towards custom firmware development.
see: https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame
icanhaz tools:
Browserleaks
Ferengi Rules of Acquisition
won't get better
https://discuss.tchncs.de/post/55725243
There's a common saying in Germany that applies.
Basically translates to: "Those Brits are crazy", but the literal translation would be: "The Brits are spinning" (yarn).
Obelix knows best.
Adblock is digital self defense against malware for your pc, as well as your mind.
https://xcancel.com/SwiftOnSecurity/status/1569083806224715776
this isn't properly remapped and depending on implementation of the key-up events by the keyboard vendor, requires an ugly time delay hack.
qed. https://github.com/Rast1234/copilot_key_on_my_keyboard?tab=readme-ov-file#the-bad
You can get a 2020 M1 / 2022 M2 Macbook air for ~400€, that will mop the floor with all new hardware in that price range released even today (completely fanless/noiseless btw.). It also has decent linux support via asahi and Apple will still probably provide 5+ years of macOS updates anyway.
The simple trick to owning nice hardware is to never give vendors your money directly, let others burden the depreciation.
It's arguably worse, because Samsung has full control over software, hardware, and firmware of their devices.
Even if MS would like to fix this mess, they can't.
I've made an update edit: Some hardware vendors fucked up when to send the key-up-sequence apparently so now every keyboard can behave differently. I don't know if this makes the situation better or worse.
Marketing said it has to be a dedicated key, engineers were stuck between a rock and a hard place.
Who would've guessed radishes were so rad^ical^ vegetables.
nah, they just ran out of options, because they already used the press all modifier keys (HYPER) hack for the physical office key(I'd have to check how it handles key-up events, but I'd bet it does it correctly / distinguishable --> I think I'm on to something https://www.makeuseof.com/remap-caps-lock-to-hyper-key-and-double-shortcuts/ )
Defining a new keycode would've gotten them in trouble with their hardware partners, because that would be hard and break backwards compatibility, so they took the easy / stupid way out to implement this awesome new button, just to appease the marketing / product department. (conjecture)
This is just a result of the banality of evil / incompetence.
You might wanna start getting used to pressing command with your thumb, instead of ctrl with your pinkie then:
Here's my rant about inconsistent keyboard shortcuts on non-macOS systems:
https://mastodon.social/@attero/115771231064736124
nope, the hardware / keyboard controller sends a complete key sequence instead of a distinguishable key-up and key-down event. The OS can interpret that sequence as it sees fit, but you loose the physical key-up signal when you release the key with your finger.
afaik: the complete sequence is triggered when when the copilot key is pressed. You'd intercept the F23-up immediately --> no way to detect when the physical key is released.
It is/was required for vendors to use the AI PC / Copilot+ label and Microsoft "invented" the key-sequence.
src: https://www.theverge.com/2024/3/26/24112500/microsoft-ai-pc-intel-windows-copilot-key-requirements