Holy shit the way he adjusts his glasses slowly is so badass haha <| sep |> I feel like today after all the turkey I ate <| sep |> I loved how the entire chat freaked out at the sight , and his answer is something like Look , I have long fingers <| sep |> man , this is hella somber , ugh i ' m in a better place after hearing this . keep it up . the sidechaining with the kickvocals or whatever is going on in there . so dope <| sep |> You are my hero . I can ' t believe I overslept . Although I am thankful AF for you every game . <| sep |> I ' ve bought 2 of the black friday bundles . However , I didn ' t want to use the 50 energy yet . How long do I have to claim them ? <| sep |> I didn ' t hear that , thank god if you ' re right <| sep |> It ' s well argued . But it ' s also five years old . He actually wrote a blog post just a few weeks ago where he makes some reflections about this . Here ' s an excerptBe Careful About What You Dislike Armin Ronacher , Nov 5 th 2016 c arefulaboutwhatyoudislike . In fact , I myself campaigned for some changes to Python 3 that made it possible to achieve better ports like the reintroduction of the u prefix on Unicode string literals and the bulk of my libraries work on Python 3 for many years now . It ' s a fact that in 2016 the problems that people have with Python 3 are different than they used to have before . This leads to very interesting conversations where I can have a highly technical conversation about a very specific issue with Python 3 and thoughts about how to do it differently or deal with it like some of the less obvious consequences of the new text storage model and another person joins into the conversation with an argument against Python 3 that has long stropped being valid . Why ? Because there is a cost towards porting to Python 3 and a chance is not seen . This means that a person with a general negativity towards Python 3 would seek me out and try to reaffirm their opposition to a port to it .