tobias

tobias

@moeritz.io

engineer flavored with too many design opinions

284 followers26 following124 posts

tobias
@moeritz.io

PSA: DENIC has had a DNSSEC related outage. Domains with a .de TLD might not be accessible for a while

tobias
@moeritz.io

worlds largest social media company’s oauth implementation tells you your redirect_uri is invalid when your client secret is invalid thanks for wasting my evening facebook

tobias
@moeritz.io

still 50/50 thorn between "tailwind 4 is the perfect evolution" and "i wish they just added oxide to tailwind 3 and called it a day"

View full thread
tobias
@moeritz.io

One thing still missing is being able to set the breakpoints as 'max-width' instead of 'min-width' (in theme.css, works with legacy js config). I want that 'md:' targets all devices below the size, not above. I know you can use 'max-md:' - but I don't want to shift my mental memory after 3 years.

tobias
@moeritz.io

still 50/50 thorn between "tailwind 4 is the perfect evolution" and "i wish they just added oxide to tailwind 3 and called it a day"

View full thread
tobias
@moeritz.io

I was very much happy with Tailwind in the beginning, because *it was opiniated*. I disliked UnoCSS because with the default preset, you could mix Tailwind, Bootstrap and Tachyons styles in the same project. The configuration effort was much larger. Either have I matured and got to know better what

tobias
@moeritz.io

I want or Tailwind just shifted too far away from the origin. This sounds a bit harsh, I still love Tailwind and their wonderful influence on making CSS a bit easier for everyone ❤️

tobias
@moeritz.io

still 50/50 thorn between "tailwind 4 is the perfect evolution" and "i wish they just added oxide to tailwind 3 and called it a day"

View full thread
tobias
@moeritz.io

One thing still missing is being able to set the breakpoints as 'max-width' instead of 'min-width' (in theme.css, works with legacy js config). I want that 'md:' targets all devices below the size, not above. I know you can use 'max-md:' - but I don't want to shift my mental memory after 3 years.

tobias
@moeritz.io

In general, the CSS config format feels more bloaty, less elegant to me - especially the font declaration. For example, I now have to add line-height, letter-spacing & font-weight separately to each font size instead of being able to pass one global object.

tobias
@moeritz.io

still 50/50 thorn between "tailwind 4 is the perfect evolution" and "i wish they just added oxide to tailwind 3 and called it a day"

tobias
@moeritz.io

I dislike that everything is available as CSS variable by default. I don't want any perspective related variables in my project if I don't use the perspective utility class once. If Tailwind can scan for 'text-green-500', surely it should be possible to scan for 'var(--color-green-500)'?

tobias
@moeritz.io

again overthinking my life choices when working with random german xml standards at midnight (at least this one is documented)

tobias
@moeritz.io

does anyone have experience in building a heavily whitelabeled react (remix) app (same logic but lookwise too different to keep it css only, so components will be duplicated with different markup) and has some opinions on organizing this?

tobias
@moeritz.io

basically, I want a <Button /> in my routes that automatically selects the correct whitelabeled button, based on context or so, without creating such a “component wrapper” for every component in the codebase (100+)

tobias
@moeritz.io

i successfully made my window shutter smart so I don't have to stand 5 minutes pressing the button each night to make it go down

tobias
@moeritz.io

weird figma quirks: you cannot scale a text element if you don’t have the font installed but it works inside a group/frame

You are up to date.