Directory is four syllables. Folder is two. Shorter wins.

And then other businesses that have “too good” numbers buy those failing businesses and let them go bankrupt to use as larger write-offs and get tax rebates.

https://justuse.org/curl/

Opinion: if the method takes a boolean it should be split to two methods. If it takes two bools it’s four methods in a trench-coat.

That’s a good bot!

This looks interesting, but I don’t particularly want another client app for this when we can “just use curl” and have that in files (already very git-friendly)?

This will not help many, but I’ve found a good way that helps me and my team, since we’re all in VSCode most of the time anyway. The extension “REST client” lets us write HTTP calls directly in a file and run them from there, with some basic variables and support for different kinds of authentication scheme and environment variables. It has replaced POSTman and Bruno for us: https://marketplace.visualstudio.com/items?itemName=humao.rest-client

If you’re not already using a vscode based IDE this won’t help you at all, sure. But, if you are - this lets you write up sequences of requests in a (still manual, but quite quick) file to test APIs and play with them. Highly recommended!

please, no more discords!

I think they’re talking about Europa, the water-nymph and consort of Zeus.

I did not know she was that into milk packaging, but that’s cool.

there’s no ‘i’ on that keyboard?

no, we don’t

Looking forward to the performance improvements, to be sure.

Not that much new in the language I’m excited for - the null-conditional assignment seems nice.

Last update they broke dotnet watch test, though. I’ve tested that specifically on this one, but I’m wary of what else will be broken and remain broken for months.

Wouldn’t analog be a lot more precise?

Accurate, though, that’s a different story…

This actually looks kind of awesome.

great post!

What’s a moca?

https://en.m.wikipedia.org/wiki/Moca

Absolutely true, but Graph-QL has never pretended to be REST.

deleted by creator

Valid, but dumb.

good old 418, always appears when you really want a cup of coffee

Why even use HTTP, when you can just send bytes directly over the physical network card, right?

Because standards make it better for everyone. You’ve no idea when, who or in what context the error will happen or be received by.

It takes so little to return ProblemDetails, and improves the experience of devs using your API so much. Just do it. Stop thinking up edge cases and faffing about with excuses. Do it.

Please, please, please, PLEASE return error-codes and problem-details.

Here’s the RFC: https://www.rfc-editor.org/rfc/rfc9457.html