sslnx's comments

sslnx | 2 years ago | on: Ask HN: Most interesting tech you built for just yourself?

Back in the day, access to the Internet was very expensive in my locality. We only had mobile data with max 20GB per month, and after that - 7KB/s unlimited for ~20% of average local salary. Having no job, it was very hard to pay that amount for the Internet, so I came up with a solution. I have set up a cloud server for 10$/month, got couple of SIM cards with that internet plan, and started developing a Linux tunnel program, which would join bandwidth of multiple interfaces into one by directing packets to my server. The server then forwards the packets further. I hadn't used it for long but it was very fun and satisfying to do it.

sslnx | 7 years ago | on: Python exceptions considered an anti-pattern

Here is the greatest inconvenience of Python exceptions for me. Say you have to try 10 different methods, and you only need one to work. Then you have to write 10 try...except blocks so that each next block is indented relative to previous. This creates unreadable code and does not scale for say 100 methods. The solution that came to mind is labeling try blocks and referring them in except blocks. For example:

  try as method1:
      method1()
  except@method1 try as method2:
      method2()
  except@method2 try as method3:
      method3()
  except@method3:
      raise NoMethodWorked()

sslnx | 7 years ago | on: Why [Insert Thing Here] Is Not a Password Killer

Fingerprint scan and Facial recognition can not replace password authentication because both face and fingerprint are public information, while password is meant to be private. You cannot hide your face or fingerprint from others.

sslnx | 10 years ago | on: Introducing Shadow DOM API

I have always been skeptical about Shadow DOM. It tries to solve different problems under one solution.

Say you want a static page without scripts but with CSS encapsulation. You cannot achieve that. Instead you have to use Shadow DOM and get it in package with other unneeded things.

CSS encapsulation could be solved with special attribute, new HTML tag or even with new CSS rule, and it would have been more flexible than Shadow DOM is.

page 1