This is an automated email from the ASF dual-hosted git repository.
harbs pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-docs.git
The following commit(s) were added to refs/heads/master by this push:
new 524e6c7 another edit
524e6c7 is described below
commit 524e6c7e5fd89af3808e698e15ff818ec8c38daf
Author: Harbs <[email protected]>
AuthorDate: Thu Dec 30 12:50:29 2021 +0200
another edit
---
features/modules.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/features/modules.md b/features/modules.md
index b111de4..7f6e94a 100644
--- a/features/modules.md
+++ b/features/modules.md
@@ -47,7 +47,7 @@ There is an example for [Basic](component-sets/basic) UI Set
[here](https://gith
Proper use of modules can help maintain _"separation of concerns"_ which helps
keep you from writing _"spaghetti code"_. If only the code in one module
changes, only that module needs to be recompiled. And if that code isn't needed
to show the first screen, then the application might start up faster if that
module is loaded only when it is needed.
## Why not modules? {#why-not-modules}
-In Flash, modules was very important. That's because application size and
compilation time grew very rapidly. Flash applications were slow to load and
modules were a good tool to help with that. The aggressive use of PAYG in
Royale along with browser features for loading Javascript made Royale
applications much smaller and load times generally nearly instant. In many
(most?) use cases of modules for Flex applications in Flash, Royale renders
them unnecessary.
+In Flash, modules was very important. That's because application size and
compilation time grew very rapidly. Flash applications were slow to load and
modules were a good tool to help with that. The aggressive use of
[PAYG](features/payg) in Royale along with browser features for loading
Javascript made Royale applications much smaller and load times generally
nearly instant. In many or most use cases of modules for Flex applications in
Flash, Royale renders them unnecessary.
Using modules can make development more difficult and in many cases cause your
application to actually load _**slower**_. Before using modules, consider the
following points:
@@ -56,6 +56,7 @@ Using modules can make development more difficult and in many
cases cause your a
* Network speeds have improved drastically over the last 10 years so many of
the considerations have changed.
* JS caching in the browser is much better than Flash caching was. You can
setup your deployments so your application resource files (js, css, etc.) are
cached for 30 days and when deploying a new version, the cache is automatically
invalidated.
* Using modules limits how aggressively code can be minified. Improved
minification helps both in deployed code size and speed of code execution.
+* There is a lot of code duplication in modules and the total size of your
application will often be many times larger if you use modules. Often, the
actual code that would be added to the main application is negligible.
* A large part of application and module size in Flash was caused by embedded
assets. In HTML, assets are stored externally and only loaded when/if they are
actually needed.
## Compiling modules
