I will say it bluntly because it needs to be said: that website is not enough for anyone to be interested in the library.

There are also plenty of other examples as mentioned in the comment above. Also many other projects using Sycamore which you can see by looking at GitHub’s reverse dependency page.

Not a single example of an actual application is not a good look for a web ui library

What kind of examples were you expecting? There are plenty of examples in the examples/ folder on GitHub as well as plenty of other projects using Sycamore as can be seen from GitHub’s reverse dependency page

At very least I'd like to see how easy it is to build a simple -/+ counter and click some buttons.

I used Sycamore tho, it's neat.

Yeah that makes sense. I’ll work on improving the front page

then you should be delighted we have LLMs one of the use cases they are best suited to is writing documentation, much better than humans can.

Good is debatable. The docs I want point out the weird shit in the system. The AI docs I've read are all basically "the get user endpoint can be called with HTTP to get a user, given a valid auth token". Thanks, it would have been faster to read the code.

They write good _looking_ documentation. How good those docs are is entirely on the person/people who prompted them into existence.

Please don't inflict LLM docs on people

the sky is falling...

finally! I'm building an app that's essentially a "sidecar" to an llm subscription and works via mcp and has a web ui to make reviewing deliverables easier, uses the user's subscription for intelligence instead of requiring to pay for tokens inside the app. The problem until now is I couldn't trigger AI work from the web ui, that limitation will be soon gone, it fixes a huge ux issue for me, I honestly thought it would happen sooner but I'm glad the industry is catching up.

it's gambling until you learn how to set up proper harnesses then it just becomes normal administration. It's no different than running a team, humans make mistakes too, that's why we have CI pipelines, automated testing etc... AI assisted coding "JUST" requires you to be extra good at that part of the job.

Was the product. It's fundamentally unsound, but beyond that, why would you be in that thing? The Metaverse had barely any content worth using, there was no reason to buy it beyond disposable income and novelty.

I think it was totally predictable, I was telling my colleagues at Meta back then the Metaverse was completely toast in 2020 for a variety of reasons that only Mark Zuckerberg in his infinite wisdom couldn't see clear as day.

The Metaverse was not something that Meta was good at, they went about it all wrong and it was doomed to fail.

it's not the CLI, it's the model. The model wasn't trained to do that kind of work, was trained to do one shot coding, not sustained back and forth until it gets it right like Claude and ChatGPT.

so now you have almost all the parts of an mcp:

1. the tools 2. the instructions

just add an auth mechanism to it and you get mcp OR use mcp because it's a nice self contained package that contains all of it.