Fuck tradition
- it has undefined and null
- it stringifies everything internally making it extremely slow, difficult to optimize, and fragile
- it has strange implicit conversion rules
- it has a strange standard library that is incomplete and poorly designed. For example, sorting, without binary search.
- it doesn't have integer type or integer operations
- it has a horrible developer community and ecosystem which actively encourage the worst development, security, and business practices.
How? It really sounds insecure when you think about password databases
Damn. This is very true.
But they're encrypted.
>Whats wrong with javascript
everything. it's an absolute bullshit language. I'm forced to program with it because: no alternative.
>Passwords should never be transmitted over the network or stored in remote databases
oh, we better shut down the entire fucking internet. nothing wrong with storing passwords in remote databases as long as they're hashes of the passwords and properly protected using something like bcrypt.
are there any tradeoffs? it seems if you really liked your folders you could emulate that easily. would algorithms work?
Why is Fortran still maintained?
There are many PAKE protocols but here's one example: en.wikipedia.org
The basic idea of a PAKE is that you have a cryptographic function that takes input from both the client and server, returning a key that is used to determine whether or not the authentication attempt is successful. Because the server only cares about the output of that cryptographic function, the client never needs to send a password even when creating an account. PAKE can also be used to enforce more robust security policy on the serverside since you can isolate your key exchanges per resource.
Because it has the advantage of being first to the scene with a compiler and tons of effort put into optimizing the fucking hell out of it, making it one of the best tools for scientific computing.