Hacker News Reader

Comment by annexrichmond | Hacker News Reader

One suggestion, as someone who is an Infra engineer and doesn't know frontend too well anymore, the first step in the demo asks me to "Select your React platform"

I don't know what that means, and what the implication of choosing between Vite, Remix, or Next.js -- it's meaningless to me.

View on HN

Oops, you're absolutely right. The frontend ecosystem is quite complex, and the entry barrier for engineers working in other roles is getting a little higher every day. Perhaps by default, Vite should be used, and Remix or Next.js alternatives should be shown for advanced frontend developers. Thank you so much; we will definitely improve this area.

Something else people may want to consider is the community health. Vite, Remix and Next.js are all extremely healthy, but Next.js is currently in a league of its own. You can see the community information for all three at:

https://devboard.gitsense.com/vitejs/vite

https://devboard.gitsense.com/remix-run/remix

https://devboard.gitsense.com/vercel/next.js

The only other project that I've seen with greater engagement than next.js on GitHub is Microsoft's vscode.

Full Disclosure: This is my tool.

ha-ha, brother, I feel you. Infra engineer (VP last position) and built an app with Refine. I was exactly in your position not a long time ago. I tried to choose "The Best Framework Ever" and made a lot of mistakes, and at the end, if you don't know frontend go with the flow: React + Next.js. Not because they are Best Ever, but because the majority of content online is dedicated to these frameworks. StackOverflow, ChatGPT, a friend who speaks frontend, etc.

I did some work as part of my consultancy, had data left and decided to try my hands at frontend. Oh, boy, I think it was a mistake, but it was a lot of fun, will do again. https://cloudprice.io

The deceptive part of these types of frameworks is this: on the first day, you think it will solve all your problems. On the second day, you're happy, thinking about how much you've sped up because you chose this framework for your project. On the third day, you have a custom need, and you research how to do it within that framework. On the fourth day, you hack the framework to make it flexible. On the fifth day, you say, 'Why didn't I start from scratch myself?'

Our goal and motivation in developing refine is to ensure that the developer continues to feel the way they felt on the first day, even on the day they finish the project and begin to maintain it.

And on the sixth day you have uncontrollable flashbacks to the days of using jquery to manage your application state as a singleton in the global scope and you die a bit inside ;).

why no one came up with the idea of reactive jquery i don't know. or, may be someone did?

literally this. but to the benefit of refine.dev i should say that you made the framework extremely easily hackable, at least where lame me wanted to hack it. your data backend didn't work with my rest api, i've asked on discord and someone said: hey, it's actually in the docs, you just copy our default implementation into your project, import it, make sure it works as before and then hack it as your own code. a productized hack, i'd say.

If I understand correctly, using 'swizzle' to customize the data provider is not a hack for refine, but an expected behavior. But I'm curious about the conversation; could you possibly share the link?

the ease looks like a hack, since it's documented it's not a "hack as in workaround". in my vocabulary "hack" is a compliment, not a derogative. i grew up on jargon file.

I tried to use the site you mentioned at the end of your post, but when I tried to add an ec2 instance (searching for ec2 resource) I got a 500 error "Error talking to backend server: 500".

hm, indeed. thanks! interesting, i need to investigate. i just redeployed the same code to the cloudflare worker and it worked.

Reply on news.ycombinator.com