solid-docs
solid-docs copied to clipboard
Documentation wish item
Would love to see a section on the website specifically and directly answering the following for people coming from React and/or Vue:
- Why another framework?
- How is this different from React / Vue? What are the relative advantages?
Yeah I wasn't sure how strong handed I should be.
There is this section: https://www.solidjs.com/docs/1.0.0#comparison-with-other-libraries (looks like the link to hash isn't working properly).
Do you think this blog post is too opinionated to just link Why SolidJS: Do we need another JS UI Library. While I have an article for pretty much every topic this is by far my least favorite. I don't like tearing at other libraries with things that fringe on opinion.
I think I probably should address this differently. There is a difference between my motivations for creating a new library and the benefits today.
I would like to work on it can u elaborate more and where I i have to do the changes..
I don't like tearing at other libraries with things that fringe on opinion.
You're good at pointing out things you've learned from other frameworks; maybe go with that angle?
Yeah I think if I do this. I'm going to have to handle this as it is delicate.
I feel like we could do a better job of answering this in the comparison guide which is being reviewed by @Jutanium . It could be very neutral and avoid answering the question directly of "why another framework". I feel like that might be better suited or solid-site to express as marketing.
Deploy Preview for solid-docs failed.
| Name | Link |
|---|---|
| Latest commit | da7a79b2c2c07b68175646f1354438038ef75399 |
| Latest deploy log | https://app.netlify.com/sites/solid-docs/deploys/62b60ea52f4e28000aeb0792 |
What do you mean by grab files from a file's contents? Do you mean allowing passing https://github.com/solidjs/solid-docs-next/blob/playground-test/src/components/repl.tsx#L49-L68 as a parameter?
@modderme123 exactly right. I'm not worried about it as a blocker for this PR
My current guess is that the build issue has to do with us running two rollup instances in parallel for two worker imports, and then rollup gets confused that it is called twice and has some outstanding async plugins that are actually for another rollup instance
Some issues that we ran into with rollup and parallelism are described here: https://github.com/vitejs/vite/pull/2689, maybe those would be useful if anyone is willing to help debug this.
Ok, the linked thread says that terser breaks everything without extremely careful work (and I no longer remember what), so someone might try disabling terser in solid-start to see if that works