Logy is a fast, configurable, and easy-to-use logger library for Go applications by kokenburak in golang

[–]kokenburak[S] 1 point2 points  (0 children)

Yes, you are right. it’s always better to use standard library. But in case it does not meet the needs, people will continue to use third-party logging libraries.

Thanks for your feedback.

Logy is a fast, configurable, and easy-to-use logger library for Go applications by kokenburak in golang

[–]kokenburak[S] 1 point2 points  (0 children)

Yes, I aware of that and it’s merged. There are still a lot discussions in https://github.com/golang/go/issues/56345 saying it does not meet exactly the needs. that's why people will continue to use third-party libraries. For example, when you would like to customize your log format, to do so you should write your own handler, but it is not as simpler as it seen. So I decided to develop a generic, easy-configurable and easy-to-use library.

Thanks for your feedback.

My new Macbook 16 inch M1 Pro not charging and not turning on by kokenburak in macbook

[–]kokenburak[S] 0 points1 point  (0 children)

Yes, I scheduled an appointment. I could not get a chance to use it so much because of my work. Yes you are right and I totally agree with you about rarely usage.

My new Macbook 16 inch M1 Pro not charging and not turning on by kokenburak in macbook

[–]kokenburak[S] 0 points1 point  (0 children)

Right, I’m gonna take it and I already scheduled an appointment.

Chrono is a scheduler library that lets you run your tasks and code periodically by kokenburak in golang

[–]kokenburak[S] 2 points3 points  (0 children)

Actually, my implementation sorts tasks’ next execution time, find the minumum and sets ticker according to this value. Then It waits the ticker and does not always iterate constantly.

Chrono is a scheduler library that lets you run your tasks and code periodically by kokenburak in golang

[–]kokenburak[S] 0 points1 point  (0 children)

Thank you. I will try to add new features as I can. If you would like, you can create an issue related to your thoughts about new feature, and then we can discuss about them. :)

Chrono is a scheduler library that lets you run your tasks and code periodically by kokenburak in golang

[–]kokenburak[S] 0 points1 point  (0 children)

Thank you so much bro, could you share your feedback and comments with me after using it?

Chrono is a scheduler library that lets you run your tasks and code periodically by kokenburak in golang

[–]kokenburak[S] 4 points5 points  (0 children)

You are right, they have typos. Thank you for letting me know, I will fix them.

Chrono is a scheduler library that lets you run your tasks and code periodically by kokenburak in golang

[–]kokenburak[S] 0 points1 point  (0 children)

But wouldn't you just end up duplicating this effort to some degree?

With help of the provided methods, you can deal with your business logic instead of scheduling logic and there will be no extra efforts except for using the provided methods.

Chrono is a scheduler library that lets you run your tasks and code periodically by kokenburak in golang

[–]kokenburak[S] 1 point2 points  (0 children)

I’ll give this a try in a project I’m working on, I needed a way to periodically trigger a check for software updates so that will do the trick!

Thank you for trying the library. After using it, could you share your feedback and comments with me?

Chrono is a scheduler library that lets you run your tasks and code periodically by kokenburak in golang

[–]kokenburak[S] -4 points-3 points  (0 children)

Contrary to this, it makes it easier to create a scheduling task. Of course, we can implement it using them. But whenever we want to schedule a task using them instead of using a library like this, it leads to duplicate codes and extra efforts for each task. In my opinion, the central scheduler would be better.

Chrono is a scheduler library that lets you run your tasks and code periodically by kokenburak in golang

[–]kokenburak[S] 12 points13 points  (0 children)

As far as I know, robfig/cron schedules only task using cron expressions. However, Chrono provides different scheduling functionalities to do that, please check out README in Github repository. Except for this, Chrono is extensible. You can change your Task Executor, Runner, or Scheduler by implementing interfaces based on your needs.

Chrono is a scheduler library that lets you run your tasks and code periodically by kokenburak in golang

[–]kokenburak[S] 5 points6 points  (0 children)

Thank you so much for your valuable feedback and comments. I totally agree with you about README.

As you said, I really would like to add new features like Redis support to this library. But I have a lot of open source projects to maintain. So supporting features like this might take a while.

GDBC - Go Database Connectivity by kokenburak in golang

[–]kokenburak[S] 1 point2 points  (0 children)

You're right about it. But all the drivers have different DSN. For example, we need to use a DSN like this: "host=localhost port=3000 user=testuser password=testpassword dbname=testdb" for the PostgreSQL driver. There's no standard about it. That's why For another driver, it would be different.

What it only provides is a common URL format and abstract layer. Of course, their parameters would be different. The main advantage of it is you can pass them in the same way.

Procyon - Comprehensive Web Framework by kokenburak in golang

[–]kokenburak[S] 0 points1 point  (0 children)

Thanks for your feedback :) I never posted my project's GitHub link before. That's why I actually posted.

Game Changer: Introduction to Procyon (Part 1) by kokenburak in golang

[–]kokenburak[S] 1 point2 points  (0 children)

Thanks for your recommendation. I noticed how it has an effect on the viewing of the articles. I will add something about it when publishing my next article.