HN user

deeter72

98 karma
Posts0
Comments22
View on HN
No posts found.

I use WSL for work as well and in my opnion it fits Microsoft's classic "embrace, extend, extinguish" paradigm.

WSL basically prevents most from requesting from the IT dept, A full blown Linux desktop/Laptop because they will simply say "you want Linux? here have WSL, it is 100% Linux", Which it is really not, WSL's idiosyncrasies from a true Linux Desktop drives me nuts at times.

Damn here I was hoping I was safe on Opensuse TW with Kernel 6.3.2

Thankfully I should be able to rollback with Opensuse's snapper. This is the key advantage of Opensuse TW in my opinion, The BTRFS filesystem alongside snapper helps maintaining a reliable system while on the bleeding edge.

This is a gross generalization. And I'm not sure where you are picking up those values from as well or their accuracy, for Flask is ~15,000 on uWsgi or Gunicorn? or the default werkzeug dev server? How you deploy matters very much I'm sure you'd understand.

However, Ultimately development teams make do with the skillset they have and saved development time is saved money. Who cares of the toolset, Most programmers forget about the business objectives ultimately. Instagram's backend was originally Django, they managed just fine for a long time. Using C++ is pretty overkill even for a simple API project and potentially a huge waste of developer time, people seem to forget developer time is expensive.

For me personally because the author of KeePass is a stubborn person who is hellbent on not using a VCS. I see no reason why one would not use a VCS in 2020. From a security point of view this is a massive violation of trust due to the fact that a criminal entity could hypothetically sneak into the computer of the author of KeePass and modify a cpp file to link to malware and the author will have no idea of it and when he compiles and distributes it. He would have unknowingly distributed malware which due to the context of the application can cause massive damage.

I do know that I can compile myself but still I cannot audit every single release, this can be migitated by myself using git and extracting tar files on every release. But this should not be this difficult.

KeePassXC on the other hand is more practical and works on all platforms consistently and is easy to compile with cmake and has convenient cmake switches to disable network connectivity.

Again not the most ideal way to do things and Mozilla is doing a different approach to Chrome and Edge. and also a concern is that malware can use DoH to retrieve data without logging suspicious DNS queries on Firewall DNS logs which are monitored to highlight of new domains that have not been pre-approved.

DNS should be something that is handled by the OS. I favor DoT which is secure and practical over DoH.