I've been writing a bunch of TypeScript lately, and figured out why most of the "Async" modules out there are actually fakin' the funk with coroutines.
Turns out even pedants like programmers aren't immune to meaning drift! I guess I'm an old man now lol.
Article mentioned:
Troglodyne Q3 Open Source goals
1615831259
-
Release PageNSA page activity watcher.
-
Build a new tool "pairwise". I'll do a video on this soon.
-
Release a few of my "test obscure scenario" scripts.
-
Configure automatic docker image creation and Github actions for tCMS
-
Finishing the transition of tCMS to "everything is a series" data model (see Issue 130)
-
Porting Overload::FileCheck to windows - This still has a couple of failing tests (I’ve screwed up something porting over the XS): teodesian/Overload-FileCheck at win32 (github.com)
- Adding JSONWire support (and then WinAppDriver support) to Selenium::Client
- Re-factor Selenium::Remote::Driver to use Selenium::Client as backend rather than Selenium::Remote::RemoteConnection, CanStartBinary, etc
- Writing unit tests for Selenium::Client
I'll publish a retrospective video on Q2 performance and Q3 goals soon.
I got a client which works with Selenium v4 and WC3 Selenium! I decided to make a new module rather than deal with some of the design decisions that made maintaining Selenium::Remote::Driver such a pain, and was freed up to bake in some nice features in the bargain.
I also go over the various "gotchas" with the new selenium and where we go from here with the module and Selenium::Remote::Driver.
Selenium v4 looks like some good stuff, so it's about time to bring it all to the Perl community since it's going mainstream this February.
I did a deep dive into how pasted links turn into previews in chat and social media applications and was pleasantly surprised to find CPAN had the solution for me. I found a couple of gotchas you might want to know about if you don't want to figure this out the hard way.
It took a bit of creative thinking to cram a site that wasn't my brainchild into muh box. Though thankfully it didn't require too much custom fitting and fixes to get the job done.
That said, it could have gone a lot smoother. Discussing that and more!
tCMS is more or less doing what we wanted it to. What's more, it fit into the time we allocated for getting it done! Today we looked back at what we did and where we want to go next with Troglodyne.
Now that the prototype has gone to production twice, we mull on what lessons we've learned and where to go next with it.
1607539436
🏷️ houstonpm
So glad to be away from hugo; getting themes to be responsive there was like pulling teeth.
We can also disintermediate our video content from YouTube (and other content aggregators). We're living the dream, baby!
Come see
our presentation on tCMS this Thursday at Houston.PM!
