It almost makes me suspicious. With the way APIs are going (reddit/Twitter) and the Rust Foundation drama and Vercel dominating the TS/JS/node ecosystem, I'm wondering how long can this last? At what point do they pull the rug out from under us and say, you need a license for this now.
@@MobiusCoin I'm no expert in this, barely even 20, but I reckon that once they find it economically infeasible to distribute it for free or that they'd like more profits, they would probably migrate to a licensed model. They have a large enough user base where it's likely that companies would happily pay for it. It's also a possibility that they will offer it to startups, etc., whose revenue are within a certain threshold, for free. But all of it is just speculation on my part backed by no evidence. It's entirely possible that they continue they way they are now.
@@MobiusCoinIt's a.utility class css framework, nothing complex, you live i' a word where GNU/Linux is free, your favorite languages, compilers, frameworks or whatever are free, it's literally nothing complexity wise compared to those
@@terrencemurray-7628 it has already been released under an open source license and this code can't be retroactively relicensed, their money making business is Tailwind UI. I don't know if you guys are devs or designers but if you're devs you should know this is just a simple post CSS powered library that would easily be maintained by tons of potential people since you can't retroactively change the license of already released code, we aren't talking about a kernel here, the complexity isn't that deep. I think you're all overestimating what it is, if tomorrow it became close source it'd just be forked and everyone would migrate to the new fork since nobody would want to rely on a close source library for styling, and not just because of money, first because it'd be risky, what if they went out of business ? Secondly because you wouldn't want to lock yourself for something that "simple", some companies could literally come up with a tailwind clone from " scratch" by themselves in no time. The concern tho is real for complex projects, what if React went close source ? It'd immediately be forked but how well would if be maintained and how well could those maintainers continue to develop the project ? Would enough people donate to it ?
nothing but love for the tailwind team and the extended community - you both revolutionised styling and allowed me to go from struggling with maintanance to getting creative with ease. I salute you, and am excited for what else is in store! Thank you from the bottom of my heart
@@electrolyteorb I suspect you're saying that because you lack to the skills to actually do it. Entertains me to no end the number of programmers who still don't know how to style.
Same for me with programming user interfaces, I was unable to understand coding the traditional way until I came across React.js where I have my logic and use it in the template in the same files directly, then it clicked instantly! We all need that visual part not to be separated and far away.
What he said is actually really informative, about fluid text sizing for mobile, dark mode, and the upcoming tailwindcss features with oxide and catalyst for react
Steve is so smart when it comes to design. Dude is literally a genius. By far one of the best designers on the web right now. Hearing him talk about his decisions is awesome.
The greatest thing about Tailwind for me as a beginner was I didn't have to discover what were the best ways to achieve some things, Tailwind had already done the hard task of figuring out browser compatibility issues and on top the most amazing tech documentation I have seen anywhere. Also not to forget that I haven't had to deal with any bugs whatsoever. You guys are amazing.
just recently started learning Tailwind and now am wondering why I didn't start sooner. This was a really great presentation and great work by the tailwind team
I'm so glad that I tried tailwind... Sheesh. I saw the markup and it scared me but I thought let me just try it and it's changed my workflow completely. Thank you guys so much.
Since the event, I have been dying to post and talk about the features of Tailwind CSS V3.4; I didn't want to steal your thunder 😅. @TailwindLabs and Adam, we all appreciate your efforts and the fantastic first-ever event and undoubtedly one of the most impactful utility-first CSS frameworks. 🎉
I bought refactoring UI when it came out and watched Steve’s videos where he improved sites. Used TailwindCSS pretty early and bought TailwindUI on day one. There are only a few others that helped me improve my developer skills as much as you did. Hats off, you really left a mark on modern web development. Additionally you are a great example that Open Source can still workout great! Thanks and please stay around ❤!
Our team at ConsenSys, building Web3 use cases are all using Tailwind Components. I've been using it since I worked at Tesla in 2018. Absolutely love it. I don't use it as often for personal projects, but anytime we have teams that need to be consistent across multiple sites, properties etc. We are using Tailwind.
how did that place not erupt into laughter at 5:50. "If you don't use tailwind I don't know why you are here? This is a celebration...". Hilarious! hahahaha
A very interesting event, a lot of content, examples and news 🚀. It's nice that Tailwind is constantly evolving. I'm also surprised and excited about a few things from the presentation. Currently, I want to use it in even more projects, although I'm still getting to know it.
"My vision for what I want to help people with Tailwind which is build CUSTOM stuff" -Adam that's why I use tailwind since his first release, I never use css frameworks, no bootstrap, no anything, until I discover tailwind! because I'd always want CUSTOM stuff, thank you Adam!
Such an amazing CSS framework!! CSS always goes unmaintainable after some time and I have seen it happening in my almost 20 year career. It seems Tailwind finally solved that issue without impacting performance or adding bloated runtime JS
I remember implementing that responsive Modal (open from the bottom on small screens and in the middle on large screens) and all I had to do was to add some responsive tailwind classes to the existing headless UI example. The tricky part, however, was to account for the dynamic height of the mobile browsers
Great Event ! Appreciate what you are doing ! Would be nice to see the Catalyst for Angular too it will be like Material UI but full customizable, without need to wasting time of writing these Reusable Components and help us focus more on the logic :)
what i love about the oxide part is, it kinda breaks the barrier between webdev and designer or somebody using a web-builder. the latter people are more familiar with css files, so the haste to config is less
Tailwind is the best thing that I discovered after Django. Today, I always use Flowbite (a library of UI components built with Tailwind CSS) in all my Django projects.
