Tailwind Studio?

I believe you misunderstood the meaning there. The designer/Developer makes it what they want and it doesn’t matter what framework it’s in, it can be done in any of them (not including js etc. Obviously you can do more with other languages.)

And although you may not consider web design coding actually “coding”, it’s still called “coding a website”.

I think this is the end of the road now bois we all develop websites (or i assume so), we all have our own opinions and i don’t think its a good idea arguing what the best framework is or how good one is over the other, i think we should simply put it to a neutral statement, that being, BSS and TW are just as good as eachother, with the exception that BSS requires more skill and years of learning, the only real reason i replied to the post putting my argument is because ive never seen a BSS or BS site that looks like an exact copy of a tailwind site, it doesn’t seem like an easy thing to do, considering the whole framework behind TW and how its set out, it was nice talking to you all, its nice to meet new people, whether that be in a debate or just gaming or talking in general, i don’t think we should bash eachother in with words to make silly arguments, i hope you all have an amazing day :slight_smile: if anyone has discord and wanna add me to talk code or gaming or general talk feel free, Свисток#1203 my tag (not an advertisement).

2 Likes

I did add u ;p idk for what but why not lol

1 Like

I didn’t see any bashing here. Just people politely expressing their opinions.

1 Like

I actually contacted the company directly a year ago asking this very same question, and their answer was “NO”.

It’s too bad because Tailwind desperately needs (deserves) a dedicated IDE, and the market is RIPE for the taking! But BSS’s response was that they “have no intentions of developing a Tailwind product”. Their loss.

Bootstrap Studio is AMAZING. For Bootstrap. Which we no longer use. And pretty much every developer I know has moved to Tailwind as well. So I don’t even install BSS anymore. But I would buy Tailwind Studio in a HEARTBEAT, and tell everyone I knew about it too. Oh well. :disappointed:

BUT, if you are looking for an IDE that DOES support Tailwind, currently the ONLY one I have found that supports it natively is Pinegrow.

1 Like

“I’m currently using tailwind inside bss with bs I had to do few small tweaks to make this work, but works really well” - Can you please let me know HOW you did this?

Yeah. Okay. :smirk:

Most of this was taken from another forum and mildly edited by me, but I consider it a generally accurate assessment…

The two technologies are not 1:1, and many folks don’t seem to understand the differences or similarities. For example, you have to pay (at last check) $300-$800 to gain access to the Tailwind component libraries & templates, while Bootstrap’s component framework is a dominant AND FREE feature that has been the go-to choice for developers over 10 years. That’s one of the reasons it’s the leader.

Bootstrap 5 dropped the jQuery dependency (which was a major pain point.) 90% of the utility classes that Tailwind offers have direct parallels in Bootstrap, they just aren’t grouped and described as a “utility framework”. So much of this is how things are bundled and branded.

Tailwind is typically a lot harder for the average user to set up.

However, the biggest difference between the two frameworks is the availability of tens of thousands of themes - free and paid - for Bootstrap, where no parallel exists for Tailwind. Bootstrap themes are a meritocratic cottage industry worth many millions, while Adam Wathan has structured Tailwind so that the only person making money is Adam Wathan. These two market models speak to the very different core demographics for each framework. Bluntly: Tailwind attracts geeks who are chill with spending the day tweaking PostCSS and think of their sites as a hierarchy of components with elements holding 20+ CSS classes, while Bootstrap is a huge success with designers and less technical bloggers and solo entrepreneurs who don’t mind forgoing some customizability to have a nice looking site out of the gate.

I’d hazard to guess that the typical Tailwind enthusiast wouldn’t buy a paid theme, even though they would be very sad if someone pointed out that their sites all look like programmers made them.

As for the total market size: it goes without saying that there’s more than enough opportunity for the two different approaches to coexist. I’d speculate that many Bootstrap devotees wouldn’t even consider Tailwind because their problems have already been long since solved by Bootstrap.

With this said, let’s look at Bootstrap vs Tailwind on Google Trends. Notably, the disproportion between the two is such that Tailwind’s impact on Bootstrap has been (and continues to be) little more than a rounding error.

https://trends.google.com/trends/explore?geo=US&q=%2Fm%2F0j671ln,tailwindcss

And finally, this is worth the read…

(Now cue the historical soundtrack)

As a graphic designer who started designing websites 20 years ago in Photoshop and handing them off to (then) HTML “wizards,” I will say this. In the post AOL world, when the web started to gain popularity among the masses, it was largely about finding and sharing information. UI and UX barely mattered. It was mainly the computer geeks’ playground. Ordinary people used the web to do research, share files and software, or for recreation - engaging in primitive social networking by exchanging pictures, flash animations, “surfing the web”, etc… (I’ll forgo mentioning the porn-colored elephant in the room.)

