Mastodon Feed: Posts

Mastodon Feed

dysfun@treehouse.systems ("gaytabase") wrote:

spin loops are everywhere in real concurrency code. usually around locks, but not just. and we just do it like we're never going to get swapped out for literally milliseconds.

to me, part of the promise of async was that we could get away from all this locking and the associated spinning. but when you go look at e.g. rust async, async primitives that need to lock are just spinning forever and hoping that the slow case won't be too slow.

i can't really do anything to make the slow case faster, but i can just not burn cpu for a few milliseconds by filling it with other work.

Mastodon Feed

db@social.lol ("David Bushell 🪿") wrote:

all I want is to bundle CSS @imports :(

how do I stop Astro (or whatever dependency hell is at fault) from messing with my styles? browser list target is seemingly ignored

(yes I know I brought this upon myself)

https://github.com/parcel-bundler/lightningcss/issues/1283

Mastodon Feed

dysfun@treehouse.systems ("gaytabase") wrote:

for example, i use a slightly racy queue, because it's so much faster on average. the downside is i have to detect the race and handle it. and i calculated that it's going to happen about 0.1-0.2% of the time. sure, that is absolutely a tiny fraction of the time and you'll probably make it back on all the other executions, but on the other hand, a small percentage are destined to wait a really long time (up to milliseconds!). and we just spinloop through this usually!

Mastodon Feed

dysfun@treehouse.systems ("gaytabase") wrote:

so fun thing, but computers are so fast that 'rare' happens all the damn time.

Mastodon Feed

dysfun@treehouse.systems ("gaytabase") wrote:

oh i'm mistaken, it's the window cleaner

Mastodon Feed

brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary: -> EMF 2026") wrote:

Anyway today my plan is to:

  • Pack for EMF
  • Buy supplies (including a T-Shirt I want to have a go at resizing and tinfoil for keeping the Sun out)
  • I read a thing this morning about how you work out thoughts by writing about them and I realise I haven't done much writing in a while. Probably sitting around waiting for inspiration isn't helping. So I want to break that writer's block
Mastodon Feed

brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary: -> EMF 2026") wrote:

Do we want another Post Office scandal? Because this is how we get another Post Office scandal.

https://pivot-to-ai.com/2026/07/14/uk-police-will-run-evidence-through-the-ai-its-quicker/

Mastodon Feed

dysfun@treehouse.systems ("gaytabase") wrote:

bellend neighbour has a radio on their balcony playing adverts and shitty music at me

Mastodon Feed

dysfun@treehouse.systems ("gaytabase") wrote:

and yes of course it has some unique features like the ability to yield instead of spin if it gets held up at the wrong moment.

Mastodon Feed

Boosted by brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary: -> EMF 2026"):
lcamtuf@infosec.exchange ("lcamtuf :verified: :verified: :verified:") wrote:

I’m excited to share the latest prediction for my blog’s subscriber growth. We’re nearing recursive self-subscribement

Mastodon Feed

Boosted by brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary: -> EMF 2026"):
eniko@mastodon.gamedev.place ("Eniko Fox") wrote:

i bet it'd be really fun to make a video game

Mastodon Feed

dysfun@treehouse.systems ("gaytabase") wrote:

it's mostly written in c, with some amd64 assembly in its own actual .s file. it supports precisely one architecture so far of course. i probably will get around to that, but not today.

the reason for pulling it out is i realised that async + async i/o is actually a really common thing people want for a variety of purposes and it'll probably wind up better than existing solutions to the problem available in C space.

Mastodon Feed

dysfun@treehouse.systems ("gaytabase") wrote:

right, i've pulled gnt (green threads and tonic) out of keysmash and made it its own library. suppose i'd better finish it up now.

Mastodon Feed

Boosted by brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary: -> EMF 2026"):
suricrasia@lethargic.talkative.fish ("blackle mori") wrote:

or any anti-ai 88x31s really

Mastodon Feed

jonny@neuromatch.social ("jonny (nonvenomous)") wrote:

I need to search up whoever came up with and gave me the idea of "n-umbra" to describe the neighborhood of nodes n-away

Mastodon Feed

jonny@neuromatch.social ("jonny (nonvenomous)") wrote:

I don't know if there's an actual graph term for "the amount of things per thing" so I went with cardinality but if there's a real term and it doesn't suck hmu

Mastodon Feed

Boosted by brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary: -> EMF 2026"):
emma@orbital.horse ("ƒ: 🪿️→ ℝ") wrote:

Hey, I do more than complain about AI and centrists. Like this Blåhaj rocket (38mm motors) I built over the last couple of weeks.

#Rocketry #Blåhaj #TransPride

A smiling white woman with grey hair and glasses holding up a stubby, four fin model rocket decorated like a Blåhaj
A smiling white woman with glasses holding a model rocket, decorated like a Blåhaj, like a small child

Mastodon Feed

Boosted by brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary: -> EMF 2026"):
dumpsterqueer@superseriousbusiness.org ("tobi is writing bugs :terminal_cursor:") wrote:

@kim's massive chore PR to remove #GoToSocial's dependency on Gin got squerged a while ago: https://codeberg.org/superseriousbusiness/gotosocial/pulls/4847

Gin was useful for a while when GtS was in its infancy cuz Go didn't have decent http routing stuff in the standard library back then. But now it does! And not only that, but Gin started accepting LLM contributions recently, so it clearly had to go 🤢

We'll keep monitoring + trying to remove dependencies on "ai"-happy code as we go along; and, as always, we will continue to forbid any LLM-based contributions to GtS itself, because ew, ick, yikes, gross.

Happy slothin'

Mastodon Feed

Boosted by brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary: -> EMF 2026"):
boredzo ("Peter Hosey") wrote:

Convenient as online distribution is, I miss when Mastodon was distributed on physical discs.

A stack of CD albums on display at Amoeba Records. The albums are by Mastodon (the band, not the social network).

Mastodon Feed

jonny@neuromatch.social ("jonny (nonvenomous)") wrote:

Its pitiful how they had to make a whole special-cased system for handling streaming token output along with batched message output where we get it for free by virtue of actually having a good graph model that can handle cardinality expansion and contraction

Mastodon Feed

jonny@neuromatch.social ("jonny (nonvenomous)") wrote:

RE: https://neuromatch.social/@jonny/116922572094121715

If I had no morals this could be the thing I cash out and made my millions on by rebranding it for "AI". Noob is like one billion times better than langchain/langgraph on pretty much every point

Mastodon Feed

Boosted by slightlyoff@toot.cafe ("Alex Russell"):
anatudor ("Ana Tudor 🐯") wrote:

A self-styling `style` element - makes itself visible & styles itself to look like code printed on an alternating line background with lateral perforations (real transparency allows to see through holes to the backdrop) https://codepen.io/thebabydino/pen/wBBLJrz?editors=1000

If you're looking for original code boxes...🐱

#CSS

Screenshot of some of the code in the styled style from the linked demo.

Mastodon Feed

Boosted by neatnik@social.lol ("Neatnik"):
soulexpress@musician.social ("Dean F.") wrote:

@markwyner I have barely a fraction of Rowling's wealth, but am willing to bet that I'm 1000 times happier than she'll ever be.

Mastodon Feed

jonny@neuromatch.social ("jonny (nonvenomous)") wrote:

Gonna see if I can move the event store to rust so I can do post-run copying out of the GIL so we can do full on time travel too

Mastodon Feed

Boosted by neatnik@social.lol ("Neatnik"):
compfu@mograph.social ("Stefan Ihringer") wrote:

The city of #Munich is admitting that our water supply is running low. We're famous for our good drinking water which is fed by aquifers from an alpine region to the south. But that region's glaciers have been melting for a while and there's less and less snow in winter.
For the next couple of weeks there's a total ban on watering your lawn, washing your car outside of commercial car washes (don't ask, this is Germany, apparently this is still a thing), etc...

