News for hackers. Stuff that matters.
Re:Bash-ini-parser: Advanced bash INI parser library by ndsipa_pomu on Friday April 04, 2025 @07:18AM (#43580629)
That's all well and good, but if you're looking for a language that will survive for decades, then BASH or shell scripts are a better choice. Often, there'll be some ancient machine that's been almost forgotten about and will die and need replacing. I can trivially copy a 30-year old BASH script and run it on a new machine, but can you do that with a 30-year old Python programme? How will today's Python survive the next 30 years?
Re:Bash-ini-parser: Advanced bash INI parser library by theamk on Friday April 04, 2025 @12:20PM (#43584623)
python 3.0 code, released back in 2008, is still compatible with latest released python, with some exceptions like asyncio or obscure file formats which are unlikely to appear in scripts. The pip packages likely did break, but we are talking about python-with-stdlib here.

Granted, it's not 30 years old, but 17 years is pretty impressive. And I don't think there will be another big break, the 2.0->3.0 transition was so painful they'll likely avoid another one for decades.

Re:Bash-ini-parser: Advanced bash INI parser library by ndsipa_pomu on Sunday April 06, 2025 @07:00AM (#43600507)
17 years is very good. I don't have anything against Python, but there's a particular niche that shell/BASH scripts are ideal for. I keep considering writing more stuff in Python, but BASH operates at just the right level for tying systems together (computer duck tape).