backend-server VS eaf-linter

I’ve been working on eaf-linter for about a few days now, and it already has 6 stars and 2 forks. My other project that I've been working on, the Backend Server, has 14 stars, 9 forks, and nearly 10 outside contributors. That might not sound like a lot, but both of these projects are only about a week old.

I’ve been working on my open-source backend server for about a week now, and it already has about 12 stars, 9 forks, and nearly 10 outside contributors. That might not sound like a lot, but the project is only a week old and it isn’t a package or anything that can be used by outside people.

Here was the project if you want to check it out

I’ve been working on building a non-profit, open-source organization for a while now and we have gotten to a solid point in the backend code. We have authentication, an event and rsvp system, profile picture generator, etc. If you want to check it out, you can here.

If you want to check out the code for the project, it’s all publicly available here. Make sure to star the repository!

I decided to drop everything that I was doing and build a really simple API for duck jokes. Right now the API has a couple of jokes, but we need some more, so if you want to submit some, you can respond to this issue or you can just drop a pull request on this repository.

Secondly, you need easily understandable features. If you look at my newest repository, eaf-linter, you will see that all of the features have a simple headline and they link to a new page. This is very important. If your feature can link to a more in depth description of the feature, it will increase the confidence that the possible contributor has in your project.

I'm working on a linter right now, and one of the requested features for it was code duplication detection. I made an issue for it already, but I need to start working on it. And, that's where my question lies.

So, I’m getting rid of it. My entire linter system, code grading, beautifier, etc. is gone. And, I’m replacing it with my own solution- if you want something done right, you have to do it yourself.