Holy cheese my untyped composite literal proposal from 2015 just got accepted. #golang github.com/golang/go/is...

I recently got back into photography and was also not thrilled about giving Adobe money, but I got the sense online that CO’s library management wasn’t as nice as Lightroom, so I’ve stuck with Lightroom.

This thread definitely makes me interested in giving Capture One a shot.

>benchmark perf improvements
>it's slower

Compiler nerd joy: making some #golang switch statements ~2.5x faster ⚡

go.dev/cl/756340

The SAT had the same cursive paragraph thing too when I took it. I had a similar nervous reaction!

“Type Construction and Cycle Detection” by Mark Freeman — go.dev/blog/type-construction-a...

#golang

Now you’ve learned to stick to HTTP/3 proposals. Those are much simpler than uuid.

I’m glad I’m not the only one that found the idea of not reviewing code unreasonable. Beyond even finding problems or understanding the code, a key component of code review is ensuring that the code base remains maintainable over the long term.

GitHub - u-root/gobusybox: Tools for compiling many Go commands into one binary to save space. Builds are supported for vendor-based Go and module-based Go Tools for compiling many Go commands into one binary to save space. Builds are supported for vendor-based Go and module-based Go - u-root/gobusybox

Oh! If you like bundle, you’ll love github.com/u-root/gobus..., an awesome cursed tool for combining multiple package mains into one binary.

I’m glad you have this follow up so not to anger the h2_bundle fan club.

//go:fix inline and the source-level inliner - The Go Programming Language How Go 1.26's source-level inliner works, and how it can help you with self-service API migrations.

Find out how the source-level inliner in Go 1.26 can help you with API migrations.
go.dev/blog/inliner

“//go:fix inline and the source-level inliner” by Alan Donovan — https://go.dev/blog/inliner

#golang

Additionally, I want to speak directly to Iranian New Yorkers: you are part of the fabric of this city — you are our neighbors, small business owners, students, artists, workers, and community leaders. You will be safe here.

“Allocating on the Stack” by Keith Randall — https://go.dev/blog/allocation-optimizations

#golang

Those were the days. Now I use nvim main.go.

spec: generic methods for Go · Issue #77273 · golang/go Proposal: Generic Methods for Go A change of view. Background For clarity, in the following we use the term concrete method (or just method when the context is clear) to describe a non-interface me...

🚀 "spec: generic methods for Go" has been accepted!

You will soon (1.27?) be able to declare (on concrete types only) methods that introduce type parameters, i.e. type parameters other than the ones (if any) that come from the method's receiver.

github.com/golang/go/is...

#golang

In retrospect x86-64 may be easier just because i386 is so cursed. At least things are simplified a little in the 64-bit world.

Good point! Once @rebane2001.bsky.social adds full i386 support, it should be possible to run Chromium in Linux in CSS. Then there would be no need to do anything natively.

My phone is now hot but the best part is I’m not sure if that is from the CPU emulator or from GitHub trying to render the 14k source file when I went to see how this works.

Turn Dependabot Off I recommend turning Dependabot off and replacing it with a pair of scheduled GitHub Actions, one running govulncheck, and the other running CI against the latest version of your dependencies.

Dependabot security alerts have terrible signal-to-noise ratio, especially for Go vulns. That hurts security!

Just turn it off and set up a pair of scheduled GitHub Actions, one running govulncheck and the other running CI with the latest version of your deps.

Less work, less risk, better results!

“Using go fix to modernize Go code” by Alan Donovan — https://go.dev/blog/gofix

#golang

Go 1.26 interactive tour New with expressions, type-safe error checking, and faster everything.

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

Some pretty awesome improvements in 1.26 for compiling/testing typescript-go.

With a clean build/test cache, running the full test suite used to take 3m45s, but now takes just 2m10s.

“Go 1.26 is released” by Carlos Amedee, on behalf of the Go team — https://go.dev/blog/go1.26

#golang

🍵

Bah, my joke has a typo anyway 🙃

I’ll be honest, I’m a little disappointed that “ahead-of-time gc” isn’t a garbage corrector that collects objects before they are ever allocated.

$ jj describe -m "Hello, world!"

I have catch-all email on my domain and got one to epstein@. Yikes

ICE out of my compiler