Mannn, I was waiting for a post like this, I saw a comment regarding Nested Routing and thought it was pretty cool. The pattern I use nowadays with Next is to have a Layout component and a Provider (using the context API) component, the Layout will be responsible for (literally) the general layout and the Provider will be responsible for storing any state and it's pretty complex.
The more I read about it, the more I feel like Remix is trying to take a whole other approach to plug the holes in React. NextJS is/has been doing a great job for a long time so it's definitely cool to see how Remix turns out. IMHO they should at least opensource the docs, so folks don't have to literally pay $250 to know what Remix offers. I ranted about this in your previous post too, so I'm sorry if it's too much lol
PS: It's really awesome that you're doing this for the community though! Maybe turn it into a newsletter? I'd definitely subscribe
Maybe there is concern that people will copy it too quickly. I mean the nested routing for one is older tech with a few improvements. There are other libraries doing similar things. It's possible that in a couple weeks we will see options to bring this sort of stuff into Next etc.
I agree re: docs. $250 is not a lot for some people, but a significant investment for others, so not really knowing what you're getting into will probably (imo) lead to even less sales for them.
Thing to remember is that we're not done, this is a "Supporter Preview Releases" not a production ready product yet. It's more of a kickstarter. Public docs would be great for some, but would also attract people that would just distract and irritate. We have millions of OSS users, so we know what can happen with something new :P
We only expect a handful of our Remix development newsletter subscribers to buy right now. They've been hearing about it for a few months. When we release the 1.0 we'll have compelling demos, documentation, and a free evaluation period. But that's now what we need right now. We need a group of supporters to help us kick the tires.
I see, that makes me feel relieved. I got pretty excited yesterday after reading this post so I might buy a license for myself to take a look at all the fun stuff :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Mannn, I was waiting for a post like this, I saw a comment regarding Nested Routing and thought it was pretty cool. The pattern I use nowadays with Next is to have a Layout component and a Provider (using the context API) component, the Layout will be responsible for (literally) the general layout and the Provider will be responsible for storing any state and it's pretty complex.
The more I read about it, the more I feel like Remix is trying to take a whole other approach to plug the holes in React. NextJS is/has been doing a great job for a long time so it's definitely cool to see how Remix turns out. IMHO they should at least opensource the docs, so folks don't have to literally pay $250 to know what Remix offers. I ranted about this in your previous post too, so I'm sorry if it's too much lol
PS: It's really awesome that you're doing this for the community though! Maybe turn it into a newsletter? I'd definitely subscribe
Maybe there is concern that people will copy it too quickly. I mean the nested routing for one is older tech with a few improvements. There are other libraries doing similar things. It's possible that in a couple weeks we will see options to bring this sort of stuff into Next etc.
I agree re: docs. $250 is not a lot for some people, but a significant investment for others, so not really knowing what you're getting into will probably (imo) lead to even less sales for them.
Thing to remember is that we're not done, this is a "Supporter Preview Releases" not a production ready product yet. It's more of a kickstarter. Public docs would be great for some, but would also attract people that would just distract and irritate. We have millions of OSS users, so we know what can happen with something new :P
We only expect a handful of our Remix development newsletter subscribers to buy right now. They've been hearing about it for a few months. When we release the 1.0 we'll have compelling demos, documentation, and a free evaluation period. But that's now what we need right now. We need a group of supporters to help us kick the tires.
I see, that makes me feel relieved. I got pretty excited yesterday after reading this post so I might buy a license for myself to take a look at all the fun stuff :)