Relatedly, now random apps can't record the whole screen. This is a good thing, now they get explicit user permission and go through xdg. I don't know how anyone could be opposed to this - it's objectively more empowering for you, the user.
But if you wanna argue Chrome should be able to read all your keyboard inputs whenever it wants be my guest. I can't fathom why people want that type of setup.
I won't expect stdlib.h to provide me a magical get_cursor_pos() function in any way.
GUI toolkits? (This includes the Win32 GUI.) Maybe.
It's not a universal thing though -- for example, you may receive mouse position _only_ when the cursor is in your window.
I did a quick google before I asked you that question, and it looks like wayland is one of the few exceptions to completely exposing current cursor position. Most "stdlibs" do expose it.
Are you referring to the native GUI toolkit of a platform (e.g. Winforms, Cocoa) or something else?
Just google it. You are incorrect and you're not pumped about it, I get it. The horse is fully beat to death. If you want to discuss further, my responses will probably just be lmgtfy links.
> In computer programming, a standard library is the library made available across implementations of a programming language.
You should show me that, among the mainstream programming languages, their standard library will provide get_cursor_pos().
I do agree that probably no-one was confused, though.
Not that it makes a huge difference in the discussion, but if you want to be smug about it then at least make sure you're right first.
It's an exception, not the rule. Even Python, well known for its batteries-included std, do not provide this magical get_cursor_pos() function that you insist is found in stdlibs.