many external dependency packages used only in one place,please realize them by framework-self instead of using external packages
many external dependency packages used only in one place,please realize them by framework-self instead of using external packages. or as an optional package. such as:
1.inquirerpy
2.multiprocess
3.rustimport
4.watchdog
Hey @ockan ,
I don't think I understand this issue. Could you explain a bit more please?
@k4976 , do you understand this?
for example, the first,'inquirerpy' only use in the 'cli.py',and use frequency is just once. in 'cli.py',there is
from InquirerPy.base.control import Choice
from InquirerPy.resolver import prompt
etc.
Why I suggest reduding the number of dependency package reduding the number of dependency package can make the maintenance of the framework is easier,because of no need to trace more many extenal packages,and not restricted by the extenal packages.when the extenal packages change the api,the framework is forced to follow it.if the extenal packages is discontinued,the framework is affected.
@ockan Yep, we can do but we are not using in core Robyn It's just in limited places only And mostly they all gets updated rarely bcoz they are much mature So their syntax change is very much less often
We will try coding all the functionalities in rust, so we don't need external dependencies when Robyn gets mature enough that we don't have much to work on
@k4976 @ockan , I don't understand the benefit it will provide us. They are not bottlenecks in terms of performance and also quite well maintained.
I am sure we will be able to handle the breaking changes should these packages push anything but why do you want to take ownership of more code?
@sansyrox If we have to decrease the number of dependencies It's all upto you
Why I suggest reduding the number of dependency package reduding the number of dependency package can make the maintenance of the framework is easier,because of no need to trace more many extenal packages,and not restricted by the extenal packages.when the extenal packages change the api,the framework is forced to follow it.if the extenal packages is discontinued,the framework is affected.