cli VS go

I am a self-employed furniture maker. I'm that guy who somewhat infamously no longer builds software[0]. About a year ago I moved my operations from a makerspace to my own shop. That's come with its ups and downs.

On the one hand, I know which idiot last used a tool: me.

On the other, I would no longer see other humans besides my wife most weeks. To keep sane I also work one day a week at a bike shop fixing bikes. It's something I'd done on a volunteer basis many years back.

The unexpected nice thing about this is that it gives me projects that are an hour or two in size in addition to the many-week sized projects that I do as part of my business. It's sort of like getting to fix a small bug in the midst of adding a big feature; it lets me pop out of the big project for a bit and see something else through from start to finish and see some tangible progress before diving back into a long-running project that moves forward in fits and starts.

Beyond getting to tackle some bite-sized projects, I'd say the thing that sustains me is getting to work with clients. It's tons of fun when people come to me with a vision that we can iterate on and bring into reality. And then the flip side is also rewarding: getting to scratch an itch and turn a design I've been turning over in my mind into reality.

https://github.com/docker/cli/issues/267#issuecomment-695149...

Furniture making

On the topic of alternatives I use https://fishshell.com/ and have the Docker Completions installed.

More cases like this (but don't seem to have a consensus): https://github.com/docker/cli/issues/2686

anything happening with this that anyone is aware of: https://github.com/docker/cli/issues/2802

I found a few different issues in docker tracker about this issue, but the only one which seems to be merged is this one which has docker ignore any options which start with x- but that doesn't seem to help here as the local log driver then just complains about:

The service in the error is about docker swarm (that you didn't mention). It seems like you have an issue similar to this one: https://github.com/docker/cli/issues/2875

Docker itself is open-source, and has slowly been broken down into modular components that are themselves open-source. For example, most of what "run this Docker container" does has been extracted out into containerd, which is Apache licensed and used by lots of things. The Docker CE engine is now based on Moby, also Apache license, and the docker command line tool is also Apache licensed. I expect these tools to continue to be community-maintained (though maybe without the Docker name) due to their immense popularity even Docker Inc folds.

Docker has a bunch of components, including the CLI, a runtime etc. They're pretty much all definitely open source, e.g.: https://github.com/docker/cli

A Discussion about including this package in Go as encoding/json/v2 has been started on the Go Github project on 2023-10-05. Please provide your feedback there.

I like the Principles section. Very measured and practical approach to releasing new stdlib packages. https://go.dev/blog/randv2#principles

The end of the post they mention that an encoding/json/v2 package is in the works: https://github.com/golang/go/discussions/63397

There used to be the GO FIPS branch :

https://github.com/golang/go/tree/dev.boringcrypto/misc/bori...

But it looks dead.

And it looks like https://github.com/golang-fips/go as well.

I'm not sure what exactly you mean by acknowledgement, but here are some counterexamples:

- A proposal for sum types by a Go team member: https://github.com/golang/go/issues/57644

- The community proposal with some comments from the Go team: https://github.com/golang/go/issues/19412

Here are some excerpts from the latest Go survey [1]:

- "The top responses in the closed-form were learning how to write Go effectively (15%) and the verbosity of error handling (13%)."

- "The most common response mentioned Go’s type system, and often asked specifically for enums, option types, or sum types in Go."

I think the problem is not the lack of will on the part of the Go team, but rather that these issues are not easy to fix in a way that fits the language and doesn't cause too many issues with backwards compatibility.

[1]: https://go.dev/blog/survey2024-h1-results

Now, I’m not going to use C++ again; I left that chapter years ago, and it’s not going to happen. C++ isn’t memory safe and easy to use and would require extended time for developers to adapt. Rust is the new kid on the block, but I’ve heard mixed opinions about its developer experience, and there aren’t many libraries around it yet. LLRD is too new for my taste, but **Go** caught my attention.

Generative AI development has been democratised, thanks to powerful Machine Learning models (specifically Large Language Models such as Claude, Meta's LLama 2, etc.) being exposed by managed platforms/services as API calls. This frees developers from the infrastructure concerns and lets them focus on the core business problems. This also means that developers are free to use the programming language best suited for their solution. Python has typically been the go-to language when it comes to AI/ML solutions, but there is more flexibility in this area. In this post you will see how to leverage the Go programming language to use Vector Databases and techniques such as Retrieval Augmented Generation (RAG) with langchaingo. If you are a Go developer who wants to how to build learn generative AI applications, you are in the right place!

net/http: add methods and path variables to ServeMux patterns Discussion about ServeMux enhancements

Make sure you have Go installed https://go.dev/.