We had two basic devices to access the web - desktops computers and laptops - with two basic browsers - Netscape and IE (maybe Safari if you cared about the Apple crowd.) We designed for one or two screen resolutions. For most individuals who had their own websites, it was about making an artistic statement (usually, sadly, with dozens of animated gifs :man_facepalming:.) For most businesses, websites were glorified business cards or informational brochures. For designers, it was the “wild west.” Dramatic and unconventional was the rule of the day. If you made a website that looked different or did something nobody had ever seen before, that was a huge deal. But there was a LOT of ugliness on the web.

Then two things changed the entire game:

  1. e-commerce/advertising
  2. mobile devices (mainly smartphones.)

Number one changed the entire focus of what we used the internet for. It was no longer about sharing information, it was about making money (some may say, “but what about social media?” but social media is really just another way to advertise/make money.) Once money/commerce entered the equation, the bar had to be raised. Things had to become more professional. The wild west had to be tamed.

Number two ushered in responsive design, and the realization that websites had to be both visually appealing and functionally intuitive on countless devices. This meant standardization (something designers HATE.) It was a painful transition with some significant setbacks (remember Adobe Muse and Flash websites? :man_facepalming:) It took awhile for us to settle on the basic format that is widely in use today, but standardization was necessary because we had millions of people discovering the web every month, and like automobiles (with steering wheels, gas pedals and brake pedals in the same locations) people needed websites to have predictability.

Frameworks were a huge step forward in this regard because they constrained developers to building websites in ways people expected them to look and work. The reason Bootstrap became so popular is not because it made it easier to build sites (although it did) but rather because it did an exceptionally good job in making websites look and work the way people expected them to.

Tailwind is not a revolution in web development. It doesn’t create “better” websites, and it’s not going to replace Bootstrap. It’s just another approach to how we use CSS. To an end user, there’s absolutely no distinction between a website built with Bootstrap and one built with Tailwind. A site built with either can be made to look and function exactly the same. Development tools will continue to evolve in minor ways, but until there is some major paradigm shift in what we use the internet for, the tools freelancers and small teams choose will largely be a matter of what each finds works best for them.

If you like Tailwind and it works best for you, then that’s what you should use. If you like Bootstrap and it works best for you, then that’s what you should use. Or you could use both. Or neither. At the end of the day, the only thing that really matters is the end-user’s experience.

2 Likes

The article is the funniest one I have read today and I’ve stopped after 2nd caption since It’s waste of time.

This guy knows literally nothing, he can’t even type his props in React component properly while he ll be teaching me why to don’t use tailwind or sum, hilarious.

The only one correct aspect would be that few utility classes have weird naming + it took me two days to feel smooth enough in tailwind, after it was just checking documentation for more things like custom values etc tweaking or extending tw options.

That guy wrote a whole wall of text just to show that he has no idea what he’s talking about and that he didn’t even jump into tw seriously at all and the fact that he can’t even prop his react component properly is even funnier to me.

He doesn’t understands the tool yet and he doesn’t recommends it and says its bad, lmao pepega.

No, it wasn’t worth the read :slight_smile:

1 Like

Depends about ur expectations, but it was enough to read tailwind documentation and implement the whole info inside bss, that’s all.

You can always reverse engineering bss, but its not worth it at all

These seem to be recurring themes in many of your posts these days (sorry, dicky just stirring the pot :stuck_out_tongue:)

As I said, we’ll each use the tools we feel are best for us. I really have no dog in this fight. I just like to read and share what other people think of different technologies because it gives me a general “lay of the land.”

After 40 years of working with computers (30 of them to make a living) I’ve gone through dozens of hardware and software technologies. I learned long ago to not sacrifice profit for loyalty. I’ve watched superior products crash and burn (like the Amiga) and mediocre ones take over the world (Windoze.) I’ve seen industries invest everything into “XYZ” only to watch it die a slow death (Quark Xpress > InDesign.) It’s basically taught me that nothing lasts forever, the only constant is change, and change is usually a PITA!

It will be interesting to revisit this subject in 5 years and see if Tailwind has “stolen the crown” (so to speak) from Bootstrap.

I’m not fighting for anything, I’m not even fighting at all. My entire point is that this guy didn’t even read the documentation at all cause his arguments are totally invalid as I’ve said the only proper one would be about the naming classes, but that’s all. Rest is easily not a problem at all, styled component are fixing the horizontal and vertical “problem”, u can also configure prettier for tailwind styling and its also not a problem at all and i could keep talking about it all the time. That guy just didn’t cover and mention anything like components in tailwind (similiar to utility api in bootstrap :slight_smile: ) and many more, its not my ego or sum, he just knows nothing about tailwind and theoretically he covered good points, but they were invalid.

