@Xdbuzz_3880@4zRiot @Mimzume Oh, it was all the mods at this point, I think. They also removed the announcement, or anyone mentioning it. Hopefully the @ everyone gave people some notice, even if the actual message was removed
@GithubProjects The vibe coded readme is horrid. I got to section 8 ternary operator. Had they made if statements as expressions, that would have been reasonable. Instead they reused the ? symbol. Zero confidence when their logic is: "C and Java have it." Yeah, that's good to win over Go devs ..
@Hasen_Judi Process & network isolation are good reasons for containers. Languages like Go, the container is often just an executable in a chroot. A much simpler tool could be used for these containers. Still valid Docker use cases: legacy/complex apps, dev tool consistency, & distribution
@slimjimmy@_chenson__@piq9117 I was going to point out those two for sure. That said, if these were bought, back in 2013, there's a good chance, at that point, the documentation wasn't actually good enough. Historical context of *when* is important, as clearly, these were just an example.
@MarioVerbelen@yatish_me I've had good success with mini -monoliths where the problem domain of each is large enough to warrant a split. Most of it could almost certainly be within the same monolith, though. Usually each being in a service layer.
@Yagyagoel@icanvardar Some languages which have come after Go with error values often have some syntactic sugar around this common pattern: https://t.co/vOBy9mJrvT | https://t.co/nDRvRxHjzB | https://t.co/0A2ejjz7pi are a few examples. I've written a lot of Go & don't mind/am used to the verbosity.
@QuantumJos@falco_girgis @JamaicaAndRoma The first one I got definitely couldn't boot audio/data discs. I don't recall ever trying data/data discs. I'm tempted to pull it out to give it a try.