giscus VS unocss

That project also has Github issues and discussions pages to ask questions and get help.

When creating my blog-centric personal portfolio, I had a goal of launching it as soon as possible. However, considering including a comment feature, the implementation process could be time-consuming. That's when I started looking for a solution that was easy to set up yet provided essential commenting functionalities. It was during this search that I stumbled upon Giscus.

But now, a new fellow named giscus commenting system has entered the town, it's basically powered by github. Since I already host my blog on github pages, this should be a natural choice for me, right? Many bloggers seem to be migrating to this new system and I might too soon. The downsides however are as follows:

Get Giscus here.

Supports Giscus - a comments system powerd by Github Discussions.

I've encountered https://github.com/utterance/utterances, which relies on github issues for providing a blog comments system of a sort.

Alternatively there's https://github.com/giscus/giscus, which instead uses github discussions.

Haven't used either so can't comment (heh) on their "performance".

There's also a recent similar tool called https://github.com/giscus/giscus that uses Github Discussions as the backing system, rather than Issues.

I wish tailwind would support attributify like https://github.com/unocss/unocss, which is much more readable for complex layouts:

  link

I feel the same about people praising Tailwind.

Tailwind (and similar, I tend to use https://unocss.dev/) is not good for your frontend architecture BUT they allow you to be so fast, that it negates the benefits.

For a job well done, I'd follow the principles of https://maintainablecss.com/

I think UnoCss is may be better than Tailwind already and has a good Vue integration https://unocss.dev/

The most popular tools that implement this approach are: Tailwind, WindiCSS, UnoCSS.

- UnoCSS: https://unocss.dev/

haha, fair point. Still, I'm on the fence about how utility components are namespaced in USWDS. Perhaps giving users the flexibility to define the namespace might work better? One thing that bugs me is the absence of class-sorting like we have in TailwindCSS. Plus, there are some gaps I've noticed in USWDS. The naming, especially when comparing "padding-x-2" and "p-x-2", can be really annoying when switching around, maybe that could also be an option for the developer or project. Similar to the ideas antfu has on uno.css https://unocss.dev/ ♥

UnoCSS is a popular option

UnoCSS — for styling with Tailwind-like atomic CSS;

Some exceptional libraries and frameworks only support VSCode, which you could argue is a bad thing, but it makes sense, VSCode is the most popular code editor after all. For example UnoCSS only has a VSCode extension, and it's my favourite way to write CSS. Astro has a LSP but I've found that the experience in VSCode is much better than in Neovim.