I think they’re just stopping operations of the company in Brazil.
But I don’t think they’re going out of the way to prevent Brazilian IPs from connecting.
I think they’re just stopping operations of the company in Brazil.
But I don’t think they’re going out of the way to prevent Brazilian IPs from connecting.
You don’t need to provide root access just because you used GPL code, you just have to follow the GPL.
Well, to follow version 3 of the GPL, you do actually need to provide effective root access.
Specifically, version 3 of the GPL adds language to prevent Tivoization.
It’s not enough to just provide the user with the code. The user is entitled to the freedom to modify that code and to use their modifications.
In other words, in addition to providing access to the source code, you must actually provide a mechanism to allow the user to change the code on the device.
The name “Tivoization” comes from the practice of the company TiVo, which sold set-top boxes based on GPL code, but employed DRM to prevent the user from applying custom patches. V3 of the GPL remedies this bug.
For Zulip, I’ve only used it on the web. Apparently they have iOS, Android, Desktop, and Terminal clients.
For Matrix, there are many clients on all platforms, but none have ever stood out to me. Element is the official client, and it’s… fine I guess.
I love this, especially the criticism of the FSF.
For coms, Zulip seems OK. I would really like Matrix to take off, but I honestly don’t really like any of the clients.
Maybe.
Linux won because it worked. Hurd was stuck in research and development hell. They never were able to catch up.
However, Linus’s kernel was more elaborate than GNU Hurd, so it was incorporated.
Quite the opposite.
GNU Hurd was a microkernel, using lots of cutting edge research, and necessitating a lot of additional complexity in userspace. This complexity also made it very difficult to get good performance.
Linux, on the other hand, was just a bog standard Unix monolithic kernel. Once they got a libc working on it, most existing Unix userspace, including the GNU userspace, was easy to port.
Linux won because it was simple, not elaborate.
Zsh
No plugin manager. Zsh has a builtin plugin system (autoload
) and ships with most things you want (like Git integration).
My config: http://github.com/cbarrick/dotfiles
Exactly.
My take is that the issue isn’t with tmpfiles.d, but rather the decision to use it for creating home directories.
The Internet.
Computers do a lot of things. But the Internet specifically is the aspect of the computer that revolutionized the world.
In the case of Google, the trade off is compensation.
You can work for for Google in NYC and make $300k+ per year, or work for Google in London and make half as much at best.
It’s the USA.
Yes, they can just fire people.
I mean, it’s GPL code.
Anyone could just upload it, possibly with branding changes if “GBA4iOS” a trademark, as long as they publish the source code with their changes
Relevant xkcd
Yeah, but I want both GPU compute and Wayland for my desktop.
Long term, I expect Vulkan to be the replacement to CUDA. ROCm isn’t going anywhere…
We just need fundamental Vulkan libraries to be developed that can replace the CUDA equivalents.
cuFFT
-> vkFFT
(this definitely exists)cuBLAS
-> vkBLAS
(is anyone working on this?)cuDNN
-> vkDNN
(this definitely doesn’t exist)At that point, adding Vulkan support to XLA (Jax and TensorFlow) or ATen (PyTorch) wouldn’t be that difficult.
Unfortunately, those of us doing scientific compute don’t have a real alternative.
ROCm just isn’t as widely supported as CUDA, and neither is Vulkan for GPGPU use cases.
AMD dropped the ball on GPGPU, and Nvidia is eating their lunch. Linux desktop users be damned.
How does Kodi compare to Jellyfin?
I use Android TV and Chrome on macOS as my primary clients, and Arch on my server with an Nvidia 1080Ti for transcoding.
There’s a Wikipedia article on multiple encryption that talks about this, but the arguments are not that compelling to me.
The main thing is mostly about protecting your data from flawed implementations. Like, AES has not been broken theoretically, but a particular implementation may be broken. By stacking implementations from multiple vendors, you reduce the chance of being exposed by a vulnerability in one of them.
That’s way overkill for most businesses. That’s like nation state level paranoia.
+1
From an order of magnitude perspective, the max is terabytes. No “normal” users are dealing with petabytes. And if you are dealing with petabytes, you’re not using some random poster’s program from reddit.
For a concrete cap, I’d say 256 tebibytes…