Today I'm researching better workflows to backup databases, and create sanitised copies for local development.
I'm not able to find a great deal of informative discussion around best practice.
Is this stuff more obvious than I think - or is it so under-the-radar-unsexy that industry practice is just not very good?
Little @codepen demo: stacked avatars https://codepen.io/thebabydino/pen/ogNQryV
Dew Drop – April 1, 2025 (#4394)
https://www.alvinashcraft.com/2025/04/01/dew-drop-april-1-2025-4394/
new article alert
In the ninth article in my design tokens workflow series we look at –
Implementing Multi-Brand Theming with Style Dictionary
https://www.alwaystwisted.com/articles/a-design-tokens-workflow-part-9
God I fucking hate working with other libraries. I hate it so much. This is by far the worst part of this job. Diving into unmaintained discords, arrogant github communities, just waiting until someone barfs out "CAN YOU PROVIDE A REPL PLS", understandable but nasty, before even attempting to understand the issue. I dive and dive into docs and posts and youtube videos and ultimately I just cannot find what I look for, spend 20 hours on just browsing the web and end up making it myself #webdev
SVGFEMorphologyElement: result property
Widely available (from Jul 2015)
https://developer.mozilla.org/en-US/docs/Web/API/SVGFEMorphologyElement/result
The result read-only property of the SVGFEMorphologyElement interface describes the assigned name of an SVG filter primitive as a SVGAnimatedString.
Here's a gradient background version on @codepen too https://codepen.io/thebabydino/pen/KwKrJGp
Shape depends on how the text content naturally wraps.
Hey web devs,
I'm trying out Svelte 5 coming from React and I'm probably doing something wrong.
My simple test component ends up being 7kb so I think I'm doing something wrong, but I can't figure what it is.
Is this normal?
Here's the code:
https://github.com/sveltejs/svelte/discussions/11214#discussioncomment-12685623
Anyone know of a good Schedular in #NodeJS? Trying to move away from agenda (https://github.com/agenda/agenda) as it's not been updated in years, and we want to use Postgres as our backing store.
Any suggestions?
#Development #Launches
Toon Titles · Cartoon titles brought to life with CSS, SVG, and SMIL https://ilo.im/1632jj
_____
#Collection #Cartoons #Animations #Design #WebDesign #WebDev #Frontend #SMIL #SVG #CSS
From: blenderdumbass . org
I want to document the way you might have a possibility to use the same software to make a similar website. @Madiator2011 already done that with blog.madiator.com. Lets go over: where you get the code, how do you set it up, how do you publish, how do you manage accounts, and most importantly, how do you modify everything, so it will look like your own thing.
Read or listen: https://blenderdumbass.org/articles/how_to_make_a_blog_like_mine_using_bdserver_software_
To fix this, we give the assembly a tiny blur.
We don't want blurry edges
either, so we push some of the semitransparent edge pixels to either 0 or 1, whichever is closer. To do so, we use another `feComponentTransfer` and map the [0, 1] alpha interval to [-2, 3]. Basically we're stretching the alpha interval to be 5 times bigger, keeping same midpoint (.5), then it's clamped to [0, 1].
`feComponentTransfer` allows us to manipulate individual RGBA channels. In this case just the alpha (via `feFuncA`) by making all assembly pixels whose alpha is below `.5` fully transparent (alpha = 0). And all other pixels fully opaque (alpha = 1).
This makes edges jagged. 
Maybe not so noticeable in some cases, but it often won't cut it.
Anonymous event planning with friends (whos-in.com)
Discussions: https://discu.eu/q/https://www.whos-in.com
How the assembly alpha is computed is something I've detailed in 
https://css-tricks.com/adventures-in-css-semi-transparency-land/
Keep in mind that where we have overlap, two corresponding pixels from the two layers may both have an alpha below .5, but their overlap can still give the assembly an alpha above .5!
For example:
.4 + .3 - .4*.3 = .7 - .12 = .58
Both .4 and .3 are smaller than .5, but the overlap alpha .58 is bigger than .5!
As you can see in the recording 
blurring makes the pixels around the edges semitransparent. The bigger the blur radius, the more pixels become transparent.
When the particles get closer, their semitransparent areas overlap. This increases the assembly alpha there.
A little spinner I made years ago on @codepen but never shared publicly https://codepen.io/thebabydino/pen/OJQKbKW
Hotfix v4.7 was just published.
This hotfix completes the transition from CDN FontAwesome usage to Selfhosted usage.
https://github.com/danielbrendel/hortusfox-web/releases/tag/v4.7
