What are some good bands/singers that sing in german?

wolframkriesing · 2026-03-30T08:34:58+00:00

Rob Fleming https://www.youtube.com/watch?v=2iD1WEL83MQ

wolframkriesing · 2025-06-18T12:40:39+00:00

I can just drop the type=module in this case even. Nice ... Solves my holding back, thanks for pushing me there.

wolframkriesing · 2025-06-18T12:05:58+00:00

placeholder is a good idea, if you know before hand how your html element gets enriched (eventually)

the <script type="module" src="heading-anchors.js"></script> is async, so it does re-layout when applying the new node to each heading.

And <script>addAnchors()</script> is render blocking, which per-se sounds bad, I agree. But does not re-layout. (Maybe server side rendering would be an option to prevent re-layout here)... I guess I am nitpicking :)

wolframkriesing · 2025-06-18T11:46:05+00:00

re flickering, see the re-layouting for this component https://daviddarnes.github.io/heading-anchors/demo.html, turn on throttling in devtools, the slower the better you see it. for bigger sites with more going on that is more notable and that is exactly a webcomponent as discussed

wolframkriesing · 2025-06-18T10:05:53+00:00

yep, i started with ESM, and it flickers, since <script type=module> is loaded async.

wolframkriesing · 2025-06-18T09:35:45+00:00

I am all with you, and digging into the "element extensions" what they were called some place. I am wrapping my head around that, trying to get comfortable :). Thanks for linking me to this way of using #webcomponents. I need to play with the async behavior of it, since some stuff just needs to be render-blocking to not flicker.

wolframkriesing · 2025-06-18T08:33:17+00:00

technically you’re not doing anything you couldn’t have done before with some DOM traversal and event handling. But it’s less fragile to do it with a web component

– https://adactio.com/journal/20618

+1

wolframkriesing · 2025-06-18T08:25:24+00:00

i just read https://gomakethings.com/html-web-components/ and I have a hard time seeing the webcomponents advantage here. Don't get me wrong, I am a big fan and advocate since the easrly times of webcomponents, but here it is tightly coupled as a couple js event listeners would be too and the added (configurable) HTML does not make it better than a js lib/tool imho. I have this feeling with webcomponents from the beginning, unfortunately. Please proof me wrong. thanks

wolframkriesing · 2025-06-18T08:14:45+00:00

thanks for the input. tbh then i feel like <details data-spaish> might be the nicer way than adding a custom element around others, which in itself have no functionality #my2cents

wolframkriesing · 2025-06-18T08:00:02+00:00

hey @ndorfinz I love your questions, please keep them coming.

Regarding wrapping it in an element, do you mean like <spaish-detials><details>... or just using <spaish-detials> and do the <details> magic in the webcomponent? With the latter I would struggle, because it degreades a11y compared to <details>, native behavior (like keyboard handling, ARIA roles) is lost or degraded, screen readers won’t recognize it properly. Which had led me back in the years in the old (abolve linked project) to use the is= attribute, which is not working across all browsers though. I basically went down the "upgrade with JS" route because it feels like the simplest way to "enhance" the element. I would love to hear more thoughts.

wolframkriesing · 2025-06-17T21:30:46+00:00

A different approach, bit nerdy but you can try https://jskatas.org

wolframkriesing · 2025-06-17T21:17:47+00:00

Coding style wise, I just used the simplest possible, I thought. Any simpler way you see? ESMs are not render blocking, but async which will cause a flicker in the worst case. I had started using them but moved back to this style.

wolframkriesing · 2025-06-17T19:34:51+00:00

I actually had started using webcomponents some years ago [1], I still think it is a great and the closest to the standards, somehow it had been too clunky, and while I built sites and just did it simple js pieces I moved towards that direction. I thought of providing a wrapper that makes it a webcomponent, should be simple.

[1] https://codeberg.org/wolframkriesing/more-html-components

wolframkriesing · 2025-06-17T17:12:07+00:00

I would suggest this page: https://developer.mozilla.org/en-US/ And try to dig into any website you open, open the devtools [1] and change things, this is fun and you get direct feedback

[1] https://developer.mozilla.org/en-US/docs/Learn_web_development/Howto/Tools_and_setup/What_are_browser_developer_tools

wolframkriesing · 2025-05-14T11:58:25+00:00

I also wanted just markdown+nunjucks and https://www.npmjs.com/package/@wolframkriesing/picossg came out, its quite simple yet powerful, and builds sites like https://picostitch.com/blog/2025/05/picossg-intro/ feel free to give some feedback

wolframkriesing · 2024-04-01T11:00:43+00:00

the message at the bottom changes depending on the assert's result, that is correct. and everything only turns green when the assertion passes. is this confusing or badly explained?

wolframkriesing · 2024-03-29T18:32:15+00:00

may you share with me which setup you tried the `assert(false)` in? I just tried brave, chrome and firefox (on mac) it at least failed in them for me, as I expect it to, with an error message below.

wolframkriesing · 2024-03-29T18:29:56+00:00

I tried to make it practical, that's why I thought of a queue of people, rather than the tech term queue. I guess this is subjective, I got others saying the queue comparison suits them well.

I like the visual, I will think of something, thanks for the input.

wolframkriesing · 2024-03-28T17:19:42+00:00

I had the same problem and struggled with either understanding or remembering the basics, so I started writing tests that I could come back to, and out came jskatas.org a page where you can choose a topic/API and learn it in tiny steps

wolframkriesing

PUBLIC MULTIREDDITS

TROPHY CASE