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

Publish decaffinated? #2

Open
fumbleforce opened this issue Sep 3, 2018 · 1 comment
Open

Publish decaffinated? #2

fumbleforce opened this issue Sep 3, 2018 · 1 comment

Comments

@fumbleforce
Copy link

Hey. I'm using the currently published version, but I see you have also added some commits after that which removes CS completely. Any reason you haven't published those?

@SimonSimCity
Copy link
Owner

SimonSimCity commented Sep 3, 2018

The reason currently is that simply removing CoffeeScript was not reason enough in my eyes 😄
It doesn't really help anything but the deployment time and the time of a rebuild for a development environment.

My idea was to implement some other features as well and to cover them by unit- and functional tests. Furthermore I also wanted to know if it's worth it (see: https://forums.meteor.com/t/jobs-worker-in-meteor-steve-jobs-vs-meteor-jobs-vs-meteor-workers-vs-synced-cron/44578).

As of now, I'm focussing on other parts on my project, but I'll keep you updated and also post stuff about best-practices and why as I have time to improve the implementation I have in my project.

If you have any code-contributions aside of this, please feel free to help me cleaning up the code-base. There's tons of code which only is needed because this wasn't started in plain javascript ... Please keep your changes in small readable chunks and don't expect me to accept a replacement of the full code-base in one commit - and (I think) you'll understand why 😉

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