slopfront
Reddit, read-only. No JavaScript. No cookies. No tracking.
preferences

Solutions Looking for Problems

0 points · submitted Sep 2024 by u/jack_waugh

Here's a list of bugs I have been working on that I have mentally treated as features; maybe I'm mentally ill or have a personality disorder that leads me to such erroneous behavior. But if any of you think any of these things are features, I can show code for them.

  • arbitrary namespaces for importing functions, classes, other artifacts that modules export, without citing the module.
  • concurrency via traditional process concept with fork, de-emphasizing promises;
  • priority scheduling without using web workers;
  • ability to abandon execution of behaviors or calculations involving deep calling trees and multiple processes (not web workers).

3 comments · 50% upvoted · other discussions

comments

guest271314 2 points · Sep 2024
  • arbitrary namespaces for importing functions, classes, other artifacts that modules export, without citing the module.

WICG Import Maps.

concurrency via traditional process concept with fork, de-emphasizing promises;

Worker(s). Atomics. SharedArrayBuffer. WebAssembly.Memeory. Though this is tricky without using asynchronous API's that were designed to handle concurrency. You can try exploiting process of AudioWorkletProcessor.

  • priority scheduling without using web workers;

Prioritized Task Scheduling API, i.e., scheduler.postTask(fn, {...options})

  • ability to abandon execution of behaviors or calculations involving deep calling trees and multiple processes (not web workers).

Perhaps generators.

jack_waugh [OP] 1 points · Sep 2024

Perhaps generators.

Yes, my techniques rely on generator functions. They are combined with a concurrency kernel and an abortable scheduler.

(I wish for a better term than "abort", because the etymology of it is denying an origination. This makes sense for a pure calculation, but not for an overt behavior.)

jack_waugh [OP] 1 points · Sep 2024

Though this is tricky without using asynchronous API's that were designed to handle concurrency.

My technique also requires that.