CodexiLab @codexilab

PostgreSQL 19 is getting graph queries. With SQL/PGQ, you can query relationships directly in SQL: → social networks → recommendations → fraud detection → dependency graphs Postgres is not just a relational database anymore. It’s becoming the database for everything. x.com/alxshp/status/…

alex shapalov @alxshp

4 weeks ago

PostgreSQL 19 is bigger than JSON Coming improvements: → SQL/PGQ graph queries → GROUP BY ALL → REPACK CONCURRENTLY → parallel autovacuum → logical replication without restart → sequence replication → better EXPLAIN ANALYZE IO → pg_stat_lock / pg_stat_recovery → online

10 22 166 102K 78

I stopped paying for several apps after discovering these. They're free. Open source. Privacy-friendly. And in some cases, they're actually BETTER than the paid alternatives. Here are 5 FOSS apps worth installing in 2026 🧵

Form follows the function, but the name is defined by intention.

Go's log/slog package essentially boils down to 5 core types: Value: holds a value like an integer or string ("alice"). Attr: A key-value pair (name=alice). Logger: Takes a string message and optional Attrs, then creates a Record. Record: Represents an event with a timestamp, message, level, and a set of Attrs. Handler: Processes Records, often rendering them to strings and writing to an io.Writer. That's it!

@AdamantxYves Con razón tienes el cerebro quemado. Por cierto, los naz-is también tuvieron negros en sus filas, put'a naz'

Your Golang knowledge, explaining: Goroutines Channels Context cancellation WaitGroups Mutex vs RWMutex Buffered vs unbuffered channels Worker pools Select statements Interfaces Error wrapping Generics net/http internals gRPC in Go sync.Pool io.Reader / io.Writer Goroutine leaks Escape analysis Zero-allocation patterns Race detector Memory profiling with pprof Interview decision: Sorry, we need someone who actually knows when to use a goroutine. Knowing Go features ≠ knowing Go engineering. I’ve seen engineers spin up 100 goroutines for a task that should’ve been a simple for-loop. They knew what a goroutine is. They didn’t know why to spawn one. Understanding fundamentals in Go means asking better questions: --- 1. Do you really need concurrency here? Just because Go makes concurrency easy doesn't mean everything should be parallelized. If your job is CPU-bound — concurrency won’t give you a speedup. If your job is I/O-light — concurrency might hurt performance. Many Go beginners accidentally create spinning goroutine storms for trivial tasks. --- 2. Should this be a goroutine or a worker pool? Goroutines are cheap — not free. Thousands? Fine. Millions? You’ll crash your service. Worker pools add backpressure, limit concurrency, and prevent cascading failures. Correct concurrency is about control, not enthusiasm. --- 3. Is a channel even the right abstraction? Channels are not the default. Sometimes: a simple slice is faster a mutex is simpler a pipeline is unnecessary atomic values give lower overhead Channels introduce synchronization. Synchronization introduces latency. Engineers who love channels often write code that’s “clever” instead of correct. --- 4. How will this context propagate? Most Go outages happen because developers: forget to cancel contexts pass background context everywhere leak goroutines waiting on dead channels ignore deadlines If your system doesn’t handle cancellation properly, you don’t have a Go service — you have a time bomb tbh. --- 5. Have you run the race detector, profiler, and escape analyzer? If you write Go without: go test -race go tool pprof go build -gcflags="-m" …then you're guessing, not engineering. Being able to explain: why a value escapes to the heap why CPU usage spiked why memory is ballooning why goroutines aren’t releasing is what separates a “Go tutorial graduate” from a real Go engineer. --- 6. Does this service need Go? Go shines in: high-throughput APIs distributed systems infrastructure tools networking services event processing real-time pipelines Sometimes Python is better. Sometimes Rust is better. Sometimes PostgreSQL stored procedures outperform your Go service entirely. Knowing Go means knowing when not to use Go. --- The best Go engineers aren’t the ones who know every feature. They're the ones who can explain: why this should NOT be concurrent why this needs a mutex, not a channel why this code must avoid allocations why this API should return errors, not panics why a simple goroutine is not a “system design pattern” Anyone can memorize go routines + channels = concurrency. Not everyone can architect a system that runs clean for months without leaking memory, burning CPU, or failing under load. That’s the difference between Go as a language and Go as an engineering discipline.

Makakmayum @makakmayum_sid

7 months ago

Your system design knowledge, explaining: - gRPC - CDNs - WebSockets - Rate Limiting - API Gateways - Microservices - Redis Caching - Load Balancers - Message Queues - Database Sharding - Consistent Hashing - Eventual Consistency - Distributed Tracing - Horizontal Scaling -

14 155 1K 127K 2K

DTOs in Go and how make it blog.stackademic.com/designing-effe…

PRO TIP: Store rate limits in localStorage instead of your database. Each user tracks their own API calls. Saves memory and eliminates Redis dependency.

|￣￣￣￣￣￣￣￣￣￣￣￣| | You don't need to create | | an interface for every | | single class | |＿＿＿＿＿＿＿＿＿＿＿| \ (•◡•) / \ / --- | |

modern dashboard for managing and monitoring Kubernetes clusters

I realized that peer-to-peer bluetooth file transfers without internet is even cooler. Here's the work in progress. Sending images and audio notes in bitchat. The image reveal animation is an hommage to all millennials surfing the web during the slow internet modem era.

calle @callebtc

10 months ago

hear me out: bitchat file / audio / video transfers between two devices directly via tor, no file storage service in between.

35 24 466 68K 31

@TheGingerBill We all go to hell anyway.

What can be extracted from this is: - Package managers are a terrible idea. - Unless your lang has an excellent stdlib, the package manager doesn't matter much. - Sooner or later you'll need a package manager anyway.

gingerBill @TheGingerBill

10 months ago

I've written up the dialogue from the last TheStandup video I was on with @ThePrimeagen, @teej_dv, and @josevalim. Package Managers are Evil. gingerbill.org/article/2025/0…

5 12 153 73K 38

`odin test` is now fancy!

Kubernetes clusters made easier with a cross-platform open source desktop app

browser-based code editor from VS Code

"OOP is well suited for GUI programming" 🤡 The OOP GUI programming: 👇

Several years ago, I wrote an article on #golang package design and styling which became quite popular. NotebookLM generated a podcast for it and it's ridiculous: - They have nice analogies. - They developed new ideas like keeping types closer help debugging. - They know how Go differs from other languages in package organization.

Official Go blog post: A new experimental Go API for JSON #golang go.dev/blog/jsonv2-exp

Announcing Genkit Go 1.0 ✨ The SDK is now stable and production-ready. This release introduces the genkit init:ai-tools command for seamless integration with AI coding tools, plus built-in support for tool calling, RAG, and more. Read the blog →goo.gle/3Kep4D6

keyboard_arrow_left Previous keyboard_arrow_right Next