compatibility with LLMs has already been influencing my own tech choices! one such example is picking up and using Tailwind for side projects. I've always eval

compatibility with LLMs has already been influencing my own tech choices! one such example is picking up and using Tailwind for side projects. I've always evaluated many different component and CSS libraries, usually settling for something a bit outside of the most common solutions. for example from 2020-2023 i mostly used HP's Grommet component library, whereas most developers were using something more popular like Material UI or Bootstrap. i had to evaluate frontend libraries in 2023 for a work project, and one of the team members suggested Tailwind, so i needed to give it a try. i found that the "ugly" utility classes were mostly the same as the bootstrap ones, which have been around a long time, and Tailwind intellisense makes decoding or remembering them a breeze. what i did not expect was how much easier using LLM's are with Tailwind. I had been using plain CSS and the LLMs do fine with that, but copying and pasting multiple files was much more annoying than having everything contained in the component as with Tailwind. so that's another vector where LLM tools can shape technology choices, besides the winner-takes-all problem!