#ClimateDiary #ClimateCrisis

Mastodon Feed

jonny@neuromatch.social ("jonny (nonvenomous)") wrote:

so our graph processing lib has something like 30 microseconds of overhead per call, about a quarter of that can be trivially trimmed, and another quarter can be written out. and that's without using any of the yno graph parts whose whole purpose is to make it easy to run graphs of operations p close to optimally concurrent. So its looking sorta sweet I think

Mastodon Feed

Boosted by neatnik@social.lol ("Neatnik"):
nileane@nileane.fr ("Niléane") wrote:

“The kids are alright”, the adults kept saying with their hands wrapped around their children’s necks right up until they couldn’t breathe

(re: social media bans, return of fascism worldwide, global warming well past the point of no return, end of universal healthcare, inflation, …)

Mastodon Feed

neatnik@social.lol ("Neatnik") wrote:

So. Anyway. Guess it’s time for another Halt and Catch Fire rewatch.

Mastodon Feed

neatnik@social.lol ("Neatnik") wrote:

I used all four of those services at various points, as well as The Sierra Network (and GEnie, briefly). And so many BBSes! Each was fun and special in its own way, but they all shared that common thread of purpose-driven usage tied to sessions with a distinct beginning and end.

We’ll never go back to that, given that the internet is now in our pockets and strapped to our wrists. But it’s interesting to think about the way we changed how we spend time online, and how that in turn changed us.

Mastodon Feed

jonny@neuromatch.social ("jonny (nonvenomous)") wrote:

cool. sweet. nice. sold on this whole rust business.

[codspeed benchmarking comment saying that one PR that rewrites some of the core logic in rust will increase performance across our benchmarks by 37%. each of the tests are a processing graph run in different ways - a synchronous runner just calls the graph... synchronously.. in order, and a ZMQ runner is a multiprocess runner that runs each node concurrently, swapping events over zeromq. i figure the details are probably not important to anyone but me, but if you are curious about the actual numbers in the table, HTML is probably easier for screenreaders and tables than i can render here, so that's over here: https://github.com/miniscope/noob/pull/243#issuecomment-4977387758 ]
[benchmarks that i ran locally on just the part that was swapped out - regular graphs are scheduled 4-5x faster than before, and large graphs are more like 10x]