crusty0gphr
@crusty0gphr.bsky.social
🥲 ▮▮▮▮▮▮▯▯▯ 🫠 | Go🪐 | Beer-Driven-Development 🍺 | Yet Another Golang Developer
It gets better when scales
November 1, 2025 at 5:35 AM
It gets better when scales
Abstraction is a simplified view of an entity , which omits unimportant details. Abstraction is a part of simplification and a key to modularity.
Go generics are debatable. This was an entirely community-requested feature to remove some boilerplate from runtime code.
Go generics are debatable. This was an entirely community-requested feature to remove some boilerplate from runtime code.
October 31, 2025 at 11:22 AM
Abstraction is a simplified view of an entity , which omits unimportant details. Abstraction is a part of simplification and a key to modularity.
Go generics are debatable. This was an entirely community-requested feature to remove some boilerplate from runtime code.
Go generics are debatable. This was an entirely community-requested feature to remove some boilerplate from runtime code.
Go's json package, conceptually, has better design. It is a product of a design choice that values simplicity and high abstraction.
October 31, 2025 at 7:35 AM
Go's json package, conceptually, has better design. It is a product of a design choice that values simplicity and high abstraction.
Rust & Zig (Bun): "We know everything about the data structure. Use that to generate perfect, specialized code possible."
Go: "We have no idea what data structure we'll get at runtime. We must be prepared to handle anything the user throws at us. We'll inspect the structure when we get it."
Go: "We have no idea what data structure we'll get at runtime. We must be prepared to handle anything the user throws at us. We'll inspect the structure when we get it."
October 31, 2025 at 7:35 AM
Rust & Zig (Bun): "We know everything about the data structure. Use that to generate perfect, specialized code possible."
Go: "We have no idea what data structure we'll get at runtime. We must be prepared to handle anything the user throws at us. We'll inspect the structure when we get it."
Go: "We have no idea what data structure we'll get at runtime. We must be prepared to handle anything the user throws at us. We'll inspect the structure when we get it."
Well, there are a fundamental difference in concepts how Zig (Bun), Rust and Go work with json. Go's json package is reflection heavy. It is also bound by the GC.
October 31, 2025 at 7:35 AM
Well, there are a fundamental difference in concepts how Zig (Bun), Rust and Go work with json. Go's json package is reflection heavy. It is also bound by the GC.
This one actually will print "something went wrong".
The difference is how return value is declared and initialized to its zero value on the stack frame. This affects the defer closure.
This is a very dangerous concept. I lost a week of debugging a problem with a similar implementation.
The difference is how return value is declared and initialized to its zero value on the stack frame. This affects the defer closure.
This is a very dangerous concept. I lost a week of debugging a problem with a similar implementation.
July 4, 2025 at 2:36 PM
This one actually will print "something went wrong".
The difference is how return value is declared and initialized to its zero value on the stack frame. This affects the defer closure.
This is a very dangerous concept. I lost a week of debugging a problem with a similar implementation.
The difference is how return value is declared and initialized to its zero value on the stack frame. This affects the defer closure.
This is a very dangerous concept. I lost a week of debugging a problem with a similar implementation.
Your answer is correct btw 🎉
July 4, 2025 at 2:08 PM
Your answer is correct btw 🎉
Good catch, there was a trap 🪤
What about this one? 😈
What about this one? 😈
July 4, 2025 at 2:07 PM
Good catch, there was a trap 🪤
What about this one? 😈
What about this one? 😈
This is a thing I've noticed for myself. If I code the solution myself, I'm more aware of what I'm doing. When I generate tests, I feel disconnected from the project. After generating a few lines of code, bug fixing feels a bit quirky, like I've lost the context of what I'm doing.
June 11, 2025 at 7:41 PM
This is a thing I've noticed for myself. If I code the solution myself, I'm more aware of what I'm doing. When I generate tests, I feel disconnected from the project. After generating a few lines of code, bug fixing feels a bit quirky, like I've lost the context of what I'm doing.