> Private IP space is incredibly useful. I build it and set it up -- my ISP does not have control. This is _gone_ with IPv6 and it makes things much more complicated than they need to.
Not in the least; IPv6 has private address space just like IPv4.
Google really screwed everyone that used this; it was marketed towards families/small groups, and now everyone is forced into Google Workspace with massive breakage for family-like stuff. Thanks Google.
This is a really great breakdown. With TPUs seemingly more efficient and costing less overall, how does this play for Nvidia? What's to stop them from entering the TPU race with their $5 trillion valuation?
Sorry. I don't trust these guys. Some of my Linux laptops use their wireless hardware and the drivers are so poor that, YEARS later, Wi-Fi still doesn't work right.
In a nutshell, Comcast used to provide a /60 to residential customers and this could be subnetted into more than one LAN. Nowadays they only provide a single /64 and this can only be used for one subnet.
I actually took this to heart and deployed it natively on multiple VLANs in my home. Then, even with the abundance of address space, Comcast pulled the ability to use IPv6 in this manner and I'm back to to using NAT on all my VLANs except for one. Progress.
Yeah. I'm as frustrated as you are. I had an app in the app store even with all the restrictions around SMS, but there's simply no way to integrate with RCS, so this is basically Google's iMessage.
Strongly disagree on this one. All operating systems require maintenance of some sort, but you singled out Void and I find I'm doing far less maintenance with this one. Even with the venerable Debian, it always required some sort of regular maintenance to work around the bugs of it's legacy packages; Void does not have this glaring issue.
What made you leave Void? I tried Debian, but I just couldn't do it; too dated and too many workarounds for the dated bugs. I tried Testing and Sid as well, but the only taste that I was left with was that these, somewhat obviously, are not meant to be production distributions and, while they get newer stuff, they're simply too buggy for daily use.
> If "automatic updates" were optional and off-by-default then users would not be vulnerable to something like SimpleMobileTools
The problem is the vast majority of users want this on by default; they don't want to be bothered with looking at every update and deciding if they should update or not.
He's not wrong, but I gave up on Windows because I found Windows annoyances more annoying than Linux's annoyances. Then again, I buy hardware from companies that support Linux, and he didn't, so I've had fewer issues.
Nice to see, though I gave up on Windows a short a while ago for Linux and KDE's Krunner is seriously awesome; even used it to do some trigonometry the other day!
You, kind of, don't have much of a choice. There's thousands of packages and it's a ton of work. In addition, as Linux continues to get more popular, more vendors are releasing software that doesn't care to work with newer libraries, so Flatpack handles this nicely.