Go

Stop Writing JavaScript for Your Go Backend. Try This Instead.

The mental whiplash of switching between Go and JavaScript is killing full-stack productivity. But a new approach using shadcn’s data-slot pattern is bringing JSX-like component authoring directly to Go. By moving styling logic to compile time, gsxui bypasses Go’s limitations and offers a viable, JavaScript-free alternative for server-driven UIs.

Stop Using LLMs to Write Code. Start Using Them to Ship It.

A developer remade Battle City (NES, 1985) in Go and made it browser-playable via WASM β€” but the real story isn’t the game. It’s how they used an LLM not to write the core logic, but to solve the deployment last mile. The hardest part of software isn’t writing code. It’s shipping it. LLMs might be best at eliminating the friction that kills projects before they cross the finish line.

Every SSH Session Can Now Be Recorded Without You Ever Knowing

SSH-cast is a pair of Go binaries that records SSH sessions entirely from the local machine β€” no server-side component, no consent mechanism, no notification. For sysadmins, it’s an elegant audit solution. For everyone else, it means every SSH session you’ve ever had could have been silently captured without your knowledge. The tool exposes a structural flaw: when surveillance happens entirely on the observer’s side, the observed loses all agency.

The PHP Server That Outperforms Nginx by 10x (And Why It’s a Nightmare for Node.js)

A new open-source PHP server bypasses the Nginx+PHP-FPM bottleneck, delivering 10x the concurrent requests. This isn’t just an upgradeβ€”it’s a direct challenge to Node.js and Go, proving you can scale existing PHP codebases without rewriting them. The architecture is simple: a long-lived event loop instead of process-spawning.

Stop Writing Boilerplate. Go Needs a Rails Moment.

Go developers love simplicity, but building web apps often means drowning in boilerplate. Andurel v1.0.0 brings the ‘omakase’ philosophy of Ruby on Rails to Go, offering an opinionated, magic-filled framework. The real question isn’t about technical performance, but whether Go’s minimalist community is ready to trade control for developer experience.

You’re Wrong About Time in Go β€” And Your Code Is Probably Broken

Go’s time handling is far from trivial. A pop quiz reveals that even senior developers get the simplest questions wrong, because time in Go is a high-level abstraction with edge cases around zero values, time zones, and monotonic clocks. The moment you treat time as a primitive, you invite silent bugs into your code.

You Run `go get` Every Day. North Korea Is Counting On It.

North Korean hackers are compromising Go and PHP packages through the PolinRider campaign β€” not through sophisticated exploits, but by exploiting a simple gap: Go and Packagist don’t require multi-factor authentication for publishers. While NPM and PyPI adapted after years of attacks, these registries chose convenience over security, outsourcing risk to every developer who runs `go get` or `composer install`.

Profiling Isn’t About Finding Slow Code. It’s About the Hidden Dialogue with Go’s Runtime.

Profiling in Go isn’t about finding slow functionsβ€”it’s about understanding the hidden dialogue between your code and the runtime. GC pauses, scheduler contention, and memory allocation often cause more slowdown than any algorithm. This article shows how to stop debugging blind and start treating the runtime as a co-author of your performance.