If an update would lead to unexpected behavior if someone is still working with the expectations from before, and this could lead to issues, then it's a "breaking change"

Semantics are the words and their meanings in the scope of the library that you created, but also how they relate to the rest of the scope. In practice this is mostly about side effects

I think semantic versionings' "major" is related to "breaking changes" and I recently read a really nice way to think of this:
Instead of thinking about breaking or nor, think about the semantics you provide as a library or API, if the semantics change then it warrants a major release aka. breaking

I saw some anecdotal evidence that 🪿 actually downranks posts that have an external link, and also if you mention 🦋
I think it was on @hankgreen.bsky.social YouTube

You could add a UTM or something like that to test it on your next post

Time to try JSR

Changing ones workflow is hard once you get comfortable, and this looks like a big change for me at least. Even though it might objectively be better

That's a great domain for a blog, too bad the owner is not using it

Beowulf

Oh wow, I went to a few but have not been in a few months. This is a good reminder to start going again it was always a lot of fun

At least add a error report to sentry or something like that

That's really cool

Very useful after talking shit

Oh cool, I just saw you are in Vienna! Do you ever go to the react or JS meetup?

When writing SQL, does it only suggest JOIN RIGHT?

It's the jimcrustaition

wow I did not expect it to actually make a piano synthesizer on its first attempt 💀
sage-pavlova-939dbd.netlify.app

its game over when Samwise completely covers the button 😂