I feel like this is Python starting to take it's position more seriously and mobile is (for better or worse) the future that has the widest reach. If Python wants to keep its ground it has to keep up, and I hope it does.

Not developing a ton of apps these days, but would be cool if I could just port of a webserver/front-end with minimal cruft in-between code and OS.

It would be insanely cool to just be able to drag together a quick UI, hook it up to some python logic and have a working app.

Ohh, things were simpler back in the visual basic days.

About time... a big win for geneticists.

Did anyone else find that Blippi video deeply disturbing? I was warned, but still recovering...

One of the great parts of the Python ecosystem for data processing is https://ftfy.readthedocs.io/en/latest/ which can handle mojibake and many other unicode-related translation problems.

But seriously, I'm always a little upset when data vendors/customers/etc don't specify the encoding they are using. You'd be surprised how many official or unique sources still use weird encodings in the name of compatibility.

If you want to test ftfy online it's available here:

https://ftfy.vercel.app/

FTFY is amazing. Really useful for processing excel generated csvs.

Funny, I have used it for the same use-case (and a sad reminder how horrific Excel's handling of UTF-8 in CSV files can be...)

"The Simpsons already did it"

So, not sure I want to go down the Google-hole, but curious what changes have been going on recently with all the chaos in Easter Europe.

Are dormant stations coming alive?

All the cool kids listen to SKYKING now. There's a fairly persistent community around doing OSINT on that.

Not sure about becoming alive but numbers stations have been operating for awhile now. A simple one time pad [1] can be used .[1] https://en.wikipedia.org/wiki/One-time_pad?wprov=sfti1

Cloud/SaaS providers could learn a lot from this practice

Okay, I'm interested but not quite following. How so? Are we talking software, or do you mean to get more mileage out of hardware by fixing failed machines?

Great advice: "If you are seriously considering using this script, please don't."

Gin for most parts Zap for logging Then Docker up the binary in busybox and run on AWS ECS

I've tinkered with echo and a couple other frameworks, but Gin is widely used enough that I can usually stack overflow most issues.

Working on a pretty sick karaoke website as well as a jeopardy training application. I figured since both involve lots of copyright nonsense that it was best just to do these as personal labors of love.