real_joschi

Correct URL is https://staan.ai/

I think the question is rather gitlab.com vs. self-hosted GitLab and Codeberg vs. self-hosted Forgejo.

They also don't want to host your homepage, so if GitHub Pages is why you used GitHub, they are not a replacement.

https://docs.codeberg.org/codeberg-pages/

Ever heard of IBM QRadar SIEM?

No problems with that in good old Europe.

I landed 259 PRs -- 497 commits, 40k lines added, 38k lines removed

I wonder how much of these 40k lines added/38k lines removed were just replacing the complete code of a previous PR created by Claude Code.

I'm happy that it's working for them (whatever that means), but shouldn't we see an exponential improvement in Claude Code in this case?

View the full thread without Twitter/X account: https://xcancel.com/bcherny/status/2004897269674639461

https://hachyderm.io/@joschi/115378071393408064 https://bsky.app/profile/joschi.xyz/post/3m3a76o6nkc2c

One thing that Liquibase does better than Flyway is supporting multiple different database systems with the same migrations by abstracting the changes instead of relying on raw SQL statements such as Flyway.

Liquibase and Flyway are the only major frameworks on the JVM which could be embedded into a JVM application to get rid of a sidecar or a startup process which has to run before the actual application could start.

I'm pretty sure they mean https://atlasgo.io/ and not https://atlas.apache.org/.

It takes some thinking, but you can just use rsync to build your own version of Dropbox.

Dash0 currently doesn't offer an own agent or a distribution of OpenTelemetry Collector.

You can use anything which is sending OTLP.

If your applications have been instrumented accordingly, you don't necessarily need a separate agent but can let the OpenTelemetry SDK send directly to Dash0.

Dash0 offers a Kubernetes operator for getting your data in without much effort: https://github.com/dash0hq/dash0-operator

Disclaimer: I am working at Dash0.

Not sure if people are still using Kafka UI. It's essentially unmaintained for a while now.

While the release notes of Kafka UI 0.7.2 [1] only mention the security fixes, it contains 1 year (!) worth of changes [2].

The designated successor is Kafbat UI [3,4], developed by the same development team which previously worked on Kafka UI.

Kafbat UI 1.0.0 [5] already contains a fix for CVE-2023-52251 [6].

[1] https://github.com/provectus/kafka-ui/releases/tag/v0.7.2

[2] https://github.com/provectus/kafka-ui/compare/v0.7.1...v0.7....

[3] https://github.com/kafbat/kafka-ui

[4] https://github.com/kafbat/kafka-ui/discussions/23

[5] https://github.com/kafbat/kafka-ui/releases/tag/v1.0.0

[6] https://nvd.nist.gov/vuln/detail/CVE-2023-52251

The author forgot JBang (Java, Groovy, Kotlin).

https://www.jbang.dev/

See also https://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres... and https://news.ycombinator.com/from?site=dkriesel.com

If you're not using any of the AWS services, that might be true but then you're also leaving a lot of potential on the table.

If you're "cloud-agnostic" and could migrate away from AWS in the blink of an eye then you're paying for an overpriced VM offering and should probably migrate to a cheaper hosting provider immediately.

- GitHub/GitLab/Gitea issues and projects

- YouTrack: https://www.jetbrains.com/youtrack/

FWIW, Graylog is not SaaS but can/should/must be installed on-premise: https://www.graylog.org/

We then stopped instrumenting for other reasons.

Any reasons you want or are allowed to share?

The goal is to keep it simple and not support everything and the kitchen sink (like Spring Boot and the Spring ecosystem in general does).

I totally agree but Jersey 2.x and Dropwizard still support Java 7, so the examples should also work with Java 7.

As Men in Black 3 wasn't that great and Star Wars: Episode 3 also had its lengths (don't get me started about Lethal Weapon 3!), we tried to avoid that. Let's see how Ghostbusters 3 will work out and maybe (but just maybe) we'll think about releasing Graylog3. ;-)

We don't want to use ES too much as Graylog should still work when ES has some problems. It's currently the default output but that may change in the future for special use cases.

That being said, we're aware that many people don't like the dependency on MongoDB and we'll work on that.

Please let us know how it worked out! ;-)

Oh, we got both kinds. We got country and western. ;-)

Seriously, the Docker image and the VM images are there to help people getting started and to quickly try out Graylog. We also offer regular OS packages in DEB and RPM formats (supporting Debian 7, Ubuntu 12.04 and 14.04, and CentOS 6) and a quick setup application (for a simple demo setup of Graylog and its dependencies). So choose your poison and be happy!

We've tested the Docker image on Mac OS X with boot2docker but of course there are always things that can go wrong.

It would be awesome if you could help us improve the Docker image by creating an issue at https://github.com/Graylog2/graylog2-images/issues with the error messages you've encountered when starting the container.