As I already said, it's very simple with JSON Patch:
[
{ *op": "replace", "path": "/Name™, "value": "otherName"}
]
Good practice in API design is to permissively accept either undefined or null to represent optionality with same semantics (except when using JSON Merge Patch, but JSON Patch linked above should be preferred anyway).
The semantics of the API contract is distinct from its implementation details (lazy loading).
Treating null and undefined as distinct is never a requirement for general-purpose API design. That is, there is always an alternative design that doesn't rely on that misfeature.
As for patches, while it might be true that JSON Merge Patch assigns different semantics to null and undefined values, JSON Merge Patch is a worse version of JSON Patch, which doesn't have that problem, because like I originally described, the semantics are explicit in the data structure itself. This is a transformation that you can always apply.
Except I never said sticky keys shouldn't exist. And no, I'm also wasn't saying that literally every disabled person ought to go out and buy a programmable keyboard. So many assumptions in this thread.
Wow, what a disproportionate and oddly vicious response to a very innocuous suggestion.
Nowhere in my comment did I suggest that sticky keys simply shouldn't exist. I was specifically responding to the OP talking about Ctrl-C/V and suggesting that a programmable keyboard would be a better solution for that, since you can turn 7 keystrokes into 1, since I expect that reducing the number of keystrokes one has to type is probably pretty valuable for someone in this situation. There are a lot of standard keybinds in an OS that could be handled this way. Obviously you can't do this for every keybinds in existence. But again, the OP was talking about standard OS keybinds. Admittedly, I forgot sticky keys are a toggle, so it's not as many keystrokes after the first time, but still, there are common key sequences that would be more challenging to hit, like Ctrl-Alt-Delete.
If someone is trying to use a public computer, by all means, use sticky keys. Again, I never said it shouldn't exist or people should never use it. I was pretty obviously talking about the normal case: using a workstation/laptop at work/home. It's kind of implied when referring to an external keyboard, since you don't usually bring those places. Don't really know why you're talking about public computers.
The rest of your weirdly personal attacks are all against a strawman you've constructed, so I don't really need to address them.
And you believe a completely obvious lie? Like it doesn't even make sense.
I mean, you're scapegoating developers right now. Developers don't determine priorities. That's a product/business direction problem.
Also, UX doesn't get to say what is hard to do or not (that's the job of a developer, you really don't have any way of knowing without familiarity with the implementation details), so that's certainly at least part of your problem right there.
Umm, you can do that on any device. It's called Google Meet, Zoom, Discord, or any other countless othe video chatting applications out there.
Apple software is pretty overrated no matter if it's iOS or macOS. I use a MacBook for work and I use exactly zero Apple apps because they just aren't very good.
Code can be viewed in more than just an editor. It might be in a terminal, rendered in a browser, etc. Sometimes you might even have to view it in an environment you don't control. I am very disinterested in configuring each and every tool to have sensible tabstops, if such a tool can even be configured.
You're the maintainer and presumably you control the discord server. You can decide to move things to a more available platform by removing Discord as an option.
Good luck doing anything remotely complicated/useful in git with an IDE. You get a small fraction of what git can do with a tool that allows absolutely 0 scripting and automation.
This is really terrible advice.