Here is a podcast episode were the devs talk about the new profiler: https://creators.spotify.com/pod/profile/corepy/episodes/The...

It's a native build. Only various tools it is shipped with are cygwin builds, like bash etc.

Oh, indeed, but git often calls them.

In Austria you can use a web browser + FIDO key as an alternative. It works nicely. https://ida.gv.at/de/hilfe/hilfe-zu-ida/authentifizierungsfa...

I'm also still using 3.11 for a FastAPI app since 3.12 and 3.13 are quite a bit slower.

On Windows (so libwinpthread), 8C/16T machine:

  $ flac --version
  flac 1.5.0
  $ hyperfine -r5 "flac -f -8 a.wav a.flac" "flac -j16 -f -8 a.wav a.flac"
  Benchmark 1: flac -f -8 a.wav a.flac
    Time (mean ± σ):     13.148 s ±  0.194 s    [User: 12.758 s, System: 0.361 s]
    Range (min … max):   12.934 s … 13.318 s    5 runs

  Benchmark 2: flac -j16 -f -8 a.wav a.flac
    Time (mean ± σ):      2.404 s ±  0.012 s    [User: 14.126 s, System: 1.355 s]
    Range (min … max):    2.395 s …  2.425 s    5 runs

  Summary
    flac -j16 -f -8 a.wav a.flac ran
      5.47 ± 0.09 times faster than flac -f -8 a.wav a.flac

See "Why not use graphs / frequency analysis to compare codecs?" https://wiki.hydrogenaud.io/index.php?title=FAQ#:~:text=Why%...

"I decided that analysis should focus on the higher, more conventional rates – 48k and 44k1" - opus is always 48khz, so that doesn't mean much.

This. Your ears are not an oscilloscope. Lossy audio codecs are designed to exploit two major weaknesses in human hearing:

1. Poor sensitivity in bass and treble. See:

https://en.wikipedia.org/wiki/Equal-loudness_contour

2. Limited ability to hear multiple sounds simultaneously, or almost simultaneously. See:

https://en.wikipedia.org/wiki/Auditory_masking

Bernhard Seeber has some videos on Youtube with demonstrations of auditory masking:

https://www.youtube.com/watch?v=R9UZnMsm9o8

https://www.youtube.com/watch?v=bU0_Kaj7cPk

The only fair way to evaluate lossy codecs is with double blind listening tests.

The problem with these weaknesses is that they are different in each human being. For me listening an mp3 is like a sanding an ear, while some don't even hear the difference between it and a live performance.

> For me listening an mp3 is like a sanding an ear

There is such a broad spectrum in thr word mp3 that you need to be more specific. I can absolutely pick the difference between certian high bitrate mp3 encodings and wav files, however a different mp3 with exactly the same bitrate, effectively indistinguishable.

Bad mp3 encoding is a problem, not one I have experienced recently though. I think the bigger issue is people will rip a music video from youtube, then instead of extracting the existing audio stream into it's own container will reencode it. Mp3->mp3 encoding will be lossy just like any other encoder.

Can you ABX it?

https://abx.digitalfeed.net/lame.320.html

I wonder how many people there are, that don't have these weaknesses.

And who are therefore forced to hear terrible audio because the compression method only considers the majority.

If people have notches in their hearing sensitivity at low or mid frequencies, sounds at those frequencies might fail to mask other sounds as expected. You could simulate this by applying notch filters to otherwise transparent lossy audio and seeing if it exposes compression artifacts. But I think this kind of hearing loss is uncommon. Normal age-related hearing loss does not cause any problems with lossy audio compression.

Discord has "Forum" channels now which are similar to Zulip, with forced "threads" which they call "posts".

Also a disaster on the one server I'm on that uses it.

Agreed, I run a 100+ member discord server for my WoW guild and so far both threads and forums are total dumpster fires that both go unused despite us trying to make them work. Slack's approach to threads is everything I want for Discord; I enjoy talking with my clients more on their Slack workspaces than I do talking with my guild on Discord just because the experience is so dismal on Discord.

I don't see the difference between slack threads and discord threads. Could you elaborate on the differences that make such a difference?

> > After you get through this hurdle you then have to install the right software, and MSYS2 makes the "genius" decision of letting me pick which binary I want to install for every single install. Do you need to install fmpeg? Better spend an hour sifting through clang-amd64-ucrt-mingw32-ffmpeg vs. gcc-x86_64-w32-gnu-ffmpeg and tons of packages.

> Huh. Yeah, that does seem odd - is it a result of MSYS2 being oriented at devs who need compatible libraries?

Yeah, we are oriented at devs that re-package our binaries and also want to be a development environment for upstreams, and also a testbed for toolchains. So we provide x86/x64/arm64, then ucrt/msvcrt, and llvm/gcc. I wouldn't blame anyone for finding this confusing. It's described here: https://www.msys2.org/docs/environments

For ffmpeg, since it was mentioned as an example, this looks like: https://packages.msys2.org/base/mingw-w64-ffmpeg

What happens if you go over the 200GB or 2 Million monthly requests limits?

Can we just put Cloudflare in front? :) joking but half serious actually..

They don't use pinning in their examples: https://cython.readthedocs.io/en/latest/src/userguide/source... and https://cython.readthedocs.io/en/latest/src/userguide/source...

Pinning depends on the requirements you as the consumer have, and the specific package manager (pip, conda, poetry, etc.) so it's hard to give guidance that's helpful when you're a library maintainer. Generally when consuming any dependency you should pin though...