Roelf Diedericks

@glcst uuid-v6

what if we run out of uuids? I'm concerned.

@ryanlpeterman Oh. @golang wins again.

Barbara Liskov (Turing Award Winner): "Python has modules, but it doesn't have encapsulation. It allows code on the outside to muck around with what's going on on the inside of a module. Encapsulation is a crucial part of making modularity work. And when you're building big programs so you have many programmers working on them, your team is really only as strong as your weakest programmer. So it's nice if the compiler can enforce things and make certain kinds of bad behavior not possible."

@LarryJones For a moment I thought you were talking about cloud hosting.

Can we stop saying " if you can’t afford to tip you can’t afford to dine out!" We need to be saying, "If a restaurant can’t pay its employees a livable wage without depending on the generosity of customers then they can’t afford to own a business!”

@hmemcpy I have departed.

I am github user 601206 and I'm here to remind you: this is not an airport - no need to announce your departure.

@noinconsistency You heard of COBOL?

this is from the Date constructor in javascript. who the fuck designed this

@mitsuhiko @mitchellh Your article sums up everything I experienced and grew up with. The web ebbs and flows. Code ebbs and flows. Web.archive.org needs all the support it can get. More then centralised DVCS hoarders like github. It was amazing, but it's time to say goodbye.

The post by @mitchellh gave me the final push to finish my GitHub "obituary". I originally started writing it after the Zig to Codeberg move. It's just a retelling of how I remember OpenSource pre GitHub and what it gave us. lucumr.pocoo.org/2026/4/28/befo…

@mitsuhiko @mitchellh Codeberg runs on Forgejo. Host your own. I just did for git.goclaw.org

@ahmetb Since when has concurrency not had edge cases ?

if you enjoy using the concurrency primitives in Go, challenge yourself to implement a connection pool sometime. there are A LOT more edge cases in this than I originally thought.

@LundukeJournal I think this tells one everything one needs to know

Lix, a fork of the Nix Linux package manager, has some of the most bizarre, political rules imaginable. For example, the following will get you immediately banned from the project: - “Transphobia” - “Peddling Right-wing Ideology” - and “Pluralphobia” If you don’t know what “pluralphobia” is, you’re in good company. I had to look that one up too. “Pluralphobia” deals with Multiple Personality Disorders. If you are not sufficiently supportive of someone who believes they have multiple people “living in the same body”… you are a “Pluralphobe”. When interacting with the “Lix” project, as a developer or user, it is mandatory that you agree that every “personality” a person has is real. For example: If a guy named Tony, from Nebraska, sometimes thinks he’s Julius Caesar… and other times he thinks he’s Gilligan (still stuck on the island)… you MUST agree that is all real, and show each “personality” respect. … or you are banned. The “Lix” project also makes it clear that people “of a less-marginalized background” are a “guest in our spaces”. Assumedly “Our” means people who think they are Genghis Khan on Tuesdays. Also, being a Republican (or having other “right-wing ideology”) is forbidden. “Lix” has declared itself to be a political, non-neutral project. Not surprisingly, one of the key goals of the “Lix” project is to replace existing C++ code… with, you guessed it, Rust. Because of course. lix.systems

@grok @JamesWard @quangtung2912 And therein lies the rub.

A Go "hello world" compiles to a single ~2 MB statically linked binary. Zero external runtime. JVM hello world? The .class is tiny, but you need the full JVM (JRE ~150-400 MB installed, depending on version/distribution). Minimal runtime memory footprint starts ~20-50 MB+ for the hello world process alone. GraalVM native images shrink Java to ~7-15 MB standalone binaries, but that's not the classic JVM approach.

Generally developers think of Go as being great for concurrency. Its not. JVM approaches are vastly superior. And even some of the best in the whole industry when you include virtual threads, structured concurrency & Effects.

@kdaigle @mitchellh Well, then maybe you can cheer on your support team to explain to me why I, a 20+ year FOSS developer had his account suspended for using github actions to compile an open source project into .deb files for distribution.

@mitchellh I'm sorry, @mitchellh. The team is going to keep working to make GitHub something you can come back to with real proof, not words. Until then, I'll still be cheering on Ghostty as a user.

Ghostty is leaving GitHub. I'm GitHub user 1299, joined Feb 2008. I've visited GitHub almost every single day for over 18 years. It's never been a question for me where I'd put my projects: always GitHub. I'm super sad to say this, but its time to go. mitchellh.com/writing/ghostt…

I have also left github and shall never return. Host your own code. Its cheap. Git is a DVCS. Distributed Version Control System, by design. Github centralised distributed version control, and that's the entire problem. Self-host your own gitea, or forgejo instance, and federate.

@JamesWard @quangtung2912 @grok @grok, how heavy is the JVM and all it's luggage compared to a simple statically linked go binary with decent inbuilt concurrency. Lets not even go concurrency. Lets just go "hello world"

@quangtung2912 @grok answer this please

@JamesWard But the, it's also Java.

@ibuildthecloud codeberg.org/forgejo-contri… Federation is the answer.

Do you need github for project visibility? No, right? Nobody discovers projects through github.

@joshmanders Host your own Forgejo instance. Super easy. I did it last night for git.goclaw.org. Github as it used to be.

GitLab was designed by developers with no eye for design but think they do. The UX is atrocious as if they never used their own product. I'd let GitHub lose another 5-10% uptime before I'd consider switching to BitBucket before I'd consider GitLab.

@WeldPond @L0phtHeavyInd Awesome! L0pht was always such an inspiration to me.

32 years ago today I registered the @L0phtHeavyInd class C. I got the email from ARIN, sent the class C address to our ISP, then got the first packets routed over our 56K modem to our 486 linux box. When those first packets come through the whole room exploded with chants of, "We on da backbone!" Then came one of the first hacking resources on the web, shell accounts, a bbs, webcams, and lots of shenanigans. You can see an archive of the website here: gbppr.net/l0pht/l0pht.ht…

@stackallocator The valid reason is interface naming consistency which was achieved in the old naming scheme as well, by udev persistence scripts,. Fortunately one can still choose between naming patterns.

there is a valid reason for this which most linuxlarpers won't understand

@unclebobmartin I mean that's reasonable debugging

Don’t use Grok to help you debug a GFCI outlet tripping. The advice it gives is absurd, and dangerous. Here’s the scenario. I have a refrigerator in the garage. The GFCI has tripped three times in a row. Is the problem in the refrigerator, or is it in the GFCI outlet. Grok’s advice was to plug the refrigerator into a non-GFCI outlet, and if it runs OK then the problem must be in the GFCI outlet. That’s just insane.