299 reputation
29
bio website
location
age 21
visits member for 2 years, 7 months
seen Dec 10 at 13:51

Someone in the world who likes games and C++.


Oct
30
awarded  Popular Question
Oct
26
comment Decision for Unchecked Exceptions in Scala
Never understood the most people don't handle checked exceptions` argument. Most people aren't good developers. I guarantee that most developers aren't going to handle error result anyway. Actually, try..catch seems much more readable than if. What's more I can also guarantee that those same most developers aren't going to write code that returns error result - too complicated in Scala - you can't even return from a function whenever you want (just like in Pascal)
Sep
24
awarded  Autobiographer
Sep
15
awarded  Nice Question
Jul
30
accepted Should data be stored to local database in Android when heavily using REST services?
Jul
30
asked Should data be stored to local database in Android when heavily using REST services?
Nov
13
awarded  Notable Question
Jul
28
comment Preventing password hashing algorithm from overloading CPU
@JamesSnell, true, missed this one out. Thanks for sharing the method. However, I believe, this re-introduces original security problem which was solved by moving away from the fast algorithm - password is stored in such hash so that it can be relatively easily guessed.
Jul
28
accepted Preventing password hashing algorithm from overloading CPU
Jul
28
comment Preventing password hashing algorithm from overloading CPU
I find Option B being as bad as not being able to process all the requests. If you can lock user's account after X attempts (even if it's for a short period of time), you can pretty much shut off most users from using the website. Option C, however, seems like a better all-around solution.
Jul
28
comment Preventing password hashing algorithm from overloading CPU
@JamesSnell, you don't get to choose faster or slower algorithms depending on the load. You must use same algorithm for generating the hash and checking password validity (or whatever you are hashing). If you meant slower/faster algorithm implementations, then I see no reason to use the slower one at any moment.
Jul
28
revised Preventing password hashing algorithm from overloading CPU
Fixed grammar
Jul
28
asked Preventing password hashing algorithm from overloading CPU
May
25
comment Pros/cons between emphasizing client-side or server-side processing
I don't think SQL injections have anything to do with moving most of your logic to the client-side. Even if you move data processing to the client-side, you still need some sort of server-side service which would actually run SQL queries (unless you want to make your database username and password public). That service is responsible for validating and escaping data. There is no difference there - you MUST validate and escape any input on your server-side ALWAYS. There is simply no way around it.
May
6
awarded  Yearling
May
1
awarded  Popular Question
Apr
22
comment REST vs RPC for mobile development
Protocol buffers are thrift seem something really interesting to look deeper into, thank you :)
Apr
22
asked REST vs RPC for mobile development
Mar
26
comment What is the supposed productivity gain of dynamic typing?
Usually job is considered 0 % done until it runs all the tests successfully. Only then your progress can be considered more than nothing. With that in mind, I don't think it's worth measuring your productivity on something that hasn't been finished yet.
Jan
4
accepted Many Blocking VS Single Non-Blocking Workers