Giuseppe Maxia

The end of dbdeployer #mysql datacharmer.github.io/end-of-dbdeplo…

The future of MySQL needs an open conversation. Governance, transparency, and a real community voice, are not optional for an ecosystem like MySQL—they are essential to its future. If you care about where MySQL goes next, read and sign the open letter: bit.ly/4kJGxBJ

An Open Letter to Oracle: Let’s Talk About MySQL’s Future ift.tt/zGtlhxX

Go 1.26 is out, and the announcement says: "Over the next few weeks, follow-up blog posts will cover some of the topics in more detail. Check back later." So you can wait a few weeks OR you can read my interactive Go 1.26 tour right away: antonz.org/go-1-26

Rarely in human experience has there been a technology so revolutionary, so important, so essential, so mind-blowingly awesome that its creators have to force it on everyone and beg people not to say anything bad about it. This PhD says: 🤖🫧💥.

This repository has many Go challenges to help you write idiomatic Go. It looks very promising: github.com/MedUnes/go-kata

Go 1.26 received a somewhat under-the-radar language change: recursive type constraints in generics. Previously, type constraints couldn't directly or indirectly refer to type parameters. For example, this interface declaration: type Ordered[T Ordered[T]] interface { Less(T) bool } resulted in a compile error: "invalid recursive type: Ordered refers to itself". With Go 1.26, it compiles just fine. A typical use case is a generic type that supports operations with arguments or results of the same type as itself (like Ordered[T]). We can use such a type as a member in a generic container (like Tree[T Ordered[T]] — see the screenshot). This makes Go's generics a bit more expressive.

There are a lot of major performance improvements in Go 1.26, but my favorite is this — a small but important one: Optimized fmt.Errorf As you know, both errors․New("x") and fmt.Errorf("x") create the same errorString error. So, it's simpler and more consistent to just always use fmt.Errorf. The thing is, fmt.Errorf was 3x slower than errors․New. So, one of the core Go developers got tired of hearing "fmt.Errorf is slow" and improved it. He created a fast path so that the "plain error" code branch doesn't involve all the heavy machinery and just calls errors․New right away (see the screenshot). Now, fmt.Errorf("x") is just one allocation (like errors․New) and is only 20% slower (25ns vs 21ns). Very nice!

Go 1.26 is coming soon, and the official release notes are pretty dry. So I prepared an interactive version with lots of examples. Read on and see! antonz.org/go-1-26

Paying $3 for a Dollar: The Rational Irrationality of Venture Capital docs.google.com/document/d/1S7…

Another thing that enrages me about public music-players is that they are RELYING on others not doing the same. If everyone played music aloud, it wouldn’t be enjoyable for anyone. These people aren’t merely rejecting codes of civility, they are actively *exploiting* them.

It would be crazy if I advocated new Go features like this: > If you still don't use the "synctest" package, all your systems will eventually succumb to concurrency bugs. or > If you don't use iterators, you have absolutely nothing interesting to build. The job of an advocate is to spark interest, not to reproach people or instill FOMO. And yet that's exactly what AI advocates do. What a weird way to advocate.

AI advocates seem to be the only kind of technology advocates who feel this imminent urge to constantly criticize developers for not being excited enough about their tech. This whole "devote your life to AI right now, or you'll be out of a job soon" narrative is false. You don't have to be a world-class algorithm expert to write good software. You don't have to be a Linux expert to use containers. And you don't have to spend all your time now trying to become an expert in chasing ever-changing AI tech. As the industry adopts AI practices, you'll naturally absorb just the right amount of them. You are going to be fine.

A generics-first HTTP client wrapper for Go. It keeps req's power and escape hatches, while making the 90% use case feel effortless #golang github.com/goforj/httpx

Editing a file without an editor johndcook.com/blog/2024/08/1…

Make sure vim terminate itself after 300 seconds. truly evil 😈 ``` alias vim='timeout 300 vim' ``` The timeout command is a simple way to let a command run for a given amount of time. cyberciti.biz/faq/linux-run-…

If you look closely, the AI hype makes no sense

Once upon a time in a village, a man appeared and announced to the villagers that he would buy monkeys for $10 each. The villagers, seeing that there were many monkeys around, went out to the forest and started catching them. The man bought thousands at $10 and as supply started to diminish, the villagers stopped their effort. He further announced that he would now buy at $20. This renewed the efforts of the villagers and they started catching monkeys again. Soon the supply diminished even further and people started going back to their farms. The offer increased to $25 each and the supply of monkeys became so little that it was an effort to even see a monkey, let alone catch one. The man now announced that he would buy monkeys at $50! However, since he had to go to the city on some business, his assistant would now buy on his behalf. In the absence of the man, the assistant told the villagers, “Look at all these monkeys in the big cage that the man has collected. I will sell them to you at $35 and when the man returns from the city, you can sell them to him for $50 each." The villagers rounded up with all their savings and bought all the monkeys. They never saw the man nor his assistant, only monkeys everywhere. Now you have a better understanding of how the cryptocurrency market works.

Gist of Go: Concurrency is out! Learn Go concurrency from the ground up with 50 auto-tested exercises and tons of interactive examples. It's a full course + book in one. antonz.org/go-concurrency

A Go-based command-line tool that transforms your codebase into a single, navigable Markdown document. #golang github.com/tesserato/Code…

Tech companies are pouring money into AI, and they’re not making it back. Matteo Wong and Charlie Warzel on how everything could come crashing down: theatln.tc/kbwowLdd