It's amusing thinking if I rigged up an electron app for a mixer it would take up more memory than the entire disk+ram.
541 karma · joined December 5, 2018
It's amusing thinking if I rigged up an electron app for a mixer it would take up more memory than the entire disk+ram.
The former has convenient distribution, but worse performance and other limitations.
The latter can be tricky to keep updated, ensure the environment is the same for everyone and/or cross-platform differences, etc., but significantly better/faster.
But both binaries about the same size. Assuming using something like sokol or SDL3.
Would be nice for something at the level of like Claude 3.5
Those numbers sound wild. For various comms systems does this mean several orders of magnitude bandwidth improvement or power reduction?
if ((Π⁻ < Π) && (Π < Π⁺)) {
I spent way too long trying to figure this out as C code instead of if ((Π⁻ < Π) && (Π < Π⁺)) {I'd settle for something markdown-like rather than full-blown html. Basic headings, lists, and inline images are all I want.
maybe streamio + unified remote?
Noted changes with XLibre 25.0 include:
a) Xnamespace extension: a novel approach for isolating clients from different security domains (eg. containers) into separate X11 namespaces, where they can't hurt each other
that seems significant, I wonder why xorg hasn't implemented something like it so far.Go team triangles!
~40y ago invented data warehouse, where an ETL process overnight would collect data from smaller dbs into a central db (the data warehouse)
~15y ago, data lake (i.e. hadoop) emerged to address scaling and other things. Same idea but ELT instead of ETL: less focus on schema, collect the data into S3 and transform it later
https://github.com/systemd/systemd/issues/30239 https://github.com/systemd/systemd/pull/26826/files
systemd-nspawn may be invoked with or without privileges. The full functionality is currently only available when invoked with privileges. When invoked without privileges, various limitations apply, including, but not limited toRIP screen reader users?
or in the other direction, to truly prevent e.g. xorg socket from being accessed by a bubblejailed application, it should exclude --share-net, regardless if you bind the actual path to the socket (since abstract permeates beyond that)