Remix v1 Beta Launch

Through lots of live code, Ryan and Michael will tell you all about where Remix started, where it's at now, and what this v1 Beta launch means for one of the most exciting web frameworks today.

[GustavoDiaz]

I can't stop watching Michael's faces while Ryan is typing.

[dealloc]

Tons of respect for Micheal and Ryan for bringing amazing tools, both open source as well as solutions that help make the web better and make developers' work easier to think about the real problems and implement ideas.

This was a cool demo, and definitely made me consider Remix for future projects. This demo just touches the tip of the iceberg of what Remix brings to the table and this demo showed the most common problems and how they solved them.

Having been a developer for a long time and using React, building a ton of software, this really changes the way we think about isomorphic software. There has been tons of prior art for solving this problem, but Remix, I think, hits the nail on the head.

[rob]

This looks amazing, I love the focus on web fundamentals. Can't wait to it out form myself!

[ryankshaw]

That demo was soooo good! Remix is going to push the whole React/JS ecosystem forward! Well done guys!

[datachaiadmin]

Remix is really awesome. Remix actually gets ryan and michael part of your team! Go for it!

[agoogleuser]

9:30 Intro about REMIX
10:20 Ryan's Demonstration

[DavidWMiller]

Is there going to be any other pricing options for learning purposes?

Or in other words, I completely support remix being a paid license once I choose to build something with it, but before that, buying even an indie license is a tough sell when what I need is just a few days to mess around, learn/test the basics, and decide if I actually want to use it.

I did catch the end of the video where you talk about the ideal case where the indie license could eventually be free, and that would address this either way, but in the meantime, I don't know how much the lack of a try before you buy hurts adoptions, but it's certainly the barrier for me.

[tshddx]

I really like the idea of automatically invalidating (and thus refetching) all the currently-active route data when submitting a form. That seems like a really great productivity boost for the happy path of website development! (I am also very curious about how I as the dev can get more control over that for more complex "app-style" projects with a much larger amount of state cached on the client.)

[MmmMmmGood]

Goodness you guys are some damn geniuses!! Major props!

[letsgrow]

Looking forward to be part of the community

[insaneviruss]

Remix is different. You've definitely got that 👍 I loved the idea of bringing back native browser primitives. Also, integrating the url routes deeply with data and App is awesome. I've struggled so much in the past just for that one thing alone. About you guys charging for it, its certainly uncommon but I'd say you guys have earned the right to do it. Go for it man! Set a new trend!
However, I still have my reservations around,
1. Idea of coupling server and client code together. I actually like it separate. Plus in real life scenario the handlers can get too large. I don't wanna play import-export
2. Remix does a lot of things magically, hiding from the user. A little too much. Personally, I've found too much abstraction in libraries a lot confusing.
3. I like using some of non-browser primitives, especially on server side. I dont wanna parse my request params and body always
But still, great work guys, especially for v1!

[monastyrskiiden]

@Remix Hey guys, it was awesome, especially Ryan's presentation style, which makes me smile every time. I can not wrap my head around Actions. Do I only allow to have a single action function per file? There're tons of stuff going on in the Web Apps today. What if I need multiple forms on the same page, with different request params? How to handle those? Do I have to put all my logic inside single action on this route and find a way to distinguish between those requests or I have to create a different route file with only an action function in it?

[ameencharoliya]

Who's here to check Remix because it's open source now

[fabiodan]

This plus some API stability can be a great framework!

Nextjs is great but I want to run it on my infrastructure, with the server side, and without relying on an API hidden in some .folder

[ByronAnderson]

Seems great! Integrating the server seems like the necessary step to allow for many of these enhancements, it is no wonder we are still waiting for suspense :/

[SUNILKUMAR-gyje]

"let's import useSubmit ohhh react doesn't have it remix does" hahahaha really liked the marketing there.

[TheMagnificientMan]

Nice, I truly wasn't expecting all that. I'm curious about that talk Mickael gave covering other different use cases. Please drop the link. The project is getting really intriguing

[JhonnyMichel]

47:03

no no no, that outlet thing is too easy. it can't be just that. right? right?

[lukejagodzinski]

Pretty interesting idea. A few questions:
- Don't you think that there should be some trial version where you can just play with it? It might be hard to convince anyone in the team to pay for the license without ever trying the software. Also adoption and popularity might not be as big, but it's just my opinion. Would be great to have some online playground so at least we could play with API
- What about GraphQL support? With Remix you would just fetch data with GraphQL on the server, right?
- What about more complex applications? What if I have several actions for a given route? I guess I would have to put all of them through the PUT metehod and do switch case based on some parameter. Maybe you have prepared some helpers to deal with it?
- I see that using built in data structures like FormData or URLParams might be a problem for TS types. Do you have some solution for better payload typing?
- You mention tree shaking but for my knowledge esbuild doesn't support tree shaking yet so I guess it's not yet supported.
- I see that it's heavily built around React with all the hook. Are you planning support for other templating engines?

[milansingh]

What will happen to the pendingFormSubmit ? The last li is displayed from pending form data. And when actual data submits it is replace through map…. What if errors happen in network? Wouldn’t’ we see jerk ui to remove last li?