Replies: 1 comment
-
If somebody wants to work on Oxpecker.React and it's Fable plugin, I'll approve that, not going to work on it myself. My initial idea was to create a new framework (similar to Sutil), but it so happened that Solid already is a framework that fulfills my needs, so I just created bindings not to reinvent the wheel
I don't know, I currently see them as a competitive choices to make.
It's possible to extend Oxpecker.Solid to accept JSX.Element (used in Feliz.JSX.Solid) as a child or parameter, however I don't think there are many projects using Feliz.JSX.Solid, so I don't see benefits of doing that (not very trivial) work |
Beta Was this translation helpful? Give feedback.
-
idea: suggest if wanting to make FE side code appetible, to target also React/Next.js as those are kind of relevant frameworks today,
this is why Fable.React and Feliz exist and i think providing a common template/integration with Feliz/React would be very welcome useful?
i understand this new CE/DSL is smarter/better than list feliz DSL, but then i think having an adapter making the 2 compatibles would be great for extending existing Feliz or Feliz.ViewEngine apps, and especially for apps using Fable.React
ReactElement
as output?https://hygraph.com/blog/javascript-frameworks
https://www.statista.com/statistics/1124699/worldwide-developer-survey-most-used-frameworks-web/
Beta Was this translation helpful? Give feedback.
All reactions