mani is a CLI tool that helps you manage multiple repositories. It's useful when you are working with microservices, multi-project systems, many libraries or just a bunch of repositories and want a central place for pulling all repositories and running commands over them.
You specify repository and commands in a config file and then run the commands over all or a subset of the repositories.
Building an editor to create, view and edit vim color themes in your browser. Half-baked app architecture with a self-built redux and event emitter and code structure, gets the job done though.
Also building mani, a tool that helps you manage multiple repositories. It's helpful when you are working with microservices or multi-project system and libraries and want a central place for pulling all repositories and running commands over the different projects. You specify projects and commands in a yaml config and then run the commands over all or a subset of the projects.
It depends, in some regards it's kind as the results are seen immediately (is a path bringing more or less compilation errors, etc), whereas as in others it takes time to see if the decision you made was good or bad (did the architecture you chose scale).
Could be perhaps because Angular 1.x is not going to be maintained in the next 2 years so there are some security issues with that. And obviously, effort was not wasted since people used the application during those 2 years and you hopefully learned some stuff.
I tried logging in but it says there doesn't exist a team to join. So when I try to create a new team using gmail, it asks for my connections.
I also assume it won't send emails on its own, but still it's information that shouldn't be necessary for me to share in order to join your application.
Why do you need the permission "View your contacts" (Google Contacts) when signing up? I would sign up and try the product but I'm not going to disclose all my contacts.
I think the down votes are due to you and the previous person attacking the poster instead of his post. I think you present some valid points and they would come through a lot better if you focused on them instead of attacking the poster.
Discarding previous knowledge where it is applicable and simpler is obviously unwarranted. Similarly to how we utilize Newtons laws within a lower energy and mass range, we should prefer the simpler equations where they make sense. However, I'm not sure that a for loop is actually simpler than map reduce as it depends on the context. Who is reading your code? How complex is the code inside the for loop? What kind of problem are you solving? The vocabulary associated with functional programming is better equipped to handle mathematical expressions than imperative code and in this case, simpler.
In essence; adding complexity for the sake of complexity or to come of as intelligent is bad...
You specify repository and commands in a config file and then run the commands over all or a subset of the repositories.