Peter Kröner

@sirpepe.bsky.social

Frontend technology trash panda, DevRel @ Storyblok Also @sirpepe@mastodon.social

It's wild how some really basic usability issues with JSX have just not been addressed since I first learned of #React back in the early Stone Age. Even CSS manages to map "gray" to "grey", but class to className? Apparently impossible! Having two expressions instead of one? Even more impossible!

export default function Cats({ blok }) {
  return (
    <h2>Cats</h2>
    <figure class="grid">
      {blok.pictures.map((picture) => (
        <img key={picture.id} src={picture.filename} alt={picture.alt} />
      ))}
    </figure>
  );
}

It's wild how some really basic usability issues with JSX have just not been addressed since I first learned of #React back in the early Stone Age. Even CSS manages to map "gray" to "grey", but class to className? Apparently impossible! Having two expressions instead of one? Even more impossible!

export default function Cats({ blok }) {
  return (
    <h2>Cats</h2>
    <figure class="grid">
      {blok.pictures.map((picture) => (
        <img key={picture.id} src={picture.filename} alt={picture.alt} />
      ))}
    </figure>
  );
}

I submit the following screenshot as my entry to the "shipping embarrassing bugs straight to production" championship. Yep, used the #Elixir language module to parse the #Rustlang example on the Code.Movie home page. For weeks. On the other hand, the parser just sort of dealt with it, so... yay?

The animated demo on the Code.Movie homepage using the Elixir language to render the Rust example.

It is _insane_ how blazing fast a Forgejo instance (hosted by some average guy) is compared to SlopHub. The latter is supposedly powered by the resources of a megacorp and feels like molasses in comparison. I'm at a loss for words.

The sky appears to be eavesdropping on the phone call with my dad, in which an extremely old man from an extremely small town has some extremely correct opinions 🏳️‍⚧️

The sky in trans flag colors

Assuming that true things are indeed true is the best #performance optimization technique. It requires no changes to the architecture, does not result in annoying code golfing, preserves readability, is easy to document, and works across platforms and domains.