←back to thread

304 points ulrischa | 1 comments | | HN request time: 0.622s | source
Show context
bikeshaving ◴[] No.44686961[source]
This is a exciting use-case for custom elements, and probably how tailwind should have been implemented from the start, but it’s hilariously a paid feature?! (https://tailwindcss.com/plus#pricing) Intuitively, I’d expect the custom elements to be free and the framework integrations to cost money.
replies(4): >>44686977 #>>44687096 #>>44687163 #>>44690620 #
hbn ◴[] No.44687096[source]
Yeah this seems like an odd thing to paywall. In the web dev world where everything is free, it's a pretty crazy ask to ask people to tie themselves to a UI framework where I guess you're forever paying a subscription just to continue using the framework?

It's like putting if postgres expected you to pay them a monthly fee.

edit: I see now their pricing is one-time perpetual access. Still, I'm genuinely curious how well this model works.

replies(2): >>44687112 #>>44687121 #
1. ◴[] No.44687112[source]