Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.prolog > #14560

Dog Shit: Call my name "jan.ai" (Was: Why do IDEs have Power Save mode?)

From Mild Shock <janburse@fastmail.fm>
Newsgroups comp.lang.prolog
Subject Dog Shit: Call my name "jan.ai" (Was: Why do IDEs have Power Save mode?)
Date 2025-06-17 16:17 +0200
Message-ID <102rtdc$ubej$1@solani.org> (permalink)
References <102ra2b$u1kq$1@solani.org> <102ra6v$u1kq$2@solani.org>

Show all headers | View raw


Hi,

The fukkers stole my name:

Jan - Local AI Assistant
https://github.com/menloresearch/jan

Bye

P.S.: Meanwhile I am struggling with Quantum Paper
whille doing a dark/light CSS. Look my light olive turned dark
olive, that is somewhere near chocolate or is it dog shit?

P.P.S.: Just figured out yesterday that some browser defaults
are more Motif/OSF than Material/Google, aka Quantum Paper.

Mild Shock schrieb:
> 
> The restart maybe explains why IntelliJ has a
> Power Safe mode, but I am not 100% sure about
> the details. But if the end-user behaviour is
> not compatible with the chosen delays, he might
> 
> tear down the tasks again and again. This could
> use compute power. Some incremental tasks or tasks
> that block (i.e. the "lag") could be a solution.
> Incremental tasks that do only small work and
> 
> not big work, are less perceived as blocking
> (i.e. the lag). But a ghost text that maybe
> involves calling an Artificial Intelligence API
> is probably in nature not a small work task,
> 
> in the sense that it would occupy a short work
> time, the Artificial Intelligence API server
> might be busy and cause a task slow down.
> 
> Disclaimer: I am doing some brain writing here...
> 
> Mild Shock schrieb:
>> Somebody wrote:
>>
>>  > noticeable lag waiting for completion candidates
>>
>> A lag wouldn’t be a problem. I guess the problem
>> is that the GUI gets blocked, right? If your GUI
>> has tasks and timers, you could try the follow:
>>
>> - Debouncing Timer: To start ghost after lets
>>    say 1000 ms, the debouncing is to assure that
>>    the ghost appears after the last edit and not
>>    after the first edit.
>>
>> - Abortable Task: The ghost is then computed
>>    asynchronously via a task. But this task is
>>    again tied to the debouncing, means the task
>>    gets aborted if the end-user shows impatience.
>>
>> I checked a couple of GUI tools to do that. Had
>> rather bad experience with Java and OpenJFX, so I
>> am returning back to the JavaScript and WHATWG
>> with my ongoing research.
>>
>> SVG tags were not working out the box
>> https://wiki.openjdk.org/display/OpenJFX/Main
>>
>> No runLater(), any task can any time modify the DOM!
>> https://whatwg.org/
>>
>> But maybe there are other GUI frameworks which
>> can do it. If tasks are also used for highlighting
>> I belive they can be also run asynchronously without
>> explicitly juggling with some queues,
>>
>> just await the asynchrous routine that the task
>> would execute, in a instrumentation loop, and ignore
>> the aborts, since an abort is now good news and not
>> bad news, it only indicates that
>>
>> the end user did an edit and that the task
>> will be restartet.
> 

Back to comp.lang.prolog | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Java and OpenJFX or JavaScript and WHATWG? Mild Shock <janburse@fastmail.fm> - 2025-06-17 10:47 +0200
  Why do IDEs have Power Save mode? (Was: Java and OpenJFX or JavaScript and WHATWG?) Mild Shock <janburse@fastmail.fm> - 2025-06-17 10:49 +0200
    Dog Shit: Call my name "jan.ai" (Was: Why do IDEs have Power Save mode?) Mild Shock <janburse@fastmail.fm> - 2025-06-17 16:17 +0200
      There is no flesh and blood async Prolog! (Was: Dog Shit: Call my name "jan.ai") Mild Shock <janburse@fastmail.fm> - 2025-06-19 14:04 +0200
        When did the Dogelog Player Quantum Leap happen? (Was: There is no flesh and blood async Prolog!) Mild Shock <janburse@fastmail.fm> - 2025-06-19 14:11 +0200
          Main problem with simulated “threads” (Was: When did the Dogelog Player Quantum Leap happen?) Mild Shock <janburse@fastmail.fm> - 2025-06-19 14:26 +0200
            Time Sharing: Martin Richards, Ken Thompson and Linus Torvalds Mild Shock <janburse@fastmail.fm> - 2025-06-19 14:38 +0200
              <parallel> Ant Task doesn't need threads (Was: Time Sharing: Martin Richards, Ken Thompson and Linus Torvalds) Mild Shock <janburse@fastmail.fm> - 2025-06-19 14:54 +0200
          Corr.: wrong date, should read 2021 (Was: When did the Dogelog Player Quantum Leap happen?) Mild Shock <janburse@fastmail.fm> - 2025-06-19 17:47 +0200

csiph-web