We always should pick up a proper tool for our projects based on our needs etc, but i just don’t like when ppl who have totally zero knowledge about x tool share wrong informations around the community.

Tailwind is already main stack in many web apps. If its not MUI or Chakra, it’s always tailwind.

I like that bootstrap added the utility api cause it makes bootstrap much more powerful and opens new ways of customizing itfor our needs or expanding the workflow, its still not tailwind, but its really good attempt to provide something similar.

“dog in this fight” Is just a euphemism. I mean discussion… debate… whatever you want to call this thread.

If anything, it’s made me more curious about Tailwind such that if/when I have the time, I may play around with it a little.

I’m curious, have you purchased their component kit?

$300 seems a bit pricey.

I like to create stuff by myself from scratch, but it depends and no i didn’t buy anything especially that theres alot of free and great ready to use ui libs or kits, so :stuck_out_tongue:

Hello, just want to contribute my 2 cents. I believe the above google trends revealed misleading stats as it compares Bootstrap and TailwindCSS. The more common form for TailwindCSS is Tailwind. The correction applied to worldwide the results are as follows:
https://trends.google.com/trends/explore?q=bootstrap,tailwind

Bootstrap is barely more used than tailwind, since last time tailwind got more attention than before and bootstrap has only 300k more npm downloads(weekly) before it was over 2 mil. I told yaa that some time and tailwind will be the main tool for styling, and since last time bootstrap got over 4x less gain than tailwind. Few months and bootstrap will be fully behind.

Just saying to add up :wink:

According to The State of CSS, Tailwind usage has grown 41% from 2019 to 2022. At the same time, Bootstrap usage has only dropped 6.3% in that same period.

Bootstrap is still the most popular framework by a sizeable margin. It is still being actively developed and improved. Millions of websites and over 40,000 companies are still using Bootstrap in 2023, so it’s certainly not going to disappear anytime soon.

I have no doubt that there are a lot of benefits to using Tailwind. Nor do I doubt that its popularity will continue to grow, but personally, the whole idea of having twenty-plus utility classes strung horizontally in my HTML just makes me shudder. The minute I see a horizontal scroll bar in code I want to get away from it. The whole reason CSS was invented was to separate the styling from the structure. HTML should be limited to the structure of the page. All the same arguments against using inline styling in HTML are applicable to using Tailwind.

Anyway, who knows where we’ll be in five years with the way these chatbot AI’s are evolving. Building websites may eventually become as simple as ordering a pizza.

2 Likes

My main tool for styling is my imagination and a splash of css.

tailwind and bootstrap are simply tools to get you started with the foundations, it is up to the designer/developer to make the end result unique.

This thread it turning into an apple/android apple/windows what is best :upside_down_face:

3 Likes

One approach might be to have an official BSS boostrap executable / script as an export option.

There is a hosted PHP version right here.

Didnt take a lot of time, to beat the downloads of bootstrap, just few months and bootstrap is already behind, it only shows what will happen to bootstrap ecosystem in next years, its same case that happened to styled components and other css in js solutions.

Also comparing usage is the most irational thing to compare, especially if bootstrap usage is dropping and its dropping by low percentage cause in latest years there was more built bootstrap based websites and apps, so its normal that it wont drop by 235235%.


interest the lowest, since no one cares about bs anymore, its really tough

you make no point to me

It wont disappear any soon cause it takes time to move thousands of apps and websites to new technology especially if the scale is gigantic also many companies wont do that cause its a cost and kinda risky move.

Just coming back to this post to show how quickly tailwind is growing and bootstrap dropping. Bootstrap has old attitude towards styling the projects, it tries to catch up modern solutions like tailwind by implementing utility api and many more, but it iwll be always behind, so it will die slowly

LOL… okay, by that logic, then the increase in usage of Tailwind is also irrelevant, right?

Yes, according to this State of CSS, Bootstrap has lost users, but State of CSS is just one website that has surveyed a tiny fraction of the website development community.

Bootstrap is FAR from being abandoned. It’s still being actively developed, millions of developers use it. 40,000+ companies use it. It got a major facelift when 5.0 came out, and with CSS variables and dark mode coming, it’s going to remain popular for the foreseeable future.

But Tailwind will also continue to gain users, and maybe it will eventually overtake Bootstrap. If so, who really cares? At the end of the day, frameworks are just abstraction layers that hide the actual CSS rules. Learn CSS and then use whichever tool helps you build your sites/apps the best.

The “influencers” will always find ways to claim “this is dead” or “that is dead” because it gets them clicks. Just search “Bootstrap vs Tailwind” and you’ll find endless hits for people on both sides. For years I read that PHP was dying but almost 80% of the web still runs on it. WordPress is still insanely popular even though it should be crucified, burned and buried. Predicting the future of web development is like trying to predict what the stock market is going to do. Nobody really knows.

2 Likes