The biggest complain for me about nextjs is the testing part. Did you ever tried to create a Monorepo which includes nextjs and want to run integration tests like any other react app with react-testing-library? Good luck. The integrated routing solution makes it really hard. There is a Community solution to named „next-page-tester“, but nothing official. That’s much better with gatsby and it’s built-in usage of reach-router. I hope it’s the same with remix.
Remix – A framework focused on web fundamentals and modern UX
181–190 of 307 posts
Re: Remix – A framework focused on web fundamentals and modern UX
#182So, after looking over the docs, here's my comparison list between Remix (which I haven't used) and other things that I've used. - Forms seem better in Remix. Remix seems focused on progressive enhancement here, rather than fetch. Imagine if Next supported POST endpoints, and the idiomatic way of making your site was to use that instead of API endpoints. I hope that we soon see a Remix-compatible form validation libr…
> Forms seem better in Remix. Remix seems focused on progressive enhancement here, rather than fetch. Imagine if Next supported POST endpoints, and the idiomatic way of making your site Remix does nothing to make this happen, it's just the way html works. I dont see how it would not work on next. The difference is api is in a separarate directory and remix have them in the same file. Superficial.
It "wouldn't work" on next because your getServerSideProps receives a node http.IncomingMessage, and you would have to parse all of the form data yourself, or install a dependency to do it. Then you would have to write a second endpoint in a second file to be able to respond to a JS-enabled (fetch) request. Plus you get to implement all of the progressive enhancement yourself (state tracking, preparing that fetch request, etc).
I mean, I suppose if your baseline is writing server endpoints in assembler, all of this probably does seem pretty superficial.
Re: Remix – A framework focused on web fundamentals and modern UX
#183So, after looking over the docs, here's my comparison list between Remix (which I haven't used) and other things that I've used. - Forms seem better in Remix. Remix seems focused on progressive enhancement here, rather than fetch. Imagine if Next supported POST endpoints, and the idiomatic way of making your site was to use that instead of API endpoints. I hope that we soon see a Remix-compatible form validation libr…
I think in an SPA, traditional form posts and server redirects are a terrible idea.
This might work for q blog post example, but imagine doing a full reload just because you liked a post or a comment.
Re: Remix – A framework focused on web fundamentals and modern UX
#184So the web dev madness has come full circle - the react people just built rails in react. In the mean time I just keep using rails...
Not full circle...this is more like an 8 shaped thing, and with this we're right at the wrong extreme right now in my opinion.
Re: Remix – A framework focused on web fundamentals and modern UX
#185Re: Remix – A framework focused on web fundamentals and modern UX
#186Earlier quoted context omitted.
Remix might be a few years too late to be honest. After watching the session, there does not appear to be any significant differences from Next.
the team behind remix probably has the biggest following in the react scene, so even without having any major differentiation (though I happen to think they do have) it's going to gain popularity.
Yes, but just because marketing.
Re: Remix – A framework focused on web fundamentals and modern UX
#187So, after looking over the docs, here's my comparison list between Remix (which I haven't used) and other things that I've used. - Forms seem better in Remix. Remix seems focused on progressive enhancement here, rather than fetch. Imagine if Next supported POST endpoints, and the idiomatic way of making your site was to use that instead of API endpoints. I hope that we soon see a Remix-compatible form validation libr…
There is https://github.com/smeijer/next-runtime if you want `getServerSideProps` to be able to handle post request and return a json
Re: Remix – A framework focused on web fundamentals and modern UX
#188So, after looking over the docs, here's my comparison list between Remix (which I haven't used) and other things that I've used. - Forms seem better in Remix. Remix seems focused on progressive enhancement here, rather than fetch. Imagine if Next supported POST endpoints, and the idiomatic way of making your site was to use that instead of API endpoints. I hope that we soon see a Remix-compatible form validation libr…
I think in an SPA, traditional form posts and server redirects are a terrible idea. This might work for q blog post example, but imagine doing a full reload just because you liked a post or a comment.
To be clear, I don't think Remix does this: the built-in `Form` component automatically handles converting the form submit into a fetch call and routing it directly to the appropriate component without doing a full page refresh, unless the component explicitly calls for an explicit refresh afterwards (e.g. redirect).
Re: Remix – A framework focused on web fundamentals and modern UX
#189So, after looking over the docs, here's my comparison list between Remix (which I haven't used) and other things that I've used. - Forms seem better in Remix. Remix seems focused on progressive enhancement here, rather than fetch. Imagine if Next supported POST endpoints, and the idiomatic way of making your site was to use that instead of API endpoints. I hope that we soon see a Remix-compatible form validation libr…
There is https://github.com/smeijer/next-runtime if you want `getServerSideProps` to be able to handle post request and return a json
This looks great! Definitely brings Next and Remix to a pretty close level in this regard.
Re: Remix – A framework focused on web fundamentals and modern UX
#190Earlier quoted context omitted.
I disagree wholeheartedly. This site breaks every UI/UX rule in the book, and in the worst ways. Instead of just letting people read the information at their own pace, they've decided to limit the information to one partial sentence at a time, and more than half of those sentences are just irrelevant jokes. Possibly even worse is the lack of snapping to the sentence, which means the user has to guess how far they nee…
Well, on a first page without any scroll you have action buttons which leads you to the pages where you can read at your own pace. For people who don't want that they've put small bits of information on each scroll. Every information is carefully chosen, so you keep scrolling and reading. After that you go to the doc to read more. I've never seen better UI/UX that hook me in so quickly. If it was just regular page I…
> Well, on a first page without any scroll you have action buttons which leads you to the pages where you can read at your own pace. For people who don't want that they've put small bits of information on each scroll.
You're reversing the series of events. A user visiting a page (especially a homepage) expects it to offer relevant information in an easily consumable way. It is impossible for a user to automagically intuit that they can get more easily consumable information on a separate page, just because a link to that page exists.
So, what you're suggesting is that it's good UX to make the homepage so annoying that multiple pages are required to provide the same information. That's called an anti-pattern, and really makes that nearly 1MB page load (and 80kB loading gif) a complete waste of time and electricity.
Even worse is that the feature information doesn't actually exist outside of the homepage, so you're making an incorrect assertion that people who don't want to scroll can instead just click a button.
> Every information is carefully chosen, so you keep scrolling and reading. After that you go to the doc to read more.
In this case especially, the information is the exact opposite of carefully chosen. It is chock full of jokes and irrelevant "aren't we cool" posturing, which comes across as pure "tech bro" and does a terrible job of convincing someone why they should use and trust this framework as a foundation for their product.
> I've never seen better UI/UX that hook me in so quickly. If it was just regular page I would think "ah, just another framework" and close the tab.
A bizarre statement. You're admitting to be willingly manipulated by style over substance, and that you have a premeditation for not actually reading a site's content unless they've met some arbitrary level of flashiness. If a project manager asked you to research frameworks, and your response was to supply them with a list of homepages that you thought "looked the coolest," you'd be fired on the spot.