[ale] Ansible and Python comment?

[Leam Hall]

On 9/12/24 08:39, Dylan Northrup via Ale wrote:
> I am very, very behind on my ALE email, so apologies for replying to this
> thread a few months late.

But so much good information that it's worth the wait!

> You might think! But Python does not follow https://semver.org/ and makes
> breaking changes in minor versions of its core libraries (like, y'know,
> having `from __future__import annotations` work on 3.6 but not work on
> 3.7). One more reason I'm not a Python fan.

Python is great if you want a job, but yeah, not very portable.

I'm not sure if it's funny or sad that the Ansible developers preclude use of "current" Ansible on RHEL 8, since Ansible came from Red Hat and there is no RHEL 10 to migrate to. Other Linux versions, like Amazon Linux 2023 (Python 3.11) work just fine.

> It's not whether the code compiles, it's whether it runs. Are you linking
> against libc? Oh, that doesn't work in this apline container. Compiled for
> x86? Oh, we're using ARM hosts.

. . .

> Ruby is my preference for an interpreted language[2]. Go is my preference
> for a compiled language[3]. Bash is my preference for a "must run on *nix
> systems where you can assume only a base install".
> 
> [2]: And I mean Ruby, not Ruby on Rails.
> [3]: It's very easy to cross-compile to target other hardware and OS
> platforms and, presuming you're not doing system/hardware fiddling,
> requires no code changes.

I knew I liked you for a reason! If Ruby off Rails had any real job market I'd still be there. Go seems like the best compiled option; better developer experience, more portable/cross-compilable. Sadly, I'm not sure I'm a good enough Go developer to get a job with it.

Leam

-- 
DevOps Engineer            (reuel.net/resume)
Scribe: The Domici War     (domiciwar.net)
General Ne'er-do-well      (github.com/LeamHall)