I read this quote on one of the web pages:
If you are writing a large application, consider its division into a set of applications and services. Smaller applications load faster and use less resources. Creating a set of applications, content providers and services makes your code more open for inclusion in other applications as described in the "Use and Use" section of the tip.
It's true? What is the thumb rule for app size?
Well, technically this has no answer best.
best
But I would go with many small applications:
, , . :
, .
Source: https://habr.com/ru/post/1748262/More articles:daemonize perl process - perlМатематический эквивалент инъекции Ruby - wolfram-mathematicaIs there an easy way to get the total page response time in ASP.Net? - c #Using Links in PHP - parameter-passingIs a `super` local variable? - objective-cИспользование Doctrine для абстрактных операций CRUD - designFacebook, as on demand, content scraper - phpWPF Combobox binding: unable to change selection - c #Is it verified that the iPad cannot create special wifi networks? - networkingHow can I use CSS pseudo-classes with GWT UiBinder? - cssAll Articles