Our great sponsors
-
I contribute to OSS as part of my job on the regular. The company is good about contributing upstream, signing CLAs, and all that. We still work against private forks for two main reasons: 1. Some changes that we need are not accepted by maintainers based on philosophical or architectural reasons that we can’t otherwise work around. You’re beholden to then unless you publicly fork the repo which has other legal/PR overhead for the company and OSS political implications. 2. Maintainers in the past have taken down repos, renamed repos, or changed the licensing on repos that have left us in a lurch. We always build against our own private forks because we need predictability and can’t be beholden to some other party for business continuity. We sync them down from the public upstream at our leisure.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Related posts
- Renaming public Go modules
- Observing AWS Lambda with Golang and Datadog
- go-coffeeshop - A practical coffee shop application event-driven microservices built with Golang
- [Summary] Is there full-fledge log library similar to Java's Log4J? r/golang
- GoLand 2022.1 EAP starts with: new сode completion options for generics, fixes for more than 50 generics-related issues, string formatting support for testify/assert functions, and more! Join the EAP!