Hello, neat project. I am also from Edmonton area. I wonder if we have talked previously, in the the late 90s I ran a local BBS system with my colleague.
I am not saying this is a solution, but the reason you see this is because a number of companies, such as TikTok and LinkedIn, have been caught scraping the clipboard.
That said, for web applications, you are required to do things like use HTTPS for the modern clipboard API, which provides the user some guarantees. Not much works without HTTPS anymore though.
Do you work in the agricultural industry? Farm equipment is expensive, farmers will maintain the equipment as long as possible, which is a long time. Manufactures such as John Deere have tried to make it not possible for farmers to do self repair.
Maybe, but I wouldn't go back to Python 2 without async. It has also improved over time in Python. I have also had success using async in Python. I do understand what the article talks about however. Understanding the difference between blocking and non-blocking code is also a concept relevant to Python. In Node it's one of the concepts you are first introduced to, because Node is single threaded by default. I also understand in Go and other languages there are different options.
Hey Yoric, I do not want to underplay what it is like to work with async, but I think there has been a lot of improvements to make it easier, especially in JavaScript/ECMAScript. It is nice not to have to work directly with promises in the same way that was required previously. The language has matured a lot since I started using in Netscape Navigator (I see you formerly worked at Mozilla). I think coding can be complicated in general, although it shouldn't have to be. I think having a mental model for async from the start can be helpful, and understanding the difference between blocking and non blocking code. A lot of people learned writing synchronous code first, so I think it can be hard to develop the mental model and intuit it.
I can tell you guys work with languages like Go, so this isn't true for yourselves, but I usually find it is developers that only ever work with synchronous code who find async complicated. Which isn't surprising, if you don't understand something it can seem complicated. My views is almost that people should learn how to write async code by default now. Regardless of the language. Writing modern applications basically requires it, although not all the time obviously.