PhotinoX #394
Replies: 1 comment 1 reply
|
Thanks for sharing the project! I have been aware of PhotinoX for a while and it also looks like an impressive fork of Photino. From the looks of it PhotinoX also seemed to heavily work on fixing a lot of open issues of Photino, and reworked the entire native system to work with an "application lifetime object" to resolve some issues Photino had from the start, which honestly looks like a very good architecture approach for the original Photino codebase. With Infiniframe, I went in a different direction and made this applicaiton lifetime object something more implicit in the native code, as I also rewrote a lot of the native codebase. As with every project, each projects has its up and downsides. For example, I choose to implement all Photino repositories into one to ease development, whilst PhotinoX choose to keep with the original multi repo structure with an PhotinoX.All repo ontop. I choose to fully split out the native JS/TS codebase, whilst I think PhotinoX also kept that as is. I don't mean to say these are bad choices at all, both roads are valid. For example, I choose to bring in some outside dependencies to make certain things easier, especially built in logging. Some devs might see this as a downside, I see it as an upside. One thing I am curious about is how PhotinoX tests its codebase, as I had to pull a lot of weight comming up with a somewhat decent approach to making the codebase testable, and workable in CICD workflows. |
Uh oh!
There was an error while loading. Please reload this page.
I just noticed this project: https://github.com/ivanvoyager/PhotinoX Wanted only to post it here. Maybe some parts of it can be used - especially the form the native layer? Or maybe a collaboration make sense?
All reactions