If I got you right, it is exactly what we are trying to do: so you define stuff in Wasp, but then you can use React to implement stuff and there is an API between Wasp and React, so you can import things you defined in Wasp into React and use them there. And you can also import your React stuff in Wasp and use it there, so it goes in two directions really.
Right now it is React and Node, but we want to add more of it: this means not just React but for example also Vue and Svelte. And for the backend, maybe even other language next to Node -> for example Python or Go. That is something we could do. However, for now plan is to focus on React / Node combo and get it working really well and then we can expand :).
Graduated in Digital Media M.Sc. now developing the next generation of educational software. Since a while I develop full stack in Javascript using Meteor. Love fitness and Muay Thai after work.
Makes total Sense from a strategic pov. You got me right - having Bindings to several layers of Frontends, Database etc. would be awesome. I could even think of an interfsce to RoR or Meteor, because from my POV the DSL Just defines the general Domain concepts and does not necessarily know how these concepts are implemented and thus you could define connectors for anything to implement them, right?
In theory yes! It really depends on how much we detach the DSL from the implementation. Right now we are not detaching us as much as we might possibly like :D, just because it would slow us down a lot - instead we are going with relatively coupled approach, in the sense it is somewhat coupled to React / Node. But, once we get that working, we will look into generalizing it.
When speaking about frameworks like Meteor or RoR: we could have generators that based on the DSL generate stuff in Meteor or RoR. Right now we have just one generator: React/Node/Prisma generator.
However, using Meteor and RoR as building blocks that connect/interface with DSL is not the way we are going right now, because DSL we are building right now is about the same level of expresiveness as is Meteor and RoR, so blocks should be lower-level (like React, Node, Prisma, ...). I think Meteor and RoR could become valid "blocks" if we raise the abstraction of DSL to the level of e.g. microservics and similar, which we are not planning for now.
I might have explained this badly or misunderstood you, please let me know if this makes sense or not!
Graduated in Digital Media M.Sc. now developing the next generation of educational software. Since a while I develop full stack in Javascript using Meteor. Love fitness and Muay Thai after work.
If I got you right, it is exactly what we are trying to do: so you define stuff in Wasp, but then you can use React to implement stuff and there is an API between Wasp and React, so you can import things you defined in Wasp into React and use them there. And you can also import your React stuff in Wasp and use it there, so it goes in two directions really.
Right now it is React and Node, but we want to add more of it: this means not just React but for example also Vue and Svelte. And for the backend, maybe even other language next to Node -> for example Python or Go. That is something we could do. However, for now plan is to focus on React / Node combo and get it working really well and then we can expand :).
Makes total Sense from a strategic pov. You got me right - having Bindings to several layers of Frontends, Database etc. would be awesome. I could even think of an interfsce to RoR or Meteor, because from my POV the DSL Just defines the general Domain concepts and does not necessarily know how these concepts are implemented and thus you could define connectors for anything to implement them, right?
In theory yes! It really depends on how much we detach the DSL from the implementation. Right now we are not detaching us as much as we might possibly like :D, just because it would slow us down a lot - instead we are going with relatively coupled approach, in the sense it is somewhat coupled to React / Node. But, once we get that working, we will look into generalizing it.
When speaking about frameworks like Meteor or RoR: we could have generators that based on the DSL generate stuff in Meteor or RoR. Right now we have just one generator: React/Node/Prisma generator.
However, using Meteor and RoR as building blocks that connect/interface with DSL is not the way we are going right now, because DSL we are building right now is about the same level of expresiveness as is Meteor and RoR, so blocks should be lower-level (like React, Node, Prisma, ...). I think Meteor and RoR could become valid "blocks" if we raise the abstraction of DSL to the level of e.g. microservics and similar, which we are not planning for now.
I might have explained this badly or misunderstood you, please let me know if this makes sense or not!
Not Bad at all, makes all Sense. Thank you! Will keep an eye on this!