‘resilience’ of beter gezegd het gebrek daaraan is een gigaprobleem over de hele linie, waaronder het wereldwijde voedselsysteem. @georgemonbiot.bsky.social schreef daar recent dit artikel over:
www.theguardian.com/commentisfre...
been avoiding uppercase letters for many years already. lazy i hear you say? now it's apparently a sign that i am *not* a lazy human 🙃
> laconic lowercase messaging has one big advantage: it suggests you didn’t entirely outsource the tedious business of communicating with other human beings to ai
delivery van partially submerged in water, roughly in a 30º angle. the print on the van partially obscured ‘30%’ which looks like ‘30º’ 🙃
schematic 30º angle
well done! 30º seems about right 🚐 🌊
(no casualties, so i can make jokes: www.omroepwest.nl/112/5091160/...)
delibreately leaving typos to signal that i'm human. waht a world we live in
heh, vue templates also have whitespace handling gotchas (and nonstandard compiler flags to change but not fix it). the syntax to ensure a regular space ends up in the dom:
{{ " " }}
diplopia ninja eyes? 🥷🏼👀😵💫
that said, i face a wall and a computer screen when i sit on that chair, not a classroom…
yep so do i 🙃 bsky.app/profile/wbol...
håg capisco 8106 reversed https://hag-office.com/products/capisco-8106
you have it backwards 🙃
(tbh i love this håg capisco chair and i have one at home. raise it slightly higher to perch/sit-stand)
bit unfortunate b/c it gets close: it can do 1M for 1000000 (or 1 mln. in nl-NL), and also combo with unit, but not with the desired result 🫤
console.log(new Intl.NumberFormat("en", { style: "unit", unit: "byte", notation: "compact"}).format(123456789))
123M byte
last time i played with it, it seemed there is no facility to combine number formatting with units in a way that produces things like megajoules/MJ, kilobytes/KB based on the numerical value, without specifying the exact unit. (supported units include explicit byte, kilobyte, megabyte, etc.) right?
🙃 i have received mail to ‘boterslee’ (butter 🧈 sleigh 🛷)
thanks! 🙏🏼 fun place indeed (part of larger cultural centre amare.nl). bumped into this jam session unexpectedly… turned out to feature quite a few decent musicians: vocals, bass, drums, trumpet etc!
how it started:
visited a modern dance 🧑🏼🩰 performance tonight, had a wine 🍷 or two afterwards… hey cool i hear live music 🎶 further down the building!
how it ended:
joined the band 🎹 with a singer i met two minutes earlier 😎 (yes i admit those wines did help get me on stage 🙃)
tulpen / tulips / tulipa blauwe druifjes / grape hyacinth / muscari botryoides
🌷
sommige ouwe (toen oud nog met een w geschreven werd 😜) macbooks hadden digitaal geluid in de minijack via analoog/optisch uit dezelfde aansluiting! mini toslink ofzo
ik bedoel tijdens opnemen. van stilte naar luid geluid geeft maar kort overstuurd geluid. ’autogain’ is dat ofzo?
telefoons doen denk ik continu aggressieve aanpassingen van compressor/limiter? mijn telefoon heeft iig geen draaiknop voor ‘gain staging’ 🙃 en toch klinkt het meestal maar heel kort overstuurd bij pieken
eerste link die ik stuurde was niet helemaal wat ik wilde sturen (maar wel gerelateerd). heb het net toch gevonden! over speakers extra hard aanzetten en dan goed oppassen voor beschadigingen: github.com/AsahiLinux/s...
ja, het klinkt beter en ruimtelijker dan zou moeten kunnen, misschien ook missing fundamentals voor illusie van diepere bas? en.wikipedia.org/wiki/Missing...
de dsp is nog veel fancier dan alleen eq, waardoor geluid veel voller klinkt dan eigenlijk zou kunnen met de speakers. dat kan alleen door slimmigheden want anders beschadigen ze (door te veel power). leuke technische details hier: github.com/AsahiLinux/a...
forgot to bring my freshly brewed cup of coffee ☕ from another room to my desk *twice* within 2 minutes. maybe i should get some… oh wait 🤦
nou, laat maar eens zien hoe volleerd je bent dan: qntm.org/files/absurd...
i gave up and just made ‘git psuh’ actually work… (checks notes) 13+ years ago 🙃 github.com/wbolster/dot...
heh, really trying, but i still have no clear idea about what problem you're trying to solve (and i believe i know a thing or two about this topic), but there's a limit to what i can do to dissuade you from writing yet-another-python-package instead of a til 💡 blog post 😜
what does ‘50% strict’ mean? sqla.orm session and postgresql defaults make all transaction boundaries explicitly visible in application code. note that i say boundaries, but it's the *end* (commit/rollback) i care about. the beginning is largely irrelevant (with default ‘read committed’ isolation)
woops, meant to say ‘repeatable read’ and ‘serializable’ as the non-standard transaction isolation levels. ‘read committed’ is in fact the postgresql default (and good enough for many use cases).
at least with postgresql, unless you're using non-standard transaction isolation levels like ‘read committed’ or ‘serializable’, having a transaction open is not an issue (they're typically shortlived b/c request scoped anyway), especially when it's only reading (e.g. only select statements)
you keep saying you want to avoid starting transactions. what makes you afraid/reluctant to start transactions? it's the ending (commit/rollback) that matters. my mental model with sqla.orm is that there's always an active tx (the autobegin that delays the ‘begin’ statement is just an optimisation)
could it be that you're mentally conflating sqla.Session boundaries and db transaction boundaries? by design, one session can span multiple transactions (though one at a time)?
i also don't see why one would want to use ‘autobegin=False’ (which didn't even exist previously!) in the general case
tbh i still really don't get your gripe. seems we want the same (strict control over transactions, no weird db state, no queries at unexpected times) yet i think the sqla orm design with defaults works in my favour while you think it doesn't 🫤
