Yes, it's a strange argument in my opinion. He also argues that almost all open source projects live on Github, but those don't pay money for dev products either.
Assuming you mean that ironically. Unfortunately, the README doesn't reveal where the name comes from, but it is truly absurdly misleading, as if it came from a random generator...
Oh wow, I really didn't make that connection. Thanks!
Still not sure it really is a good name for a lib: someone who doesn't already know it will probably not think about jQuery when they see this name in a dependency list...
Also with the advances in local AI processing it seems realistic that the image analysis gets much more powerful and suddenly you have something like Microsoft's Recall but in your monitor/TV (and used _solely_ for profiling and not your benefit).
This doesn't reflect well on Asahi Linux. It feels similar to the WordPress drama of the past few weeks: individual people have a personal vendetta and are holding an open-source project hostage. I'm certain not all WordPress or Linux maintainers are behind their respective dramas but are inevitably pulled into it.
It left me speechless after commenting on a (small) text on my hoodie – this made it feel super personal all of a sudden (which is amazing for an AI of course)
That's the second time I read this comment and I still don't believe it: it's listed as a "dedicated root server" (usually billed by the month) with no mention of typical cloud offers.
But that kid in your example isn't doing _nothing_, they are playing video games. That is entirely different from consciously pausing and doing nothing.
This court ruling was (also) about "CDL" (controlled digital lending), i.e. lending ONE digital copy of a book for each physical book in a library's possession – and only while the physical copy was not lent.
This is as far away from "giving away infinite copies to anyone" as it could be.
While I agree with your point, there is some nuance because transfers can be nearly instantaneous. Physical books have to be transported to and from the library. CDL is as if we all lived in the same library and could shelve/swap books with anyone at any moment and only have to wait when there is a queue.
That's what the internet does: it makes things that took days or weeks before (nearly-)instantaneous.
If I have 100$, I can lend them to someone (via paypal or whatever), and when I get them back, I can immediately give them out again. I don't have to wait for them to physically go to my place (or a bank) and return cash.
If your whole defense hinges on "borrowing books has to have an inherent delay of X hours/days/weeks before they can be given out again", that's a very weak point in today's day and age. It's like saying "sending mails is bad because it is nearly instantaneous, and you don't have to wait for the postman to deliver your letter".
I'd argue it probably doesn't affect it. I have certainly not seen any stats to support that argument. I most certainly would not wait to compete with the rest of the world to read a book once my spot in the queue finally arrived. I would simply buy it.
On second thought, I don't think the demographic of "people buying (your) books" and "people borrowing (your) books from a library" have that much overlap.
People who borrow books from a library are usually people who either don't want to (or can't) buy all the books they like to read. In that case they are unlikely to buy the book anyway even if they can't find it in the library... OTOH people who love your books or your writings, or people who saw a review and think "I'd like to read that book" will buy it anyway and not read a scanned version of it on their small phone screen.
I mean I understand why authors would love it if libraries didn't exist and everyone had to buy the book to read it, I would probably be in the same boat if I were an author. But the calculation "1 borrowed book = 1 lost sale" is flawed the same way that software companies' "1 warez download = 1 lost sale" is flawed
Sadly Microsoft has a history of enabling "features" after updates, even though the user has disabled it before. Of course only to "improve the experience".
