Ole Bulbuk

@tsenart I think it's more about sec teams now being *forced* to learn and use these tools next to everything they have on their plate already. And even much more that the time to roll out patches is reduced to minutes. This essentially removes any chance to test patches first.

I don’t understand the fear factor here. Is it the case that blue teams trail behind red teams so significantly that they can’t throw the very same models at their code to find and patch these zero days ahead of time?

@goinggodotnet Not in Germany either. 😉

Tell me you're not in the States without telling me you're not in the States

A rare personal note. My dear friend Ivo (the dad) has a rare genetic liver disease (PSC) and has, after concerted persuasion from those of us who love him dearly, finally consented to a public appeal for a living donor. Liver donation is quite miraculous in that one can give half and both halves grow back. Fwiw, none of the AI models yet understand how to cure PSC, though I would bet that the next generation of humans will be more lucky. I've never asked for RTs etc before but I think it would help in this case! Link below.

@duginabox @ibuildthecloud If they are your (de)serializers, you can build a custom way to hand any data to them. 🤷‍♂️

@ibuildthecloud I don't care about "cancel", I want to pass config/options to my custom (de)serializers.

encoding/json/v2 is the first golang SDK API to use functional options. This is the beginning of the end. From here on out, the language sucks. Options should always be a structs and then the functional patterns can be layered on top. Refer to controller-runtime client for a good implementation of this.

@VaughnVernon And what are those better ways? I would love to learn more about it

The approaches to error handling and failure are roughly 99.999% wrong. If not, it's even worse. There are far better ways than those commonly used.

@JasonThorsness I'm finishing a parser combinator library that can report multiple errors. Only parsing (mathematical) expressions isn't finished yet. github.com/flowdev/comb

Anyone have any little-known Go projects I could feature on an article about little-known projects?

@nzachow_ I think it's a good decision. A better one might be something aspect oriented. That could help to centralize errors, logging, metrics, and other technical aspects.

Did you know that Go's 'if err != nil' is a design choice for clarity, not just boilerplate? 💡 It makes error handling explicit and local, preventing hidden exceptions and simplifying code reasoning. What's your opinion on this topic?

@zajacr There are already a lot of testing libraries. And many Gophers are happy with the standard library. I'm not sure the world is waiting for yours. 🤷‍♂️

I'm developing zero dependency testing library. Which one of those are more intuitive for you? A or B? C or D?

@zajacr Clearly B and D. want has to be the edge value. The actual one has to be great or later.

@bernoussama It's good for many in-house projects. But I wouldn't use it for open-source libraries. I don't like to force dependencies that aren't strictly necessary on others. And it's one more thing to keep safe/up to date.

I just discovered a testing package called Testify that simplifies writing assert tests without the boilerplate of the standard testing package. It makes unit tests easier to write and read, imo. What do you think?

@CAFxX I would like to see an example of that, too.

@flowdev_org I am referring to the blind/unwarranted pushback that even most sensible proposals receive nowadays.

I have increasingly the feeling that Go is ossifying a bit too much. Languages that don't evolve in response to legitimate use cases and reasons risk being left behind... and that would be a pity, because many of the fundamental ideas of Go will stay relevant for a while.

@VipinJangi3398 So it becomes easy to understand. 😀 It depends mostly on the context.

How to structure a golang project?

@thehumanmaskot Idiomatic Go code. It often gets the most optimizations from the compiler, too. 😀 Unless you can prove that it's a bottleneck. Then you write efficient Go code. 😁

should you write idiomatic Go or efficient Go code?

@CAFxX Your statement is so abstract. So what exactly are you talking about then?

To preempt the KISS argument: I am not talking about evolutions that would make Go unnecessarily complicated.

@Rajshri0987 Usually web APIs. I'm using GORM only for a desktop APP. ORMs are great for simple cases. But if things get complex, they become a bottleneck, IMHO.

@flowdev_org Ok. What are you building then??

Which ORM do you prefer for development in golang??

@sinore69 I am not a fan of try/catch. It's a lot of extra keywords and behavior for very little or even no gain. I would love to have good aspect support in Go. That could centralize error handling, logging, instrumentation,... Much more orthogonal and bang for the buck.

Go team has officially stopped considering new syntax proposals for error handling if err != nil is here to stay. What’s your take on a try/catch style syntax that doesn't change behavior, just reduces verbosity? #golang #programming

@sinore69 What kind of project interests you? I would start with a rather small project. Things like Kubernetes are really cool, but most people need years of training and experience before they can provide value to such a project.

Hi everyone! 👋 I'm looking to start contributing to open source and would really appreciate any recommendations for Golang repositories. Preferably ones with active maintainers and good documentation. Thanks in advance! 🙏 #golang #opensource #devcommunity

@EngComp269 C++ is great for training your mind because it's so complex. In practice, most professional programmers use simpler languages. Many aren't able to work on a big C++ code base. So, no. You don't need C++ at all to become professional.

@ErelVanono Some good old patterns don't work anymore. That's frustrating. It takes time to learn new ones and understand that you don't really need most of the old ones. Reading good examples like the standard library is a good start.

After a year with Go, I admire its simplicity but often find myself missing the expressiveness of other languages. The trade off feels limiting at times. For those who’ve been here longer: how do you stay expressive in Go without fighting the language?