I so hate it when people use these ridiculous acronyms with meanings dependent on context. Just type out experience and everyone will know what you’re talking about. What does ‘level’ even mean in this context? Do you level up to level 2 when you get enough experience like in a video game?

It seems to do a lot of interesting new things, but the subscription and registration model makes it a no go. Still, this is a net positive, as it might give some new ideas for a FOSS implementation similar to it.

I don’t understand. What does the fediverse have to do with the jam? Do you have to use mastodon/lemmy in you game somehow?

I don’t think you got my point: Acronyms are silly. Especially the ones you can easily type out.

Wow, so this guy sabotaged a community of almost 5 years in just a few weeks because he couldn’t understand how financials work. And has now left it open with a big “Scam warning” at the top, that will damage the reputation of the entire project.

Maybe he should pass it on to someone else instead of acting like an overgrown child throwing a tantrum.

I’m not a frontend dev. Can someone ELI5 to me the point of DaisyUI+Tailwind? With Tailwind you’re supposed to style your elements faster with atomic classes directly in your HTML. But then with DaisyUI you’re using semantic class names, so it’s basically going full circle to plain old CSS? What is the point of TWO added tech layers when you could achieve the same using CSS+HTML components like Bootstrap and the like? I’ve also read that Tailwind has horrible performance for development since it moves around megabytes of utility CSS, that with DaisyUI, you are just not going to use, and will mostly be stripped out by a long build process before release.

Indeed, this is a huge design flaw. You would basically have to police everything that users post on other instances as well. Do you even have moderation tools for this?

The famous Mediterranean diet did not include the ridiculous amount of meat and animal products that are so common today.

Every front-end styling dev can now speak the same language, rather than constructing their own from scratch.

Ok, but with Tailwind it seems that they are just saying p-4 uppercase instead of padding: 1rem; text-transform: uppercase; which is shorter, but exactly the same thing since it maps 1:1 to ‘custom’ CSS. It also doesn’t abstract away the CSS underneath, it just gives it a new name, which you have to learn in addition to the CSS

Tailwind compilers should only bring in the classes that you’re using, so it should be much smaller than almost any other framework.

In theory yes, but in practice look at the link in my original post for how it becomes slow with hot reloading in Vite. I don’t know if it would have the same problem with leptos, but probably yes, since it is an architectural flaw of generate the world, strip it down later.

DaisyUI is useful because it has helper classes

I do get DaisyUI, and it does fulfill the goal of getting devs to speak the same language. <button class="btn btn-primary"> totally makes sense. What I don’t get is why couple and build it on top of Tailwind which becomes useless at this point, since it’s just shorthand for some CSS. Maybe I am missing some big feature of Tailwind? Quoting the creator of Tailwind from the main page

So he is clearly against the approach that DaisyUI advertises as a selling point.

Enshittification.

I just switched to https://marketplace.visualstudio.com/items?itemName=humao.rest-client a few years ago. Way better, simpler, easily version controlled and reviewed, completely FOSS. Only downside is it’s just for VSCode, if that’s not your thing