Recent searches
Search options
#go
ACCU 2025 SESSION ANNOUNCEMENT: An Introduction To Go by Dom Davis
https://accuconference.org/2025/session/an-introduction-to-go
Register now at https://accuconference.org/booking/
How many problems or improvements can you spot in this real-world #Go code example?
Hint: It works as intended, so it's not bugs, per se, I'm looking for.
I’m a wordy bastard. I really struggle with 500 characters. I’d struggle with 500 words sometimes. It's been hard to find a flow here (despite Mona's fantastic thread generator.)
I’m creating a #blog to house longer writings and share thoughts here without requiring anyone to visit platforms so many gathered here to avoid.
I'm using #Hugo instead of my usual #WordPress and dipping my toes into #Go and #TailwindCSS. I've only created the local structures, but so far, I dig it! It's #FOSS too!
I'm really surprised that log/syslog, the official go library implementing syslog, is:
Using the old RFC 3164 instead of the newer RFC 5424. I understand the need to support legacy stuff, but having a recent language support legacy as only option is surprising.
Not even fully compliant with RFC 3164, as stated by this issue. This sucks because stuff like @grafana Alloy isn't parsing it.
When I first learned #GoLang #Go I remember not being happy about the lack of exceptions and always checking the error returns. I never got over it. I’m not a Go user and don’t really know it currently. But now I am a #RustLang #Rust user and learner. Rust works in a very similar way. Yes, I was skeptical at first (and said so here) but now I’m okay with it. Options and Results make sense.
Maybe I just didn’t give Go a fair shake?
> Modern languages are not using the zero-character to terminate strings, but C does it a lot.
This is NOT true. Why is everybody confusing C (the language) with the C Standard Library? The C language doesn't know anything about terminating strings with a zero character (0x00) byte. What you referring to is the C Standard Library, not C the language.
Share of programming languages used by #GTK3 / #GTK4 applications (2025-03-16):
28% #Python
21% #Vala
20% #Rust
17% #C
06% #C++ #Cplusplus
06% #gjs #Javascript
04% Other: #Csharp #Go #Lua #Haskell #Swift #Typescript #Crystal #Swift #D #Perl
63% use GTK4 (90% of them use #libadwaita), while still 37% use GTK3
Method: Source [1] lists 543 awesome #gtk (3/4) #opensource applications and their #programminglanguage
[1] https://github.com/valpackett/awesome-gtk
"There are so many shapes deriving from the basic comb shape that covering it fully is beyond the scope of a proverbs book."
-Power, "Essential Go Proverbs", which is over 500 pages long
I found myself agreeing with everything in this post from Steve:
https://steveklabnik.com/writing/choosing-languages/
I don't think that the brigade of "Rewrite it in Rust" people is nearly as common or big as all too often claimed, but for if you ever appreciated what either Steve or I ever had to say, and have an impulse to brigade a project on GutHub or social media (even accidentally! If you arrive early you might not realize 2000 people are coming right after you), please don't. It's pointless. It's draining. It can be abusive. And it's counter productive.
»TypeScript zehnmal schneller – Microsofts Pläne für die Programmiersprache:
Microsoft hat die ersten Schritte unternommen, um TypeScript durch eine native Compiler-Implementierung in Go stark zu beschleunigen.«
Da bin ich mal gespannt, ob nun @TypeScript von Microsoft das Frontend WebDev nun auch wirklich effizienter macht ;)
Kudos to the #TypeScript team for doing the port to a native language! Truly amazing! 
https://devblogs.microsoft.com/typescript/typescript-native-port/
Altogether, their choice of using #Go makes perfect sense!
However, there are always trade-offs. One of the biggest trade-offs, IMHO, is:
Not being able to use a _common representation of the AST_ in all language tools - this is an explicit goal for the team behind void(0):
Parse once, use anywhere!
1/2
When you start a new project, the language choice is crucial since it involves many critical aspects. Here is why Microsoft used Go to implement the new Typescript compiler: https://github.com/microsoft/typescript-go/discussions/411
That's a great explanation, why #Microsoft #TypeScript is going to use #Go, and not #Rust, for porting:
* w/ garbage collection
* w/o borrow checker
* w/ cyclic dependencies
* w/ inline memory objects
* w/ shared memory concurrency
In short, their code base is so convoluted that it's easier to port it's flaws to another C-like language than actually fixing the issues.
I think it’s fun to see all the support and rant reactions about Microsoft rewriting #TypeScript tooling in #Go instead of C# or Rust.
Notice that I said "fun", not "interesting". It’s fun because this is just the latest version of "vim vs. emacs" or "tabs vs. spaces". Everyone has opinions, everyone has their favorite programming language, but at the end of the day, 0% (or a very close number) of the people ranting about it are actually working on the project. It’s always easy to criticize someone else’s work when you have nothing at stake.
Do I know any Python uv users who are also Go developers? 
We want to expand Syft's catalogers to understand uv lock files.
Looking for brave new contributors!
https://github.com/anchore/syft/issues/3268
#python #go #opensource #sbom
https://github.com/anchore/syft/issues/3268
I'm on Fallthrough: An Exploration of APIs, Versioning, & HTTP
Announcing my appearance as a guest on Fallthrough, talking about APIs, versioning, documentation, and more.https://fed.brid.gy/r/https://www.jvt.me/posts/2025/03/10/fallthrough-api-exploration/
Looking for other names for the Go Configuration Management system. GCM is nice and short but it's also Galois/Counter Mode (GCM), a mode of operation for symmetric-key cryptographic block ciphers, and I don't want to squat on a name.
So, anyone have any ideas for alternate names for a Go configuration management tool set? Willing to get wild here. 
Rust Alternatives — https://blog.fox21.at/2025/03/09/rust-alternatives.html
This is a follow-up blog post to this thread: https://mastodon.social/@TheFox21/114081657999520621
Thanks for the input.
