345 karma · joined February 16, 2016
The current state of web development makes me sad, mostly because it's all fault of all the die-hard javascript developers, you know what f*ck all javascript/ecmascript/typescript/node developers.
R: NO, https://github.com/keepassxreboot/keepassxc/issues/148
> Why should I move from KeePass2 to this?
R: KeePass 1.x and 2.x are the official KeePass releases, KeePassX is a community port in C++ originally built for Linux/Unix but now it includes builts for Windows too. Most people that recommend KeePassX over KeePass 2.x is because they are (.NET/Mono)fobics, plain paranoids or just haters of microsoft. KeePassX and KePassXC aren't improved versions of KeePass they are just ports to C++ (for Linux and Windows) of KeePass.
And this point of failure for many startups was beautiful represented/mocked in the silicon valley series of hbo: https://www.youtube.com/watch?v=Lrv8i2X3gnI
WHAT? 2017 and you haven't met or saw a hooker in your life? you are kidding right? well if you want to meet some without leaving your room you could just search escorts in your area, it's pretty much the same as an a hooker just more expensive, don't be afraid to try! just remember to paid them after not before.
Linus hasn't ever been security-minded, in fact half of the article is about Linus making a complains to Kess with things like "it will be slow to compile, it's a PITA to mantain, i don't understand it therefore is crazy and nobody needs this", so if you value security over anything else then Linus isn't the best person to rely for an advice on the topic.
> For me, the fact that it has existed for 10 years and _not_ been merged does not speak highly to it's quality
Parts of the grsec patch have been implemented over the years but not the whole mostly because Linus doesn't understand the need of most of the features not for quality reasons.
> I feel that any non-kernel dev applying a patch to their kernel is the opposite of a good security recommendation. I'm not nearly as qualified about the tradeoffs between performance and security or even code quality as Linus and the kernel team. That's why I delegate the decision about what code goes in my kernel to them
The fact that you don't understand why you need it, it's the very reason why _you_ shouldn't use it. Leave that decision to someone else on your team with experience handling incidents not to Linus et al.
A _good_ CEO it's worth more than 1 good engineer by the fact the second one needs input from the first one, a good engineer is useless without a goal or an idea to develop. Software Foundations are probably the only places were this tough isn't valid for everything else it should.
> Containers are not meant to store data. Actually, they are meant by design to NOT store data. Any attempt to go against this philosophy is bound to disaster.