Microsoft Active Career Copilot 365 ONE, thankyouverymuch.

Grow your .NET-work!

It took quite a bit of scrolling until I found my old faves of dexed and zynaddsubfx, and I didn't see Helm (https://tytel.org/helm/) at all.

I submitted a suggestion to add the sophisticated multi-engine FOSS soft synth that I use, Yoshimi (https://yoshimi.sourceforge.io/) which is a linux only fork of ZynAddSubFX.

Helm has been replaced in practice by Vital (same author), I think.

They are completely different synths.

Vital is a wave table synth; Helm is a subtractive synth.

Helm was the first synthesizer that I really excelled with. I would recommend anyone who wants to actually learn the fundamentals of synthesis, to start on it. Once you get good at to it, it's faster to dial in the exact sound you want than to reach for a preset.

It's far more straightforward and less complicated than additive (ZynAddSubFX), FM, or wave table synths.

That being said, if you just want a very advanced synth with a lot of great presets, Vital is far more advanced.

Surge XT is also at the bottom of the list.

None of the big browsers can be trusted at this point. Firefox is at best the least worst out of the big cross platform browsers.

Apple nearly didn't survive until they bought a company that made an OS that didn't work that way.

MS Word had to be rewritten from ~scratch to get rid of a document losing crash. Yes, we survived, but at what cost?

No, you cannot. Our abstract language abilities (especially the written word part) are a very thin layer on top of hundreds of millions of years of evolution in an information dense environment.

Not it isn't most animals also have a language and humans do way more things differently, than just speak.

> most animals also have a language

Bruh

Only if you are doing in-place updates. If append-only datastores are your jam, writes via mmap are Just Fine:

  $ go test -v
  === RUN   TestChunkOps
      chunk_test.go:26: Checking basic persistence and Store expansion.
      chunk_test.go:74: Checking close and reopen read-only
      chunk_test.go:106: Checking that readonly blocks write ops
      chunk_test.go:116: Checking Clear
      chunk_test.go:175: Checking interrupted write
  --- PASS: TestChunkOps (0.06s)
  === RUN   TestEncWriteSpeed
      chunk_test.go:246: Wrote 1443 MB/s
      chunk_test.go:264: Read 5525.418751 MB/s
  --- PASS: TestEncWriteSpeed (1.42s)
  === RUN   TestPlaintextWriteSpeed
      chunk_test.go:301: Wrote 1693 MB/s
      chunk_test.go:319: Read 10528.744206 MB/s
  --- PASS: TestPlaintextWriteSpeed (1.36s)
  PASS

Before it was an ACID compliant database, it was also the fastest backup solution on the market: https://bofh.bjash.com/bofh/bofh1.html

It isn't even really that -- most CLI tools are single-threaded and have a short lifespan, so your memory allocation strategy can be as simple as allocating what you need as you go along and then letting program termination clean it up.

"I came up with a step-by-step plan to achieve World Peace, and now I am on a government watchlist!"

That sort of thing is why I wrote my own DHCPv4 server that is directly integrated with the core product at $DAYJOB. 10 years ago. Having the DHCP server determine how to handle PXE requests straight from the machine database made my life so much simpler.