Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
c.im is one of the many independent Mastodon servers you can use to participate in the fediverse.
C.IM is a general, mainly English-speaking Mastodon instance.

Administered by:

Server stats:

2.9K
active users

c.im: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.6

#tailwind

2 posts2 participants0 posts today
Replied in thread
Public *
stateful being

@redscroll

instead, what do people do these days? they do #tailwind, as an improvement to styled #react components - both of which strike me as completely ass-backwards workarounds.

and that's exactly the kind of thing we get for not resisting: the entrenchment of suboptimal architectures!

seems to be a common theme in the history of the means of production, and hardly ever gets resolved in a nice and polite way. instead, revolutions happen, heads fly... then everyone forgets.

@mcc

Continued thread
Public *
sb arms & legs

Thinking about the wasteful nature of #LLMs got me thinking about waste in my own development. While it can be convenient to use the large, enterprise-grade frameworks to deliver a minimalist website in 2025 - it's absurd.

Do I really need #laravel with #react, #jquery, #tailwind, #webFonts, #postgres to host some simple #markdown?

Do I need to re-render a bunch of static content at every hit? Does every simple article require 64 connections to the server to display?

I think not.

I want my material to be available to anyone who wants it - regardless of the device they are using or the robustness of their connection.

I want to respect users who disable #javascript for their personal protection.

I want to respect #ScreenReaders and users of assistive technology, without unnecessary complexity.

Everything we need is built into the HTML and CSS specs.

Public
Nicd

My first time trying Tailwind today (with Lustre). I was able to whip out a pretty decent UI with much less work than usual, though my "usual" is from scratch. Tailwind seems to have pretty sensible defaults, but it sure takes time to find out all the class names since they're kind of arbitrarily named. I'm quite happy with this from the hands of a terrible designer.

All in all, I might just continue using it for my small personal projects. So far it has been fun.

#Tailwind#CSS#Lustre
Public
lemon 🍉

Sometimes I really hate my brain and the shit it gets hardstuck on. :clownppuccin:

Me: just playing around with a couple ideas on how to present the upcoming @catppuccin port for Tailwind V4 and built a silly little calendar UI.

Brain: But what if it actually worked? ✨

Me: *spends the next couple hours figuring out how to build a working calendar in JS*

May I present: Probably the most over-engineered demo component I've ever build.

#webdev#css#tailwind
Public
GENKI

#Tailwind は設定周りを #CSS 関数化して大分 JS から #CSS 的なアプローチに変わった感があるけど、CSS 変数はそういう設定周りだけじゃなくてスタイリングの定義にガツガツ使ってはじめて効果が実感できるみたいな感覚もあり、「そこまで CSS 的なアプローチするならそもそも Tailwind 使わなくてよくない？」という気持ちがある。scoped なスタイル書く方法は色々あるわけだし、特に色周りなんかはカラーパレットを段階的に用意するのはもうナンセンスというか、主だった元カラーだけを用意して末端のスタイルでそれらを color-mix() とか color() とかで合成するほうが理にかなってる気がしてきている

Public
Mike :nixos:

Any #WebDev out there have an HTML block editor / page builder, they like?

I've hacked something together with #vuejs and #tinymce but it's cumbersome and janky, and think its time to cut my losses.

But I don't know what to go to. I'm in #php now, but will be rebuilding in #elixir very soon, so if there is something in Elixir / #phoenix that's decent off the shelf, i'd be curious to see that.

#tailwind css support for this would be extra cool.

Public
James Basoo

#Tailwind v4 removing the ability to disable core plugins is quite a subtly hostile change. It was previously possible to use the utilities in an opt-in fashion to strictly control the output and prevent clashes with existing #CSS but now it's all or nothing.

Public
Andreas Sander

Just upgraded my #blog

- #nextjs v15 (nextjs.org/docs/app/building-y)

- #tailwind v4
(tailwindcss.com/docs/upgrade-g)

A huge round of applause for those that wrote the #upgrade tools. I never had a more seamless process of upgrading although my blog has a very small codebase, but still I literally just had to run two `npm/npx` commands that updated my codebase.

👏 Pretty cool!

nextjs.orgUpgrading: Version 15 | Next.jsUpgrade your Next.js Application from Version 14 to 15.
ExploreLive feeds
About