First the unrelated concepts argument. It's generally hard to know if a concept is related to your research without understanding it or knowing about it. Then there's the dunning kruger effect where we overestimate our own abilities. It's likely that there was a tangential link and the author failed to see it. Ironically her failure to see the relation possibly led to a poor impression.
The argument of not having family members to talk about research is absurd because you always have some colleagues talking shop.
The language argument fails because every year many immigrant students with English as a second language take the same exams and do well.
However, applications that just grabbed X11 framebuffer won't work. They have to use respective APIs with user control ("portals") for that. Some do (Chrome, Firefox), some don't (MS Teams).
If you're forced to use an application that only supports the X API, you can kludge it to work by VNCing to yourself with x11vnc and then screencasting the x11vnc window.
I use it every day. I can share screen in Google Meet, Zoom, Slack Huddle, and many others. It doesn't work in Signal, though, because Signal is using an outdated version of Electron.
Since each company sort of sticks with 1 tool for every employee, could be kind of a deal breaker if they pick a tool that can't screen share on Wayland.
A friend of mine couldn't share his screen on meet or teams and I had to change it from Wayland to X11 to make it work. His was a Ubuntu 22.04 distro (GNOME) 4 month old install. Wonder why that happened.
No! The Wayland protocol provides no mechanisms for screen sharing and it is not intended that it ever will. Screen sharing has to be done by external protocols that are either compositor specific or using a somewhat standardized dbus protocol that is completely separate from Wayland.
It seems to work for a lot of people, but I still get constant crashes using xdg-desktop-portal-wlr, despite trying multiple GPUs, extensive testing etc. I will probably dive into the code when I get some time.
That's a very one-dimensional analysis of a complex problem. You can't ignore the obvious physical differences and roles in reproduction. These factors affect how you relate to a larger society and to what extent you depend on it.
The problem is not of one isolated mouse but a society of mice and how your physical size, vulnerability (men don't have period pains or pregnancies) affect how you relate to society and thus your personality.
Read books by Gary Provost on writing. Writing Tools by Roy Peter Clark. Draft number 4 by McPhee. They contain a variety of ideas. Writing Tools is great if you want to identify and drill techniques. Provost's books cover everything and are written well.
There's was a great article on HN on how C is more than a programming language. It is a protocol for most of computing. I would suggest you to look into the actual influence of C on computing and protocols instead of just looking at software.
There's a great George Carlin bit on how changing the names to less severe sounding terms can actually be harmful. He gives the example of shell-shock being changed to PTSD which sounds more benign and doesn't capture how horrible the condition is. Also the race baiting in black box and red team is so unintentionally hilarious.
It is remarkable how much long-term advantage people like us have gotten by trying to be consistently not stupid, instead of trying to be very intelligent. -- Charlie Munger
What if the fixation points are not on every word but create a narrower space by being a couple inches in from either side of each line to use the classic speedreading trick of using peripheral vision? Has it been tried?
