Re: GIMP 3.0.0-RC1

On 1/4/25 4:24 AM, 186282@ud0s4.net wrote:

On 1/3/25 7:27 AM, -hh wrote:

On 1/3/25 6:52 AM, The Natural Philosopher wrote:

On 03/01/2025 11:45, D wrote:

No I think it is just because someone pulled in comp.os.linux.advocacy. Seems a lot of trolls reside there. I looked into it, found it way to annoying, and stopped. But I got a reminder of why I stopped reading that group.

>
Yup. Ain't that the truth.

>
Yup, its a product of crossposting.  Things change and USENET just doesn't have the audience it did 30 years ago to have groups have sufficient critical mass to sustain (on- or off-topic) dialogs/

    USENET isn't what it was ... has kinda fallen off
   the proverbial radar. IMHO this is kinda GOOD.

As much as the 'Eternal September' days of disruption were a nuisance, the downside today is a manifestation of aging and decline:  there's probably zero current participants in these newsgroups who are under age 40 ... and the average age is probably closer to 65.

   Shit ... when I first got into Usenet the AI guru
   Minsky used to post to the AI groups - things were
   respectable then.

I can recall chatting with John Godwin about the Internet Law named after him (“As an online discussion continues, the probability of a comparison to Hitler or to Nazis approaches one").

Linux is good all by itself. Doesn't need advocacy.

>
Its a tool like anything else, so use the right tool for the job.

>
   Well ... 'tool', yes ... but ALSO a 'philosophy',
   a way of looking at things. Lin is NOT Win.

Sure.  This is just a simplifying conversational expediency, not a PhD thesis.

Advocates in COLA have historically fight against the wisdom of understanding that everything has its own strengths & weaknesses, swimming against uses where other solutions are better.

    Well, Win is MOSTLY 'weaknesses' ....
 

For example, take a new digital camera: wouldn't it be nice to not have to wait a year to read its new RAW file format?  Most folk just want pics, so they choose a platform where its supported on launch, not to have to sit down to DIY write & test a 3rd party driver first.

    Linux, and esp BSD Unix, are always a bit behind
   the driver curve. However I've never found that to
   be a major inconvenience. Much stuff just doesn't
   change that quickly anymore.

Which circles back to "right tool for the job" for when one is buying new stuff for whatever purposes; the example I used here was digital camera gear (& a 2025 New Years resolution is to start to meddle with higher video formats on my still-new-to-me 2022 Canon R6 Mk2).

Meantime, my New Year's Resolution is to tweak my Linux NAS; seems that it needs a better RAM cache to not bottleneck on network, and those parts are due to arrive this weekend. I'll have to look around to see if I have some spare NVMEs to change up its disk cache while I'm at it too.   If that doesn't resolve things, then its probably time to look to some network gear to move some nodes from 1GbE to 10GbE.

    Done lots of NAS over the years. Used packages
   and kinda wrote my own too.
    Yes, 'tweaks' can help - a LITTLE.
    However, if you really try to benchmark it, the
   tweaks don't REALLY add much but complication
   and ops for failure.
    So, from my long experience, stick close to
   'vanilla' and you'll do OK and not SUFFER.

Precisely, because its intended to be a tool, not a toy.  I did get the RAM installed yesterday & its rebooted and recognized fine; will want to run a couple of throughput performance tests.
Didn't have time to look for spare NVMes to swap out ... but that was more a case that the current ones are gratuitous overkill (2 x 2TB) so it would be nice to repurpose them - I've been looking at using them to make a "zero cost" duplicate instance of my entire photo library to give a test run on "DigiKam", a FOSS photo management tool which came recommended.

   Oft unrealized gem these days - OpenMediaVault.
   It's become a very complete NAS system yet is
   still kinda 'light' code-wise. DO note that
   you can't just write randomly to its files
   because the system won't index it - will not
   think your direct writes exist. Gotta set up
   like SMB shares in scripts or whatever that
   ref it's 'approved' shares. THEN it'll work.

I still have a couple of old towers sitting around if I want to get frustrated with a random homebrew project!  <g>  Which in semi-serious form would be a decent use of the pile of small (<8TB) HDDs I've accumulated, but it would probably add +$10/month on my electric bill.
-hh