[README] About [Implementations in other languages] section #2887
I realize implementations in other languages are a bit of many things mixed in.
I identify different sections this should be split in:
Those 5 aims to be compliant with pugjs specifications and support native PHP/Java/Python/C# objects (no serialization, so object methods can be called from the templates). And there are written in their target languages.
Other language equivalent:
Those 3 have really different syntax. Scala is a bit closer but has different operators and include/extend different system.
I also think larpug should not appear alone on the top of other languages implementation, it's more like an pugjs-to-laravel adapter for me. And if we talk about framework adapters, we should provide some guidance to the user to help him picking the package he needs, explain the different approaches and give him a larger view of existing solutions.
So the if you think it's relevant, here is what I propose to do (I can do the pull-request):
What do you think of it?
The text was updated successfully, but these errors were encountered:
Finally a pull-request at #2928, some little changes since I opened this issue, I moved Ruby and Rails implementations in their framework/language sections and I also CMS plugins with wordless that enable Pug (among others) and I hope some other CMS could implement it (Maybe October CMS, I will try to take a look).
So to be discussed, adjusted if needed.