4 ms·
That's a really bad idea. You need to have a good counterexample, otherwise it's just wasting time at the best case. A lot of people learn from really bad codeb
by kissgyorgy 7y ago
That's a really bad idea. You need to have a good counterexample, otherwise it's just wasting time at the best case. A lot of people learn from really bad codebases and picking up the same style which is terrible. You should look at GOOD codebases instead!
- theSage 7y agoI did some work on html2text when I started off and while the little parts did make sense, the whole library was confusing for me. I couldn't change anything without breaking tests. On the other hand I've been tinkering with curio for a while now and it's a fresh breath compared to that. My trouble is that I still don't understand what makes the html2text thing "bad". What particular thing there caused me to not like working with it? I'm trying to understand that. I've been book hunting + figuring out if it's something that I did not know which would have made the code a lot easier to work with (stuff got a lot easier after I cleaned up my set theory understanding) - https://github.com/dabeaz/curio https://github.com/dabeaz/curio - https://github.com/Alir3z4/html2text https://github.com/Alir3z4/html2text