Kind replies

Variable key isn't used?

Yeah not sure where that came from but as you say, you can pin to a tag/commit, and Go's module proxy stops you from having someone re-push the value of a tag, once it's had someone download a dependency.

You also only pin, as there's no way to do a range, so IMO that makes it nicer and more explicit than other languages / toolchains with respect to pinning

Yeah I'm very much looking forward to // tool landing as that'll push more folks to using a tools.go style approach.

I'm seeing some folks who'll use a tools.go in a separate Go module so then it doesn't impact the top-level dependency tree, on top of Go' s inbuilt module graph pruning

Also as much as I recommend tools.go, there's still some things it can be awkward with ie golangci-lint tracked as a source dependency can lead to issues (dependency version clashes, Go version incompatibility), as well as it not being the recommended use case

Thanks! This looks like it was via my release announcement to reddit

I don't know, I've never had one either but there's certainly some level of hype that makes me curious!

I'd selfishly like to think there's room for both!

Yup! I wrote about this in a bit more detail a few months back

Hand writing the spec, then validating (ie via http://gitlab.com/jamietanna/httptest-openapi) is a valid option - keeps it in sync very well from quite a few big Go apps I know using it

Or you could wrap your implementation in https://github.com/oapi-codegen/oapi-codegen/ from a hand rolled spec - we support net/http - and that then starts towards the process of being closer to the spec

Either way, you still need to validate the spec and implementation are in sync, and IMO, hand-writing the spec is the only "right" solution that makes sure you're intentionally making changes to the API, whereas generating spec from code could lead to just documenting what's in place and ie accidental breaking changes being missed

No, because I have an alias gcob that is much further engrained 🤓

Thank you 💜 anything you feel would be useful to add on top of what's in there?

I used to do this - especially with t-shirts at stake - but since last year I'm not as bothered 🤷🏽‍♂️

Now I try and raise PRs when I can, otherwise I'll forget about them 🙃

Would love to hear about this 💜 as someone who does something somewhat similar, somewhat passively (publicly sharing my salary history), I can attest to how important it is to chat about it with your friends and colleagues and work to get better 🙌🏽

They can be useful, but at least my OSS doesn't need them much. I've got some work bits that do have Musts for convenience either in func main or as you say, in tests

I'd say that adding a separate /x/ or /exp/ package can also be a good way of testing out new things - very clearly a separate "experimental" thing, which can be tested independently

Using a fork of the module is also a good suggestion and a way to make sure it's not even in the main repo, but gives you mostly the same codebase to be able to test things

Oh no, feel better 🤗😷

Thanks! Wondering if it'll get more traction on Hacker News or whether it's maybe a bit wordy 😝

Et voila

Aaron Parecki wrote Meetable - more info - which isn't quite a replacement for the platform and it's social aspects, but is used in a few places including https://events.indieweb.org

go-semantic-release has this same default but thankfully it's straightforward to set it so you can use 0.x releases.

Making it the default is IMO a very bad decision, as it teaches people that they should go to 1.x far too early.

My grumbling will result in a blog post sooner than later 👀

Was the unfinished sentence intended?

Plain OS rather than a container, ie a distroless wrapper for a given DB?

Oh amazing thank you! That's exactly what I was looking for, and has given me many more things to add to mine, thank you 🤓

As was mentioned, Tidelift is generally pitched at bigger orgs, so I'd recommend reaching out to see if it's worthwhile.

(I'm a Tidelift maintainer)

There's also things like https://stackaid.us or https://thanks.dev that may be easier to onboard to

As co-maintainer of oapi-codegen, I have to disagree that the Go community doesn't do OpenAPI 😂

For a point of reference, I post my salary history publicly https://www.jvt.me/salary/

In terms of this and the first episode? As Jesus mentions on the episode, they're some interesting things, but none that'll generally change the way you write Go, but can be fun trivia points or interesting to know

We've had an Oxo Easy-Clean Compost Bin for years - after my parents have had one for years and rate it - and it's pretty good. A good size, dishwasher safe, fits a fair bit. Would recommend!

Is this a public repo of things to know and remember? 👀

Ahh huge congrats!! I'd meant to wish you happy wedding day, but obviously missed it. Hope you had a lovely time 🥰

Surely we still know someone there to do it? 👀

Glad to hear, hope it's of use. We're looking at packaging some of it up so teams can be writing tests for regexes in their own repos, without needing to set up the whole framework themselves 🤞🏽

Oh no that's a typo! Will fix that now

Awesome! I've already used it to refactor some gnarly regexes with safety, so it's already been a worthwhile investment 😁

Does for me on Firefox Nightly (Android)

I remember hearing about that proposal and that it sounded tough to do - sorry you're having to deal with it 😅

https://github.com/mholt/archiver came to mind, but looks like it doesn't support the encryption side of things. Can you use one of the options from the proposal's thread?

It is in fact where this reply is coming to you from! Aka www.jvt.me

This may be of interest to you, @simon 👀

Have an amazing time!

Kris Brandow?

Also seems to be significant downtime at DuckDuckGo too 🤔

Yup, having to !g everything 😥

There are a number in the #IndieWeb community, generally under https://indieweb.org/Microsub#Clients - and in fact what pointed me to your post to reply to, all via Micropub and Webmentions 😁

Can't celebrate big willies now cause of woke 😔

Would it be possible to increase the contrast on those code snippets? 👀

Nice, I do that for my GitHub/GitLab README ie https://gitlab.com/jamietanna/jamietanna/ and keep my /now page hand maintained!

Thanks very much!

Yup, especially as a maintainer, just in the last few days posted https://www.jvt.me/posts/2024/05/09/oapi-codegen-sustainable/ for the most active project I maintain, very much in my free time

Great! This will be part of v2.2.0 which aims to be hopefully mid-May but definitely by the end of May - in the meantime, feel free to pin to the commit that fixes it (on our default branch) until the release

Trying to take an existing project and convert it to Gradle? Trying to add things to an existing Gradle project?

Thanks for the report! No need, I've raised https://github.com/deepmap/oapi-codegen/pull/1585 which should fix it!

If you're able to try the branch to confirm it that'd be appreciated (instructions in the README) but no worries if not

Have you added the output-options configuration item for it? (https://github.com/deepmap/oapi-codegen/?tab=readme-ov-file#generating-nullable-types)