“More music is being released today (in a single day) than was released in the calendar year of 1989,” Page explained.
“More of that music is being done by artists themselves, meaning there’s even more demand for music production software.”
It’s true,
the rise in musicians goes hand-in-hand with the rise of music-making software and music-distributing platforms.
Now that making high-quality recordings is possible from the palm of your hand
— and sharing them i…
'Relaxed' Shedeur Sanders after first NFL win: 'A lot of people want to see me fail ... it ain't gonna happen'
https://www.cbssports.com/nfl…
In der politischen Diskussion bringen manche Politiker*innen das Argument, "da kommt doch noch ein Rollstühl über den Gehweg" als sei das das bereits die Maximalforderung. Aber Gehwege sind so viel mehr als ein Stück schlecht gemeinter Barrierefreiheit. Erstmal sollten sich zwei Menschen in Rollstühlen begegnen und an einander vorbei kommen können und dann sind #Gehwege eben auch Orte zu…
Great app. I've used it for many years. https://indieapps.space/@mp3tag/115756809912174858
I'm building webkit-gtk right now. It's one of these messy packages where a few source files need a lot of memory to compile, and ninja can randomly order jobs so that all of them suddenly start compiling simultaneously. So to keep things going smoothly without OOM-ing, I've been dynamically adjusting the available job count via steve the #jobserver.
While doing that, I've noticed that ninja isn't taking new jobs immediately after I increased the job count. So I've started debugging steve, and couldn't find out anything wrong with it. Finally, I've looked into ninja and realized how lazy their code is.
So, there are two main approaches to acquiring job tokens. Either you do blocking reads, and therefore wait for a token to become available, or you use polling to get noticed when it becomes available. Ninja instead does non-blocking reads, and if there are no more tokens available… it waits till one of its own jobs finish.
This roughly means that as other processes release tokens, ninja won't take them until one of its own jobs finish. And if ninja didn't manage to acquire any job tokens to begin with, it is just running a single process via implicit slot, and that process finishing provides it with the only chance to acquire additional tokens. So realistically speaking, as long as there are other build jobs running in parallel, ninja is going to need to be incredibly lucky to ever get a job token, since all other processes will grab the available tokens immediately.
This isn't something that steve can fix.
#Gentoo #NinjaBuild
Optical Ocean Recipes: Creating Realistic Datasets to Facilitate Underwater Vision Research
Patricia Sch\"ontag, David Nakath, Judith Fischer, R\"udiger R\"ottgers, Kevin K\"oser
https://arxiv.org/abs/2509.20171
Dynamical correlation effects in twisted bilayer graphene under strain and lattice relaxation
Lorenzo Crippa, Gautam Rai, Dumitru C\u{a}lug\u{a}ru, Haoyu Hu, Jonah Herzog-Arbeitman, B. Andrei Bernevig, Roser Valent\'i, Giorgio Sangiovanni, Tim Wehling
https://arxiv.org/abs/2509.19436
dnc: DNC emails (2016)
A network representing the exchange of emails among members of the Democratic National Committee, in the email data leak released by WikiLeaks in 2016.
This network has 2029 nodes and 12085 edges.
Tags: Social, Communication, Unweighted, Multigraph
https://networks.skewed.de/net/dnc
dnc: DNC emails (2016)
A network representing the exchange of emails among members of the Democratic National Committee, in the email data leak released by WikiLeaks in 2016.
This network has 2029 nodes and 12085 edges.
Tags: Social, Communication, Unweighted, Multigraph
https://networks.skewed.de/net/dnc