I benchmarked identical Go and Rust servers under heavy load: - 15,000 concurrent users - 15 minutes sustained load - Real Hetzner K3s cluster (not localhost) - Separate nodes for apps, monitoring, and load testing - k6 for load generation, Prometheus + Grafana for metrics Both servers do the same thing: 100 iterations of SHA256 hashing, return JSON. Go: standard library only Rust: Hyper + Tokio + sha2 I tracked p50, p90, p95, p99 latencies in real-time. The results were not what I expected.

Code is on GitHub if you want to run it yourself: https://github.com/huseyinbabal/benchmarks/tree/main/rust-se... Curious what you all think.

I built a terminal UI for AWS and shared it 3 days ago. It reached ~1.4k GitHub stars in two days.

Using the same architecture and UX approach, I built a GCP version and shared it as well. That one got ~4 stars in two days.

I’m curious how people here interpret this difference. Is it about console UX, user demographics, tooling culture, or something else?

AWS: https://github.com/huseyinbabal/taws GCP: https://github.com/huseyinbabal/tgcp

What is the error? We can continue on github, I can do my best

I didn’t take code or reverse-engineer anything from that Reddit project, and I wasn’t aware of it when I started.

I’ve been a long-term k9s user, and the motivation was simply: “I wish I had something like k9s, but for AWS.” That’s a common and reasonable source of inspiration.

A terminal UI for AWS is a broad, well-explored idea. Similar concepts don’t imply copied code. In this case, even the UIs are clearly different—the interaction model and layout are not the same.

The implementation, architecture, and UX decisions are my own, and the full commit history is public for anyone who wants to review how it evolved.

If there’s a specific piece of code you believe was copied, I’m happy to look at it. Otherwise, it’s worth checking what someone actually built before making accusations based on surface-level assumptions.

Will be available soon ;) https://github.com/huseyinbabal/taws/issues/18

There was a resource handling problem, but it is fixed in 1.0.1 that you can try

I also care security part, but this is just beginning :) New features will be added iteratively based on community requests, and it seems there are plenty of good requirements in HN thread, thanks

I'm excited to announce the launch of Rapidapp, a new SaaS platform for managing PostgreSQL databases in the cloud. The main motivation is here to provide the simplest way to spin up a PostgreSQL database with powerful integration. Rapidapp allows you to create and use PostgreSQL database in less than 1 second. We also offer various integration like Spring Autoconfiguration, Terraform provider etc.. We're currently in early access and would love your feedback. You can sign up for life-time free plan which is limited to 1 database / 20 MB data.

In this article, I explain the basic concepts about Java Thread Synchronization and show real life examples to explain how deadlock occurs