Michał "rysiek" Woźniak · 🇺🇦Ermahgerd, #LibResilient ( https://resilient.is/ ) got a code contribution and, more importantly, someone is putting a lot of effort into diving into a somewhat complex issue they are affected with!
I am very excited about this development.
I am at the #GlobalGathering in Estoril, Portugal this weekend, and have booths about #LibResilient (Saturday, 15:30 - 17:30) and about #Quad9 (Sunday, 15:30 - 17:30).
If you're there as well, come say hi!
Got interviewed about #LibResilient for NGI
(emojis added by the editors)
https://www.ngi.eu/ngi-interviews/michal-wozniak-libresilient/
Here's the link to the project (that somehow does not show up in the published interview, sigh):
https://resilient.is/
And here's the talk I gave at MCH2022 about it:
https://media.ccc.de/v/mch2022-198-trusted-cdns-without-gatekeepers
A few issues got created by someone and another merge request was submitted to my little side-project! 
One of the issues is about having a release. My little project is growing up so fast! 
The project website is here by the way, in case anyone is wondering:
https://resilient.is/
I just finished Doing A Thing and I am very proud of myself. Winning at adulting. And #LibResilient just got content-based MIME type deduction. Weee!
I just spent 30min thinking about how I would implement a specific thing that would help me test improvements to #LibResilient with less fuss…
…and then discovered that I had already implemented that very thing months ago.
I am a highly skilled professional, I swear.
Old tests runtime: 1m45s
New tests runtime: 0m26s
Code coverage up 20%, to ~87%.
I am okay with this. And all it took was rewriting the tests to Deno over a few months.
Also, #LibResilient finally has zero Node/npm related crap. I cannot express how happy I am about that.
Rewriting #LibResilient tests in #Deno and… damn!
The number of random "add a timeout to wait here and hope all random promises started deep in the code resolve before it" I am removing — partially because I now understand my code better, partially because Deno has sane, reliable implementations of WebAPIs — is quite substantial.
Makes me a happy camper.
Rewriting #LibResilient's tests in #Deno (from NodeJS and Jest) not only helps me write cleaner code and get rid of the mess that npm dependencies are, but also it helps me understand #JavaScript better, it seems.
In a number of places (in tests and in code they test) it forced me to actually *understand* some quirk of the language and re-write stuff in a cleaner, more unambiguous, easier to debug way.
Can't wait for the rewrite to be done so that I can remove the last bits of npm crap!
About a thousand lines of code re-written from NodeJS/Jest tests to Deno:
https://gitlab.com/rysiekpl/libresilient/-/merge_requests/19/diffs
About 1/5th towards the milestone:
https://gitlab.com/rysiekpl/libresilient/-/milestones/12
Rewriting all tests for Deno will mean I am able to completely remove NodeJS stuff from #LibResilient. Which I am very excited about!
