liori

@liori@lemm.ee

• ⁨Comment⁩ on ⁨Tool for instantiating a C++ template at runtime?⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  Personally I think child processes are the right approach for this. Launch a new process* for each query and it can (if you choose to go that route) dynamically load in compiled code. Exit when you’re done, and the dynamically loaded code is gone. A side benefit of that is memory leaks are contained, since all memory you allocate is about to be removed anyway.

  I’d probably be fine with hundreds or thousands of these hanging in memory. I suspect the generated code for a single query would be in hundreds of kilobytes, maybe a megabyte. But yeah, this is one of those technical details I’d worry about.

  Honestly, I wonder if you could just use an actual HTTP server for this? They can handle hundreds or even thousands of simultaneous requests. They can handle requests that complete in a fraction of a millisecond or ones that run for several hours. And they have good tools to catch/deal with code that segfaults, hits an endless loop, attempts to allocate terabytes of swap, etc. HTTP also has wonderful tools to load balance across multiple servers if you do need to scale to massive numbers of requests.

  Not sure how a HTTP server would solve the CPU bottleneck of scanning terabytes of data per query?

• ⁨Comment⁩ on ⁨Tool for instantiating a C++ template at runtime?⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  I somehow didn’t think a regular JIT solution might be applicable here, but it is. Thank you! There seems to be a number of projects doing JIT for C++, will look at them.

• Tool for instantiating a C++ template at runtime?
  Submitted ⁨⁨9⁩ ⁨months⁩ ago⁩ to ⁨programming@programming.dev⁩ | ⁨7⁩ ⁨comments⁩
• ⁨Comment⁩ on ⁨Please recommend your cheaper, reliable SSDs 2TB+ (4TB ideal)⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  So far I’ve been following recommendations from this person: old.reddit.com/…/ssd_guides_resources_ssd_help_po…

• C++ Design Patterns for Low-latency Applications Including High-frequency Tradingarxiv.org ↗
  Submitted ⁨⁨1⁩ ⁨year⁩ ago⁩ to ⁨programming@programming.dev⁩ | ⁨0⁩ ⁨comments⁩
• ⁨Comment⁩ on ⁨Linux file system developer: we're severely under-resourced⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Kernel is not a monolithic application, and you cannot develop it like one. There are tons of actors: independent developers, small support companies (like Collabora), corporations, all with different priorities. There is a large number of independent forks (e.g. for obscure devices), that will never be merged, but need to merge e.g. security patches from the mainline. A single project management tool won’t do, not your typical business grade tracking&reporting tool.

  CI is already there. Not a central one—again, distributed across different organizations. Different organizations have different needs for CI, e.g. supporting weird architectures that they need to develop against.

  There is a reason Torvalds created git—existing tools just wouldn’t work. There might be a place for a similar revolution regarding a bugtracker…

• ⁨Comment⁩ on ⁨Linux file system developer: we're severely under-resourced⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  The thread is an attempt to merge a new file system, bcachefs. This is a large change, requiring a lot of review from experienced developers, and getting anyone to do this work turned out to be difficult. Darrick here started talking how, in general, all development of file systems in Linux is troubled by lack of manpower.

• ⁨Comment⁩ on ⁨Linux file system developer: we're severely under-resourced⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I guess the best start would be to have a person to organize volunteers.

• Linux file system developer: we're severely under-resourcedlore.kernel.org ↗
  Submitted ⁨⁨1⁩ ⁨year⁩ ago⁩ to ⁨programming@programming.dev⁩ | ⁨35⁩ ⁨comments⁩
• ⁨Comment⁩ on ⁨Intentionally corrupting LLM training data?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Another idea that just occurred to me. Maybe position: absolute; both the real content and the gibberish content with the same top, left, width, and height attributes so that the real content and the gibberish overlap and occupy the same location on the page. Make sure both the real and gibberish content elements have no background so that remains clear. Put the gibberish content in the DOM before the real content. (I think that will ensure that the gibberish appears behind the real content even without setting the z-index.) And then make JS set the color of the text in the gibberish element the same color as the background so humans can’t see it.

  Be aware that these techniques can affect accessibility for people using screen readers.

• Asynchronous cross-orgizational APIs—any available tooling?
  Submitted ⁨⁨1⁩ ⁨year⁩ ago⁩ to ⁨programming@programming.dev⁩ | ⁨2⁩ ⁨comments⁩