marcotm

I think that a huge part of Tailwind‘s success is not so much the underlying concept but a combination of several aspects: You get a kind of generic design system (margins, paddings, matching colors, etc.) that are restrictive enough to help make things look good and consistent but flexible enough to not result in a every-site-looks-the-same situation (at least not to the extent many other CSS frameworks did); Tailwind sits at a low level of abstraction above raw CSS that is just enough to make some CSS concepts a little bit easier to use (flex, grid, etc.); the documentation is quite good and getting started is relatively easy; …

Given these (and probably some more) aspects, Tailwind makes it easy to get some good results quickly which helps to convince users that their whole approach is the right way to go. Add very good marketing and early traction and you are where we are now.

So I agree with the article that Tailwind‘s conceptual approach is not the holy grail it‘s often said to be, but it maybe also is not even the reason for its success compared to many auxiliary things it did/does right.

Sample size one, but I actually found that the iOS ecosystem works surprisingly well for having a finished app. I have one, created over six years ago with almost no updates over the past years. I intentionally built it in a way that does not require any kind of maintenance: It works offline, i.e., does not require a backend; it's a one-time payment through the App Store (no subscription -> no expectation of continuous updates); the free and paid versions only differ in how many items you can put in the database, i.e., everyone can try the full feature set before buying -> reduces complaints / refunds; etc.

While these are deliberate design decisions, a nice benefit of the iOS ecosystem is that the app has kept working on every new iOS version without me updating anything in the code. Things like installation flow, payment processing, etc. are definitely components that would fall apart a lot sooner when not offered by the platform itself.

Sure, platform lock-in and all that stuff, but so far the app just keeps generating happy users every month (and some pocket money).

Just to present a balanced view for our international audience: a significant number of locals sincerely enjoy Oktoberfest. Within my circles in the Munich tech/startup scene, a visit to Oktoberfest with the team is often considered one of the year’s highlights in terms of team building and socializing. People attend with friends, family, etc. The infamous images of inebriated tourists merely represent the most attention-grabbing outliers, overshadowing the majority who simply have a splendid time there.

Munich does have its share of issues, rent being a notable example. However, most of these problems are likely a result of the general lack of serious troubles, relatively speaking, which in turn boosts the city's attractiveness.

Yes, sorry, you're right of course. I wanted to say that you need to use the more developer-oriented tooling (API, Playground) if you want to have the parameter options.

Thanks for mentioning the Firebase-based API. I knew it existed, but somehow I went with the Algolia API by default. I use their HN search quite a bit, so that's probably why I stuck with them. (no affiliation)

You're welcome! For the chat model, it definitely helps to let it know that you want valid, parsable JSON (and nothing else). Otherwise it tends to get chatty. ;-) Depending on your use case, you might even ask it to fix the JSON if it's not parsable.

Thank you very much! I will definitely try out your suggestions! However, at least with GPT-3.5 and the amount of data I have to deal with in this case, my main concern is the quality of the extractions. With about 500 posts per month, the cost is manageable. But for larger datasets, saving tokens is definitely important.

Thank you very much! Filtering by location (and role) is on my todo list, but it is trickier than it seems at first. And I totally agree that the buttons are confusing. Actually, the "sort" button does sort the jobs. It sorts by semantic similarity to the job you selected (using the GPT text embedding). As for the buttons (and probably other parts of the site) not being accessible: I apologize. This shouldn't be an afterthought.

Exactly. I am sure you can get similar results with some "traditional" NLP skills, but the good (bad?) thing is that they are not required when using one of the newer LLMs.