This may be true from a pronunciation standpoint, but he's mostly writing from a text processing standpoint. From a text processing standpoint, Russian and English are pretty easy to deal with.
On the other hand, it's a bit funny to point those out as easy to deal with, because they are bicameral alphabets, with notions of upper and lower case, case mappings, title casing rules, and the like. That's a complex system, that if you didn't grow up with it and already have had to deal with and come to terms with it, you would probably include it in a rant like this.
So, this is actually more about "your writing system, and legacy encodings of it, suck."
While we do still have to support legacy encodings, increasingly we should just be using a universal encoding that doesn't have all of these problems he mentions. UTF-8 is such an encoding; it is ASCII compatible, contains no nulls, has the usual ASCII control characters encoded the same, no shift sequences, if you jump to an arbitrary byte in the middle of a text there is a maximum number of bytes you need to go forward or backwards to find a character boundary and you can do so with no ambiguity, etc.
And a large portion of the writing system suck rant has to do with Chinese (hanzi/kanji/hanja) characters, because there are just so many of them and standardizing them is a fairly difficult process. And it's true; that writing system does suck. It may have some good points, but it's amazing that it's still in use, it would be enormously economically beneficial to move to a simpler, easier to learn writing system.
Of course, if you did that and people no longer learned the older, much more cumbersome and complicated system, they would lose access to a large number of older cultural works which do use it, so it's a pretty tough sell.
Just to note, Korea actually does use a much simpler, more efficient writing system for the bulk of their text, but they do have a few words that they still use Chinese characters for. One of the reforms in North Korea was to abolish the use of Chinese characters entirely, using only the much simpler hangul writing system. His complaint about Korean is more due to how hangul is encoded in Unicode, which could be considered complex or clever depending on how you look at it; in any other sense, though, hangul is a great, very efficient and easy to deal with writing system.
While lots of people mention the connection between cats and toxoplasmosis, it's actually more likely for you to get it from eating undercooked meat than from your cats. It comes out in their feces, and you would need to eat the feces to get infected; so while it can happen if you clean the litter box and don't wash your hands afterwards, it's not all that likely.
It is also carried by chickens and pigs, so if you eat undercooked pork or chicken, that could be a risk factor.
Cats use the litterbox and then lick their paws, as well as the rest of their body. If you pet your cat and then absent-mindedly eat something (like I've done all too often, unfortunately), you may become infected.
Throwaway for obvious reasons, but this would actually explain a lot. Oh god...
Anything that touches the cat's litter or butt might be infected. I.e. you'd have to keep the cat off your furniture, especially eating or food preparation areas -- every time. You'd have to not ever put your face on something that the cat might have snuggled against, or walked on. It's just not feasible.
Well, and Linus would never agree to move to the GPLv3 even if that were an option (assuming that copyright were assigned to him or an organization he had a controlling voice in). In his opinion, the GPLv2 is the perfect license, and he doesn't like the additional restrictions imposed by the GPLv3.
I don't necessarily agree with him, but based on his influence in the kernel community, it would be pretty hard to change the license over his objections.
Looking at the opinions of specific individuals is kind of missing the point. Theo de Raadt and Bill Gates don't much care for GPLv3 either.
Ask it a different way: How many popular GNU/Linux distributions have zero GPLv3 binaries in them? I expect Linus has GPLv3 software on his own machine.
Theo de Raadt and Bill Gates don't much care for GPLv3
either.
Right, and so like Linus and the Linux kernel, that's why they don't ship code under the GPLv3.
I'm sure Linus does have GPLv3 running on his machine. He doesn't mind using the license, as it doesn't constrain him as a user in any way that he objects to. But he doesn't ship his own software under that license.
I wasn't saying anything about the relevance of his opinion, to anything other than the kernel license himself. You had asserted that the kernel hadn't moved to the GPLv3 because of lack of copyright assignment; and I was just pointing out that in addition to that, the lead developer of the kernel personally dislikes the GPLv3, so even if he had the ability to change license, he probably would not have.
Personally, I'm pretty happy with the GPLv3. I wish more developers would release code under it, instead of more liberal licenses, to help defeat things that I find unpleasant like Tivoization and software patents. But not everyone shares my opinion, and Linus's opinion carries a lot more weight than mine as the leader of the kernel project.
While Apple has not publicly said anything about it, it's pretty clear from their actions that they consider touching anything under the GPLv3 verboten.
Every single piece of software that has new releases under the GPLv3 they have stopped updating. A few of the most important ones, like GCC, GDB, and Samba, they've even gone as far as to pour substantial amounts of money and effort into funding replacements (clang, lldb, Apple's smbd). Others that they don't consider very important they've just let languish, like bash, make, and other GNU utilities that they include on their systems.
Sorry, are you asking why Apple and Microsoft do not allow distribution of GPLv3 licensed packages?
Given that they haven't made any public statements about it, it's hard to say with certainty; you can only speculate.
But the major things that the GPLv3 changed, which companies like Apple and Microsoft are likely to object to, are the anti-Tivoization clauses, the patent license clauses, and the "no effective DRM" clauses. If you check the information about what changed in GPLv3 (https://www.gnu.org/licenses/quick-guide-gplv3.html), those were pretty much the only extra restrictions added.
The anti-Tivoization clause says that if you distribute the software along with hardware, you must also distribute (or provide users with a way to change) any keys that are necessary for users to run their own modified version of software on that hardware. Given that both Apple and Microsoft ship locked down phones that don't allow users to modify their software, and are increasingly moving towards locked-down App Store models even on desktop and laptop computers, they may not want to risk every being obliged to follow that requirement.
The patent grant clause is likely the one that worries them the most. That says that if you distribute the software, and your distribution of the software relies on patents that you either hold or license from someone else, you must either pass along the rights in those licenses (if possible), or give up the patent license (that is, if you have licensed a patent from someone but don't have the ability to transfer that license to downstream recipients, than you may only distribute the software if you give up that patent license, putting you and your users on equal footing if the holder of the patent decides to enforce it).
The DRM clause may also bother them, but I doubt that they would avoid using software due to it, since it only applies to software which is itself used as part of a DRM system, saying that it can't be considered an effective technological measure (as the other freedoms provided by the GPL allow users to replace it), and so none of the legally enforced restrictions on removing DRM can apply. Since that only applies to code that is used as part of a DRM system itself, I don't think that would cause them particular problems, as long as they avoid linking any of their DRM systems to GPLed code, but there may be cases in which it would come up.
Anyhow, I can't really say which of these is the reason that they don't allow it, as they have never made any public statements about that. My guess would be the patent clause, followed by the Tivoization clause, followed by the DRM cluase, in order of importance.
You're just describing the changes in the license, and none of those seem particularly objectionable. You seem to agree that the DRM restriction is quite harmless. The anti-tivoization clause might reasonably apply to iOS, but I don't think iOS includes any version of these utilities, and that still wouldn't explain excluding them from OS X. It's not like they couldn't just take them back out later on.
And the patent license seems least objectionable of all. The primary change from GPLv2 seems to be having to include some language accounting for it in the agreement for any patents they license, which they have every incentive to do regardless in order to be covered in case an employee puts an Ubuntu ISO somewhere public, and in the worst case they're still only in the same situation they would be if the patent in question had been owned by some patent troll.
Also, the post I responded to is talking about "Apple and other proprietary software publishers." So Apple is more the exception than the rule in having any trouble at all with the anti-tivoization clause since most software vendors don't make their own hardware.
I still don't see anything that should make it so untouchable.
Have you watched Apple's patent war with Samsung? They rely heavily on patents to attack competitors. If they distributed something under the GPLv3, then there's the chance that Samsung could have looked at that, said "hey, that GPLed package implements something that your patent license covered, that means that we now have a license to that patent."
Or there's all of the patents that the license from other parties, like the H.264 patent portfolio. Those patents they can't relicense; so if any of those apply to any of the GPLv3 software they tried to distribute, they would be in violation of one or both of the licenses.
Also, the post I responded to is talking about "Apple and
other proprietary software publishers."
Well, this thread is about Apple, and the one you were responding to was comparing Apple with Microsoft. The part about "other proprietary software vendors" was in there, but I'm not trying to back that up since that's too broad a category to discuss as a whole. There are several different kind of proprietary software vendors, that sell software in many different ways, and so discussing them as a category is likely not to be useful.
For example, vendors who sell closed-source, proprietary applications could never use any GPLed code, as linking to it would mean they were required to release the code of the whole application under the GPL. So there there's really no different between GPLv2 and v3.
Vendors who sell bundled software hardware combos could ship GPLed software, and embedded Linux is common there. However, some of them like to lock down their hardware, not allowing it to be upgraded or modified by end users. The anti-Tivoization clause specifically forbids that, so they may avoid GPLv3 software in order to avoid the anti-Tivoization clause. One example here is Android, where they even avoid GPLv2, for software that ships on phones, almost everywhere except for the kernel.
There are also some proprietary software vendors who do ship GPLv3 software. For example, Oracle, one of the biggest and most notorious proprietary software vendors, actually does ship Oracle Linux, a distro which contains an awful lot of GPLv3 software. So its clear that not every company has made the same decision; some avoid it like the plague (Microsoft and Apple), some avoid it in certain products but not others (Google avoids it Android, but ships GPLv3 code in Chrome OS), and some are fine with shipping it. You can't really make any blanket statements about all proprietary software companies.
But anyhow, as I said, for cases such as Apple, it's very obvious that they are fine shipping GPLv2 software, but very clear from their actions that they won't ship GPLv3. There are three major additional restrictions in the GPLv3, and we can speculate which one was the tipping point for Apple. My money is on patents, but I think that the anti-Tivoization may play a role too. However, unless they publicly say something, or someone leaks some internal communication about it, we will just be left speculating as to why.
> If they distributed something under the GPLv3, then there's the chance that Samsung could have looked at that, said "hey, that GPLed package implements something that your patent license covered, that means that we now have a license to that patent."
The patent license only applies to derivative works so Samsung couldn't use it for its non-GPLv3 products.
> Or there's all of the patents that the license from other parties, like the H.264 patent portfolio. Those patents they can't relicense; so if any of those apply to any of the GPLv3 software they tried to distribute, they would be in violation of one or both of the licenses.
They could just not distribute that GPLv3 program.
Obviously this runs into the problem that you don't know which patents which programs infringe, but that has nothing to do with the GPL. Some troll could just as easily jump out from under the bridge and demand a hundred billion dollars for a patent on Safari.
Some troll could just as easily jump out from under the
bridge and demand a hundred billion dollars for a patent
on Safari.
Sure, and that kind of stuff does happen. And Apple likely makes decisions based on limiting their liability to that kind of thing. They have publicly stated that they objected to Ogg Theora because they had a patent license for H.264, and didn't think it was worth the risk to ship something like Ogg Theora, which may be covered by unknown patents.
Now, H.264 may be covered by unknown patents as well. But based on the existence of the MPEG-LA and its patent pool, and the fact that they'd already invested in and exposed to any potential H.264 risk, they felt like there would be more risk to them to add Ogg Theora support than just sticking with H.264. Were they right? Who knows. But that is the decision they made.
Now, we are just speculating about why they hate the GPLv3 so much. But they obviously do, and they have both done a lot to use their own patents offensively, as well as being cautious about infringing patents as a defensive stance, so my best guess is that the patent clause is their concern.
But there's no way for me to be sure; there's not much point in continuing to discuss it, because it's Apple that has made this decision, not me. I'm perfectly happy shipping GPLv3 covered software; if you want to know why Apple isn't, you could try asking them, though are unlikely to get an answer.
The GPL is designed to preserve the end-user's freedom. In order to do that, it only grants other distributors the right to copy it if they agree to grant the same rights to others they distribute it to.
Under copyright law with no license at all you would have no right to copy it at all; the GPL grants you additional rights, but only if you do the same in turn.
Complaining that that restricts your freedom is like complaining that it restricts your freedom to go to a country that forbids kidnapping. Sure, in stateless areas with no effective government, you may have the additional freedom to kidnap someone else, denying them their freedom. But on the whole, laws against kidnapping (or false imprisonment, or the like) are their to preserve freedom.
Likewise, the additional freedom that the MIT or BSD licenses grant you is the ability to deny other users the freedom to use and modify your works derived from the code.
Can we please stop having the argument that BSD or MIT give more "true freedom" than the GPL? The only additional freedom they give you is the ability to apply more restrictions to other people.
Now, you may not want to make the deal that the GPL makes, trading your code for a promise that other people who distribute it continue to offer the same freedoms that you offer. You may not really care what restrictions other people place on it, or on their modifications to it, after you've released it. You may even want to have the ability to collaborate with those who use their software licensing to restrict end user freedom. Or you may not want to deal with license compatibility headaches.
But arguing that "true freedom" comes from license like BSD or MIT, and not the GPL, is ridiculous; the GPL is designed to ensure that the software and all modifications to it will always remain free, while liberal licenses simply allow people to redistribute it with more restrictions, making the ecosystem less free, not more.
The GPL, MIT, BSD, and any other license that meets the requirements of the free software definition, Debian free software guidelines, or open source definition, are all "truly free," they just differ in whether they attempt to preserve that freedom transitively or not.
Right. One case in which I've come across this problem in Python is writing unit tests for code using Twisted (and Trial, Twisted's unit test framework) with @inlineCallbacks, and trying to also use this style of resource management for mocks (or, essentially the same, the @patch decorator to set up the mocks).
Then you run into the problem that @patch has cleaned up all of your mocks by the time the yield returns.
Now, I haven't tried to do anything equivalent in Rust; I'm not sure what the idiomatic equivalent would be. But having more explicit control of lifetime, rather than it always depending specifically on that stack frame, seems like it might help here.
There is no way in which you can look at systemd and say that "it's a bug". It may be a system not engineered the way you would prefer, but it absolutely isn't "a bug". It's a large, well engineered piece of software, that solves many pain points of traditional ways of managing services and sessions on Unix-like systems over the years.
What way would you like to customize your system that you cannot using systemd? I'm genuinely curious if you've ever tried using it.
Now, there are many valid reasons why systemd may not be to your taste. No one is forcing you to use it. There are projects in which development is moving to depend on systemd, because it provides a lot of functionality that other systems don't, and the people writing that code don't want to have to reinvent the wheel. Lots of software has dependencies, some of which you may not like, but you shouldn't blame Person A for making a system that you don't want to use, that Person B who writes software you do want to use depends on; and really, blaming Person B isn't particularly helpful either, as they are just trying to get the job done efficiently and don't have the time to maintain many different backends for many different incompatible session management systems.
Note that the above referenced "retroactively aborted" rant was not directed at Kay. It was instead directed at some unnamed developer who had set up kernel log handling in Debian with a "dd bs=1 if=/proc/kmesg of=/var/run/klogd/kmsg", which was copying the kernel log one byte at a time to a FIFO (presumably because something reading the log was better able to deal with a FIFO than whatever strange semantics /proc/kmesg has).
Kay had then made /proc/kmesg semantics somewhat weirder, by not blocking but instead returning 0 when the available buffer wasn't big enough to read into; normally, returning 0 to a read indicates that the file has been closed, while if there simply isn't data available yet the call is supposed to block until it is.
So Linus was asking Kay to fix the issue, but also making an aside about how stupid it is to try to read one byte at a time from the kernel.
Now, there was the other incident you mention, in which Linus did get upset enough at Kay for not responding very well to a big report, but this one was not that; he was merely asking Kay to fix a bug, and cursing out some unnamed other developer for having done something as dumb as byte-at-a-time reads.
Not really defending either side here. I find Linus excessively caustic on these issues, and Kay a bit too unwilling to admit when he needs to fix a bug. I feel like Lennart gets way more hate than he deserves; he can be a bit difficult to work with sometimes, but it's crazy how some people think that he's single handedly out to destroy the Linux ecosystem.
I run a lot of software originally written by Lennart (Avahi, Pulse, systemd, heck, I recently even started using ifplugd on systems that still needed to use ifupdown but we wanted to respond properly to network cables being connected and disconnected), and find that it tends to be higher quality, more well designed, and more stable than a lot of the other code in the stack. Due to the fact that much of it changes the "traditional" way that systems worked to a very different but friendlier way, there tend to be a few integration issues along the way for early adopters; if you don't want such integration issues, it's probably best to use a stable distro like RHEL/CentOS or Debian Stable, rather than a quickly updating distro that ships code that's not yet ready for primetime like Ubuntu, Fedora, or Debian testing/unstable.
On the other hand, it's a bit funny to point those out as easy to deal with, because they are bicameral alphabets, with notions of upper and lower case, case mappings, title casing rules, and the like. That's a complex system, that if you didn't grow up with it and already have had to deal with and come to terms with it, you would probably include it in a rant like this.