I kind of like this guy, as in he is funny. But seeing the previous linux sucks videos as well, I must say that he most definitely don't have a too deep knowledge of linux - and it is kind of mean to call Linux people dumb who advocate for flatpak over appimage, especially that he don't really understand the problem at hand. (though imo nix is the only one solving the problem properly)
No, nix can cache already built binaries with hydra, so on a normal system it simply downloads from there - same speed as apt or the like.
During the audit they likely disabled it, so nix had to build everything from scratch (like even system libraries, the build tools, everything).
It sounds like "this is the first time I've seen this build system and don't really see how it works, would be better to change it to a more often used one".
Which is fair for a security auditor, but it stems from the newness of the project and nothing inherently bad with it - like I doubt they know what actually happens inside whatever other build system other's use, but since they empirically know it poses no threat they are okay with it.
If you ask me, this is absolutely no reason to not use Nix - well maybe not for a bank (though on long term they would definitely win with it)
But I do agree with you, it's not as straight-forward as it should be yet. But I absolutely love how I can be certain that no garbage is accumulating on my computer like I needed this program one time and I don't even know what does it do, yet I have it's complete dependency graph installed that the package manager can barely uninstall.
In nix I just create a `nix-shell -p package` for one time use, do my work and then forget about it. At the next `nix-collect-garbage` it will be removed from my computer completely.
They all use different UI toolkits, some are gtk, some are java UIs, some are electron-based apps. So that's why - it's a higher level problem that is unfortunately inherent to desktop fragmentation which is hard to avoid on linux.
That's why designing the actual program is important. Also, static and strong typing for powerful refactoring plus extensive tests, and you can refact that Dragon class into something new.
And while I do agree with you, I think it is not OOP that's bad but the programmer doesn't understand when to do inheritence vs composition etc
But that's not true. While lethality is estimated at tops 3.6%, the cases requiring hospitalization, including breathing apparatus, etc are quite high, and it WILL overflood the capacity of hospitals in virtually every country that didn't take really really serious precautions, of which there are only a handful.
It will be a big problem both in Europe and in the US, because they are starting to take measures only now.
The vast majority of cases are mild, like a head cold. This is a fact, and has been reported around the world.
You’re arguing about relative hospitalization rates, but that has nothing to do with the discussion here. Mild cases aren’t clogging up ICU wards at all, because they’re quite mild.
What do you mean? As I understand it it depends on the font - you can provide any sort of encoding. So Unicode is there, I don't see how that would be harder than with the latin abc (which is still a hard problem as per the article)
https://www.youtube.com/watch?v=7Hai7cavmUY