Conversation

Notices

1. Embed this notice
   Kit Rhett Aultman (roadriverrail@signs.codes)'s status on Thursday, 18-Sep-2025 17:28:31 JST Kit Rhett Aultman

   The single most galling moment for me in working on various "modern" languages is actually at the moment of install when I realize they're asking me to intentionally throw the idea of my machine running a curated distribution out the window.

   I have been repeatedly told I'm an out of touch oldhead who "doesn't get it". Yet, here we are...
   https://drewdevault.com/2025/09/17/2025-09-17-An-impossible-future-for-JS.html

   • Embed this notice
     I Forget (epilanthanomai@signs.codes)'s status on Thursday, 18-Sep-2025 22:10:36 JST I Forget

     in reply to

     @roadriverrail Do you mean the thing where every language invents its own cross-OS package management?

     As a backend dev of 25+ years who's lived and breathed package management for most of that, I've been souring on them over time. They have a lot of potential for building an OS-agnostic dependency layer. But IME everyone gets lured in by easy access to bleeding edge cowboy libraries, and almost nobody wants to invest in maintenance discipline, much less let go of toolkit chauvinism.

   • Embed this notice
     Kit Rhett Aultman (roadriverrail@signs.codes)'s status on Thursday, 18-Sep-2025 23:38:51 JST Kit Rhett Aultman

     in reply to

     • I Forget

     @epilanthanomai I'm indeed talking about just that, particularly the part where some useful tool, often written in Python, is incompatible with the standard Python libraries on my distro, so I then have to fix that, but I'm not supposed to update my *system's* Python packages but make a virtual environment for the tool to live in, and each tool needs its own solipsistic and incompatible world.

     Golang and Rust are vaguely better since they're compiled, at the cost of statically linked binaries.