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

Build system #75

Open
BambiHaber opened this issue Jan 15, 2022 · 1 comment
Open

Build system #75

BambiHaber opened this issue Jan 15, 2022 · 1 comment
Labels
codebase question A question about the GridSound's codebase

Comments

@BambiHaber
Copy link

Hello,
I was wondering if there's a specific reason for not using node or a packager to build the system? also, I have noticed the UI is declarative not using any kind of template engine.

Was this a choice by design?

@mr21
Copy link
Member

mr21 commented Sep 11, 2022

Hi 👋

Sorry for this 9 months delay, your question is quite related to this one:
#56

The fact that there is no packager is because from the begining i knew i would not use any package or react or anything in that vibe. And from the begining of my coding life im used to use Makefile to compile programs, then i like the idea to maintain your own file order by hand to be compiled how you exactly want.

And finally after all these years i have found a good way to use the uglyfier in a smart way to also mangle all the public stuff, then even for reducing the production code i don't feel the need to use something like webpack or anything than just a basic script shell.

@mr21 mr21 added the codebase question A question about the GridSound's codebase label Sep 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
codebase question A question about the GridSound's codebase
Projects
None yet
Development

No branches or pull requests

2 participants