Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Google Closure Compiler to improve performance #1

Open
gDanix opened this issue Jun 13, 2016 · 1 comment
Open

Using Google Closure Compiler to improve performance #1

gDanix opened this issue Jun 13, 2016 · 1 comment

Comments

@gDanix
Copy link

gDanix commented Jun 13, 2016

Hi!

I was thinking on using Google Closure Compiler to minify and improve performance (which is a negative point of JavaScript) of jsEO algorithms.

We can start testing if the speed gain is worth the time invested and, if so, write an script to auto-minify all the source code (maybe using Maven?)

@vrivas
Copy link
Owner

vrivas commented Jun 13, 2016

Hi!

Any help is welcome, so thanks!!

Currently, jsEO is still under development, so every time I execute it, I need to trace the algorithm in the web-browser. Thus, it is still important for me to have the code "as it" running in the browser.

In any case, I think we could test Google Closure Compiler over https://github.com/vrivas/evrbf_dcai2016, that it's one of the concrete use of jsEO. You can test it in its current state accessing to http://vrivas.es/dcai16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants