1. Forum
  2. Usenet
  3. COMP.LANG.PROLOG

  • Interview with an Emacs Enthusiast [Colorized]

    From Mild Shock@21:1/5 to All on Sat Jun 14 23:10:06 2025
    Hi,

    The average Prologer in 2025:

    Interview with an Emacs Enthusiast [Colorized] https://www.youtube.com/watch?v=urcL86UpqZc

    What happens when a Prolog does a web server?

    You end up with the PiLLoW framework,
    with nonsense such as html//1 and print_html/1.
    This is the worst "milestone" ever in Prolog.

    https://cliplab.org/Software/pillow/pillow.html

    Bye

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mild Shock@21:1/5 to Mild Shock on Tue Jul 8 16:37:06 2025
    Hi,

    Wanna found an IDE business. Well the Editor
    is only the Tip of the Ice Berg. What gives
    you wings like red bull, is this:

    - Instant editing:
    Files don’t really have a modified status,
    they get directly written. Typically the MVC
    is buffer based there. But for instant editing,
    buffers are written when an application switch happens.

    - Local File Content History:
    IntelliJ keeps a local file content history.
    This compensates the dangers of instant editing.
    Instant editing is very useful for tool interaction,
    like interacting with a Prolog system. Through local
    file content history I can view local changes and
    undo them across IDE starts.

    - CVS Integration:
    IntelliJ has CVS integration, like SVN, GIT, etc..
    through their local history. You can freely choose
    what to commit or not. And you can also receive
    changes from a repo.

    - File System Operation Integration:
    Local File Content History and CVS Integration are
    in sync with refactoring. So when I move a file, this
    is a move on the file system. But File Content History
    and CVS don’t get confused by a move. The simply show it
    in their history as well.

    - File Content Index:
    The IDE also maintains a global text index, and
    this text index gets notified by external changes and
    internal changes. They pretty well have it always accurate,
    including file moves, lengthy re-indexing of a whole
    repository happens rarely.

    Mild Shock schrieb:
    Hi,

    The average Prologer in 2025:

    Interview with an Emacs Enthusiast [Colorized] https://www.youtube.com/watch?v=urcL86UpqZc

    What happens when a Prolog does a web server?

    You end up with the PiLLoW framework,
    with nonsense such as html//1 and print_html/1.
    This is the worst "milestone" ever in Prolog.

    https://cliplab.org/Software/pillow/pillow.html

    Bye



    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mild Shock@21:1/5 to Mild Shock on Tue Jul 8 19:39:23 2025
    If you have a suitable Prolog plugin,
    you can do all kind of search,

    Currently the marketplace shows me only one Prolog
    plugin, but it rather adresses gprolog than SWI-Prolog.
    Strange I think there were more. But if plugins don’t

    get maintained they often become incompatible.
    I didn’t try the below yet, seems to be new!

    https://plugins.jetbrains.com/plugin/20982-prologcode

    So only I Prolog tries to tap into a company like
    JetBrains that has profit of at least 200 million USD
    per year, with a growth of 5 - 7% per year.

    Prologers are all communists I guess.

    P.S.: The plugin seems to be from Switzerland.
    But it wasn’t me! PrologCode is a plugin for IntelliJ
    IDEA that provides support for the Prolog language.

    Specifically, it provides:

    Prolog syntax highlighting
    Prolog code completion
    Prolog code folding
    Prolog code navigation

    Three different ways to run a GNU Prolog REPL
    Real-time background syntax checking.

    Initially, this plugin was developed as part of
    a project for the course “Programmation
    logique” at HEIA-FR.

    https://www.heia-fr.ch/

    Mild Shock schrieb:
    Hi,

    Wanna found an IDE business. Well the Editor
    is only the Tip of the Ice Berg. What gives
    you wings like red bull, is this:

    - Instant editing:
      Files don’t really have a modified status,
      they get directly written. Typically the MVC
      is buffer based there. But for instant editing,
      buffers are written when an application switch happens.

    - Local File Content History:
      IntelliJ keeps a local file content history.
      This compensates the dangers of instant editing.
      Instant editing is very useful for tool interaction,
      like interacting with a Prolog system. Through local
      file content history I can view local changes and
      undo them across IDE starts.

    - CVS Integration:
      IntelliJ has CVS integration, like SVN, GIT, etc..
      through their local history. You can freely choose
      what to commit or not. And you can also receive
      changes from a repo.

    - File System Operation Integration:
      Local File Content History and CVS Integration are
      in sync with refactoring. So when I move a file, this
      is a move on the file system. But File Content History
      and CVS don’t get confused by a move. The simply show it
      in their history as well.

    - File Content Index:
      The IDE also maintains a global text index, and
      this text index gets notified by external changes and
      internal changes. They pretty well have it always accurate,
      including file moves, lengthy re-indexing of a whole
      repository happens rarely.

    Mild Shock schrieb:
    Hi,

    The average Prologer in 2025:

    Interview with an Emacs Enthusiast [Colorized]
    https://www.youtube.com/watch?v=urcL86UpqZc

    What happens when a Prolog does a web server?

    You end up with the PiLLoW framework,
    with nonsense such as html//1 and print_html/1.
    This is the worst "milestone" ever in Prolog.

    https://cliplab.org/Software/pillow/pillow.html

    Bye




    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mild Shock@21:1/5 to Mild Shock on Wed Jul 9 03:31:08 2025
    Hi,

    If I take this DCG miscarriage:

    Implementations conforming to this TS shall
    not define or use a predicate (\+)/3. http://www.complang.tuwien.ac.at/ulrich/iso-prolog/dcgs/dcgsdraft-2023-08-14.pdf

    Possibly the same as here, but who pays
    98 CHF for such a nonsense?

    ISO/IEC TS 13211-3:2025
    https://www.iso.org/standard/83635.html

    I must believe gprolog is not conforming.

    LoL

    Bye

    P.S.: You can check yourself, it fully supports (\+)/3:

    /* GNU Prolog 1.5.0 (64 bits) */
    p --> \+ q, r.
    p --> \+ q.

    And then:

    /* GNU Prolog 1.5.0 (64 bits) */
    ?- listing.
    p(A, B) :-
    \+ q(A, _),
    r(A, B).
    p(A, B) :-
    \+ q(A, _),
    A = B.

    Mild Shock schrieb:
    If you have a suitable Prolog plugin,
    you can do all kind of search,

    Currently the marketplace shows me only one Prolog
    plugin, but it rather adresses gprolog than SWI-Prolog.
    Strange I think there were more. But if plugins don’t

    get maintained they often become incompatible.
    I didn’t try the below yet, seems to be new!

    https://plugins.jetbrains.com/plugin/20982-prologcode

    So only I Prolog tries to tap into a company like
    JetBrains that has profit of at least 200 million USD
    per year, with a growth of 5 - 7% per year.

    Prologers are all communists I guess.

    P.S.: The plugin seems to be from Switzerland.
    But it wasn’t me! PrologCode is a plugin for IntelliJ
    IDEA that provides support for the Prolog language.

    Specifically, it provides:

    Prolog syntax highlighting
    Prolog code completion
    Prolog code folding
    Prolog code navigation

    Three different ways to run a GNU Prolog REPL
    Real-time background syntax checking.

    Initially, this plugin was developed as part of
    a project for the course “Programmation
    logique” at HEIA-FR.

    https://www.heia-fr.ch/

    Mild Shock schrieb:
    Hi,

    Wanna found an IDE business. Well the Editor
    is only the Tip of the Ice Berg. What gives
    you wings like red bull, is this:

    - Instant editing:
       Files don’t really have a modified status,
       they get directly written. Typically the MVC
       is buffer based there. But for instant editing,
       buffers are written when an application switch happens.

    - Local File Content History:
       IntelliJ keeps a local file content history.
       This compensates the dangers of instant editing.
       Instant editing is very useful for tool interaction,
       like interacting with a Prolog system. Through local
       file content history I can view local changes and
       undo them across IDE starts.

    - CVS Integration:
       IntelliJ has CVS integration, like SVN, GIT, etc..
       through their local history. You can freely choose
       what to commit or not. And you can also receive
       changes from a repo.

    - File System Operation Integration:
       Local File Content History and CVS Integration are
       in sync with refactoring. So when I move a file, this
       is a move on the file system. But File Content History
       and CVS don’t get confused by a move. The simply show it
       in their history as well.

    - File Content Index:
       The IDE also maintains a global text index, and
       this text index gets notified by external changes and
       internal changes. They pretty well have it always accurate,
       including file moves, lengthy re-indexing of a whole
       repository happens rarely.

    Mild Shock schrieb:
    Hi,

    The average Prologer in 2025:

    Interview with an Emacs Enthusiast [Colorized]
    https://www.youtube.com/watch?v=urcL86UpqZc

    What happens when a Prolog does a web server?

    You end up with the PiLLoW framework,
    with nonsense such as html//1 and print_html/1.
    This is the worst "milestone" ever in Prolog.

    https://cliplab.org/Software/pillow/pillow.html

    Bye





    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)