3 ms·

I think they give a very good answer in their own blog: https://remix.run/blog/not-another-framework https://remix.run/blog/not-another-framework Summary: Lear

I think they give a very good answer in their own blog: https://remix.run/blog/not-another-framework https://remix.run/blog/not-another-framework Summary: Learn Remix, Accidentally Learn the Web > It is an explicit goal of ours to design APIs that are high-level enough to help you just get the job done, but close enough to the web to backfill your fundamental knowledge of Kung Fu the web. That's something I really like about remix.

h4ch1 3y ago
tbh I am not sure I agree that's a selling point, how much can you abstract away till people have no clue what's happening internally and are lost when usecase X is more complicated than simple CRUD. If I want to learn web fundamentals I SHOULD learn web fundamentals, not through an API that makes it seem like magic, because it's not transferable to other frameworks/platforms. This creates problems for new developers as well, who in this day and age learn frameworks instead of the underlying tech, and then bring that mindset to other domains. I've had so many React devs being unable to work with say a Svelte or a vanilla HTML/TS applications because their web development skills are actually React skills. For ex this line here "When you learn how to handle requests and send responses in Remix, you're actually learning the Web Fetch API that's in the browser already." I'd rather just use fetch so I know explicitly what I am doing.