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 ;).
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.
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.