pythonist

It is a big contribution to opensource it. The work behind the data is huge and extremely significant. Thanks Troy!

The service implementation that I did with a bit different technical requirement is here https://github.com/janos/compromised as an alternative. It is actively used behind the NewReleases.io service.

It focuses on extremely low memory usage and supporting very high request rates on a commodity hardware, cheap vps or cloud instances.

I must say that I also relate with the author and would add that making things just for fun or your own curiosity or even need, can be beneficial to others too, directly or indirectly. With every toy project, new skills are acquired. Useful or not, you cannot now at the time, but I can say that if I did not make toy projects, I would not have jobs that I had and some of the projects that others also find useful, like https://newreleases.io, would not exist.

Of course, I am affiliated, but also using it for Alpine Docker image notifications.

Given the popularity of Alpine it is important to update images as soon as possible given how many significant updates are there. Services like [1] help a lot for that...

[1] https://newreleases.io

Tailwind released 2.0, but it is a result of constant work releasing new versions gradually and listening to the users. This is a very active project and it is good to keep an eye on new things https://newreleases.io/npm/tailwindcss. Actually, 2.0.1 is out already. :)

It is a manual update, replacing, for now. Automated update would be a good improvement, for sure. It is not there just as it is a recently started project. Also updates are not so frequent.

Or if you do not and you like official releases, you can use some of the services like https://newreleases.io to get notification and install using official installer.

Not a bookmarking site per se, but has many notifacation options for developers on projects that they track https://newreleases.io.

I am implementing organisations feature to https://newreleases.io, which is a software release tracker service.

Release notifications for Software engineers https://newreleases.io/

Thank you for making it!

And also very important to watch for changes of your dependencies, as they can be quite dynamic. A single review too early or too late in the development process may have misleading results. Watching for commit changes is too time consuming, so watching for releases is a bit easier, especially if you use something like https://newreleases.io or other similar sites.

https://newreleases.io

The stack can be much boring, simple and easy to maintain. Golang helps a lot for that.

For example https://newreleases.io/

- Go with embedded databases for web services

- Vue.js for frontend

- Nginx just as there are other sites on the server

- Prometheus/Grafana for monitoring

- Gitea for code hosting and some automation

- Bind9 for DNS

- Debian

ASGI, finally! I was so happy to see the first alpha newreleases.io notification for version 3.

I am wondering that also, scheduler is of most importance.

Go is such a joy to work with.

Very cool! Congratulations!

I was happy to se new Rails notification from newreleases.io today.

This will be very neat just as GitHub user experience is so far. Centralization is a questionable, but it looks like that the community values much more the convenience than decentralization and privacy. In any case, it is excellent to have multiple choices beside other registries. I hope that other services like https://newreleases.io will catch up and support this registry as well. But, maybe this would even make them obsolete and everything a bit more centralized.

and https://newreleases.io to support at least https://crates.io...

Thank you very much for Bleve! It was useful for me on a few projects. And, do not be afraid to break things in the future major version, modules are handling that nicely.

So you do not need it as you do not want to use it too soon. That is cool. Others may need docker image release aligned with regular release, and I think that there is nothing wrong with that. Especially for the people that are trying to contribute to Go by testing beta and rc releases.

I think that the question is, why wouldn't you? There are already a lot of work and testing done on projects that depend on 1.12 features, but using beta and rc releases. Final 1.12 version would just confirm that everything works, but without docker image, testing on staging infrastructure is delayed even the final version is out.

This is why I have https://NewReleases.io configured to track both Go GitHub releases as well as golang image tags on Docker Hub.

For some organizations unpredictable docker image releases are considered unreliable to use at all. Sometimes the image is updated the same day, sometimes after a few days, earlier even after more than a week.

The gap between developer tools and infrastructure support for them should be as small as possible this days. It's 2019.

But sometimes golang docker images are late for a few days which is very annoying if your ci build pipeline depend on them. It would be great if Go team would be able to update docker images as well. And I am sure that this automation would not be so hard to do.

Maybe they can use https://NewReleases.io to track Go releases.

- Frontend: Vue with TypeScript and Bulma or TailwindCSS

- Backend: Go (no framework) with monolith first approach with well defined internal logical interfaces that can be easily implemented as external services when they need to scale (session service, user service, notification service, slack integration service...)

- Storage: embedded BBoltDB or Badger, separate db for every logical service and PostgreSQL data structure is very very complex

- Services communication: Protobuf with GRPC

- Monitoring and alerting: Prometheus with Grafana

- Log aggregation: simple central rsyslog, indexing when really needed

- Editor/IDE: VS Code

As less operational maintenance is needed, the easier is to live with your creations.

Example: https://newreleases.io

YTBmp3 https://www.ytbmp3.com is built completely with Go. Autoscaling cloud instances based on load with a custom scaling solution is also written in Go. It handles very long running requests on streaming transcoding and compressing. Go's net/http is exposed to the internet with great results which adds to infrastructure simplifications, graceful reloading (important for long running requests). Go allows so much infrastructure simplifications that there is not even a single container involved. :)

A very fine example of such site http://www.jeffbridges.com/.

I completely agree. Go made me enjoy programming again.

Good points, and also correct answer. Identity is hard to question. But when you try Go without prejudice, it's just fun (and productive) afterwards.