Just testing out a #Rug #crate called rug, which seems to give convenient access to libgmp, libmpfr and libmpc.

Understanding #audio and frequency distributions reflects a lot to #quantum gates. Similarly distribution is "the number" and goal is to make distribution to do the job or pursued balance for you by operating it with quantum gates.

Also these new cross-over widgets for The Grid are nice:

Pultec emulations are nice too but not as mandatory for moving forward, as "Pultec curve" is easy to draw with EQ+.

#Bitwig 5.2 is best update since I started because it replaces so many external plugins with stock options:

1. A dedicated clipper called Over (substitutes StandardClip).
2. A glue compressor Compressor+ (substitutes The Glue).
3. A a tilt EQ (substitutes Things Flip EQ).

It is the first version at least where I’m actually able to draft a track without VSTs. Especially lack of proper bus compressors has been an itch when migrating from #Ableton Live.

#MusicProduction #audio

Cool got some response from rust-vmm/vm-memory people, asking to give more details, which I will provide next week.

#Enarx is a kind of hybrid #VMM, and I think this is exactly where I think the overall rust-vmm umbrella has the best opportunities. I.e. instead of just hosting guests with QEMU you might want to do a tailored VMM below to get the optimal characteristics in performance, security and whatnot for your use case.

Enarx hosts #WebAssembly payloads in confidential computing environment. To realize those it:

1. Uses #KVM API to bootstrap wasm run-time inside a #AMD SEV-SNP VM.
2. Uses /dev/sgx to partition address space for boostrapping a wasm run-time inside an #Intel SGX enclave.

The first one is very surgically constructed VM with all access outside it disable, and the second is not actually VM at all.

My take is here that any commercially viable memory API should first of all scale to all possible types on VM’s, and also address stuff “on the edges of universum”, e.g. SGX enclaves, which in many ways resemble VM’s (at least to some level).

#Linux #Rust #rustlang

Oh great #Bitwig 5.2 has stock plugins for PEQ-1 and MEQ-5 #pultec

BREAKING: C++26 will add destructive copy

@ben @vbabka For Fedora I think there was bug already ongoing (maybe even finished). Does OpenSUSE already have one?

@ben Even more importantly for Linux users:

1. Check if the default settings have this turned off in your distribution.
2. Report a bug to your distributions bug database if it is turned by default on.

#firefox #linux #adware

@ben Even more importantly for Linux users:

1. Check if the default settings have this turned off in your distribution.
2. Report a bug to your distributions bug database if it is turned by default on.

#firefox #linux #adware

@RunRichRun for a company whose business is security trainings.

@RunRichRun makes me wonder why this was not obvious from the get go

Security Firm Discovers Remote Worker Is Really a North Korean Hacker —
"The incident occurred at KnowBe4, which develops security awareness programs to teach employees about phishing attacks and cyber threats. The company recently hired a remote software engineer who cleared the interview and background check process. But last week, KnowBe4 uncovered something odd after sending the employee a company-issued Mac." https://www.pcmag.com/news/security-firm-discovers-remote-worker-is-really-a-north-korean-hacker
#Oops

Climate Change Actions Are Far More Popular Than People in U.S. Realize
https://www.scientificamerican.com/article/climate-change-actions-are-far-more-popular-than-people-in-u-s-realize/
“False social reality” obscures widespread U.S. support for climate protection measures

Not just the US, this is a global problem #DontLookUp

@thegibson Irritating welcome screen really nails this site!

Great, #Bitwig 5.2 has a stock #compressor, which I don't proactively hate ;-) I think the previous ones were quite horrible but this does the job (also glues nicely).

@donovanh @exerra @rolle

Modern protocol story goes like this:

1. First a company creates a JSON protocol because it is what everyone else is using.
2. After a while a scalability/bandwidth issue is hit.
3. Someone finds out about protobuf, and it is used as duct tape to address the bad design choice.

If text protocol was designed in the first place from grounds to fit the application, one could realize that it could become an investment.

As long as data is UTF-8 text representation, it is dead easy to convert to some other format (for e.g. protocol bridges) despite not using a standard syntax (JSON, XML). JSON is totally over-rated these days ;-)

https://www.joelonsoftware.com/2001/04/21/dont-let-architecture-astronauts-scare-you/

Found a #Parallax #Propeller 1 #CPU while cleaning up my place ("breadboard" version).

I wonder what I need to do to make that tick and how do you get a VGA adapter for it.

I probably do next a texture mapper for triangles (not a goal just next thing in mind).

I have my 86box setup as Pentium-166 MMX so to take advantage of that I'm also going to do a texture mapper for triangles, which uses texture organized into 8x8 tiles for the sake of efficient L1 usage, and order opcodes in a way that the filler keeps both of the two pipelines busy. Can be extended to perspective correction later on without huge sacrifice in perf as FPU (MMX) can run in parallel with ALUs.

From classic Intel CPU's Pentium is my favorite because it already has a bit of modern parallel and pipeline alike stuff but you can still cope it in your head easily ;-)