On 24/05/2016 19:34, wb wrote:
> I tried to port my Pyjs project to Brython recently, and it failed
> because Brython was terribly slow.
I though that they had recently improved the performance, but apparently
not enough :-(
> 2. Python source code is not exposed to public
This is no good argument to me. You are free to pre-obfuscate and minify
the code if you want.
> 3. Pyjs is designed to support MVC(Model-View-Controller)
This is an advantage and an inconvenient at the same time. Although the
graphical library is nice to have, I think that it is sometimes better
to dive in your HTML and CSS. One main problem of Pyjamas is IMHO that
it does everything with tables and this is not flexible at all. To
rewrite the library for producing div using flexbox instead of tables
would probably be a nice step.
Anyway we can talk about this and that but the main issue is that nobody
is taking care of pyjs anymore, and especially in web dev it is
difficult to maintain and improve your stuff without using new
techniques. For example, the output that is produced for each target
browser is probably full of hacks but how useful are they if they have
been made for a browser version that nobody uses anymore (not the case
yet, but it will eventually be)?
Here are a list of issues that we encountered with Pyjamas, some are
specific to the project but you can see some incorrect behaviors with
decorators, inheritances and other stuff that are annoying us:
Who will fix these issues? I unfortunately can't. We have been hoping
for long to see a pyjs/pyjamas relaunch but it's not going to happen,
that's why I prefer to find a more or less similar project with a larger
and more dynamic community.