Would love to see this integration with php (Symfony in particular but bare php will do it). This sounds very good, the frontend and backend api issue has always been a headache to solve.
That's called RPC, or SOAP, and pretty much everyone hates them. Cross language solutions need to be more verbose because everything must be described. Maybe an opinionated approach could simplify those solutions, but still I'd prefer a data only transfer layer; sure, the typing system is poor, ma probably a solution using protobuf could be the answer.
Interesting approach, though!
Possible? Sure (it's my first language, I know what I say). Useful? I don't know, it seems to me that the logic shared between two projects written in two languages isn't too much at the end.
While I'm intrigued from a conceptual point of view, I don't think I'll use this approach for a production project.
Would love to see this integration with php (Symfony in particular but bare php will do it). This sounds very good, the frontend and backend api issue has always been a headache to solve.
That's called RPC, or SOAP, and pretty much everyone hates them. Cross language solutions need to be more verbose because everything must be described. Maybe an opinionated approach could simplify those solutions, but still I'd prefer a data only transfer layer; sure, the typing system is poor, ma probably a solution using protobuf could be the answer.
Interesting approach, though!
I haven't used PHP for years, but I am pretty sure it is possible to port Layr to PHP in an elegant way.
Possible? Sure (it's my first language, I know what I say). Useful? I don't know, it seems to me that the logic shared between two projects written in two languages isn't too much at the end.
While I'm intrigued from a conceptual point of view, I don't think I'll use this approach for a production project.
What about all the boilerplate you can avoid by removing the web API?