There are a lot of places where channels look like the correct primitive but may actually be overkill. One of my favorite examples is collecting results from a group of goroutines. If you know the number of results up front, you can just define a slice and give each thread an index of the slice to write to (and a waitgroup of course). No channels, no mutexes, and completely thread safe.
Channels are honestly one of the most over-used things in Go. I've been writing Go professionally since 2015 and I honestly rarely use them. Programmers new to Go love to shovel them in everywhere because "why use Go if you're NOT going to use channels?" and I have to say sorry, no - write it serially, then determine if it breaches your SLOs, THEN determine if concurrency fixes it.
I've worked with a lot of "smart" engineers over my career with whom autoscaling is a completely foreign concept, or a half-baked concept at best. My favorite is devs pushing to migrate to k8s because it "scales" and won't hear a single thing otherwise.
Americans would rather die than give up their air conditioned bubbles on wheels. I've wondered why someone hasn't tried manufacturing an enclosed go kart with AC and enough trunk space for a few groceries.
I was recently looking for a new running watch but couldn't for the life of me figure out what Garmin's higher end watches do to justify being over $1000. Like, ok, better battery life... but besides that?
I feel like this isn't a thing when it comes to applications. All the decisions you'd make to allow an app to scale sideways are just, like, good design decisions? Even if you never went 1->2 instances. Otherwise every app would just be PostgREST on top of a beefy VM.
Major version upgrades, HA, multi-master, sharding and georeplication are all stories that are not as out-of-the box simple as they should be at this point, IMHO. Then you layer on all the ways devs tend to abuse postgres (stored procedures, pubsub systems, re-indexing hot tables, etc) that will need hours and hours of debate + meetings + committees + design reviews + more meetings to settle. When all along the team probably could have just written the data to something like Firestore and been, like, totally fine?
I've pushed teams to choose Spanner over using Postgres (when already in the GCP ecosystem). It's not really more expensive when you sit down and do the math, you save untold hours of maintenance over the lifespan of the app, and it actually scales without fuss.
I feel like I'm the only person on HN that doesn't have any major (or cliche) problems with GCP, even after using it for a decade at this point. Like it's not perfect and I've hit weird roadblocks along the way but I've dabbled AWS and I currently use Azure at work and those are hilariously bad in their own ways, people just seem to kind of be used to it?
The problem is, when the context window grows, Claude tends to forget these kinds of rules. It will then do whatever it wants. I had to outright ban comments in the global claude.md, the local claude.md AND write a hook to catch any that still slipped through.
I have been a full-time go developer since 2015 and I have quite literally never written a line of generic go code. I can't even recall seeing any written at any {job} since they've been introduced...
I've blown away by flash 3.6's speed while Opus chugs along for _hours_ on similar tasks. I've gotten into a opus designed -> gemini implemented -> opus reviewed dev cycle recently.
> For a major blockbuster, tax incentives equate to tens of millions of dollars, freeing up money for name-brand actors, elaborate set pieces, and unremarkable CGI effects.
SF is such a weird vibe in general. I've watched a lot of founders/tech bros go to burning man for the first time, completely miss the point of it but adopt an air of superiority for attending. I watched a founder weave in his experience on peyote into a company all hands. They also, for reasons I simply cannot fathom, go out and buy a green Range Rover. And as someone who's been in the ENM space for a long time, SF is the LAST city I'd want to experience it in...
I have no skin in this game and this comment will be gray in a few minutes BUT a friendly reminder that these types of threads are astroturfed heavily by competitor labs and any info should be taken with a massive grain of salt.
If the damage was large, it would be hard to cover up. And if it was very large the US would seek to minimize it. “A few people killed” might be interpreted as “probably a ton of people killed” by the enemy and they keep doing it. Zero information means you can’t argue the case one way or the other, and in those cases the project gets scrapped.
One of the most interest facts about this disaster is that if the submarine was standing on its tail straight up, its nose would be sticking 150ft OUT of the water it sunk in.