in reply to Re^17: Ideas for "fixing" PerlMonks 1.0
in thread Ideas for "fixing" PerlMonks 1.0

welcome to our world. Do you think it’s any easier for us to understand?

I thank you for looking into it. I feel like you have validated our long-term collective reluctance to do anything about it.

  • Comment on Re^18: Ideas for "fixing" PerlMonks 1.0

Replies are listed 'Best First'.
Re^19: Ideas for "fixing" PerlMonks 1.0
by LanX (Saint) on Dec 23, 2024 at 10:00 UTC
    Risking to repeat myself:

    This can only be solved with a real DEV environment.

    As a pmdev I can only do static code analysis with one arm bound at behind my back.

    And any patches are directly injected into the running system, I have to be available when the gods decide to do so.

    That's like a doctor only allowed to scratch dead bodies to find a cure.

    A god can log on to the machine and access the living creature, look into the logs and run queries against the DB. A god could find out if a code-snippet is relevant or just abandoned experiment.

    A DEV environment would allow to fork the current engine, implement tests and run experiments.

    Probably best in a container.

    Wishful thinking, I know.

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    see Wikisyntax for the Monastery