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 bae1be6 small edit
bae1be6 is described below
commit bae1be6b2949d2e54f30cdd044bbce564bc98359
Author: Harbs <[email protected]>
AuthorDate: Thu Dec 30 00:15:40 2021 +0200
small edit
---
welcome/what-is-royale.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/welcome/what-is-royale.md b/welcome/what-is-royale.md
index d49d8dd..9d33c26 100644
--- a/welcome/what-is-royale.md
+++ b/welcome/what-is-royale.md
@@ -35,7 +35,7 @@ Royale compiles ActionScript for multiple run-times. The
ActionScript compiler i
You might compare Royale to Webpack, ES Build or Parcel. Royale compiles your
app both for debugging and into a single JS file for deployment.
## It's a toolbox
-Royale has a huge library of functionality. Because Royale is very smart about
only including in your application parts actually used, Royale is able to
include a very large library of functionality.
+Royale has a huge library of functionality. Because Royale is very smart about
only including in your application parts actually used, Royale is able to
include a very large library of functionality without effecting application
size.
## It's an ecosystem
Royale does not use npm. That's both an advantage and a disadvantage. npm give
you access to a huge amount of code. That's both a blessing and a curse. If
you've ever tried to stay on top of auditing npm modules and keeping them up to
date, you know it's a nightmare of dependencies. Even knowing what your code
depends on is very difficult with npm.
