More

mxey · 2025-12-13T06:08:14 1765606094

> For users that require new features or reliable resolution of reported bugs, we recommend using pgx which is under active development.

mxey · 2025-12-12T07:45:38 1765525538

> especially if readers don't read to the bottom.

That note at the bottom was only added after the article was posted.

mxey · 2025-12-11T18:17:19 1765477039

> We’ve discussed doing brownouts where we fail everything for an hour with clear error messages as to what is happening.

That sounds like the best option. People are used to the idea that a service might be down, so if that happens, they’ll look at what the error is.

mxey · 2025-12-11T18:12:25 1765476745

The article has a new note at the bottom:

> In case the sarcasm isn’t clear, it’s better to leave the warts.

phyzome · 2025-12-11T21:36:05 1765488965

Wow, that wasn't there from the start? That explains a lot of the comments here.

mxey · 2025-12-11T17:50:50 1765475450

glibc, which has had ABI compatibility for decades?

jcalvinowens · 2025-12-11T17:52:47 1765475567

There have been plenty of build breaking changes over the past couple decades, generally they happen for very good reasons and only affect niche usecases.

mxey · 2025-12-11T17:56:48 1765475808

So existing binaries will keep working?

jcalvinowens · 2025-12-11T18:08:00 1765476480

Not necessarily if you go back far enough to have nss problems :)

mxey · 2025-12-11T17:47:21 1765475241

Go does deprecate stuff. It just never removes it.

mxey · 2025-12-11T17:47:01 1765475221

> If you develop a useful library and give it away for free then all power to you if you want to rearrange the furniture every 6 months.

That would make it no longer a useful library

mxey · 2025-12-11T17:37:28 1765474648

Actually this is the reason why Win32 is the stable ABI for Linux.

https://blog.hiler.eu/win32-the-only-stable-abi/

jcalvinowens · 2025-12-11T19:37:57 1765481877

While I certainly empathize with the author of that article and respect the work they put into debugging it, this is a better explanation of that whole thing: https://maskray.me/blog/2022-08-21-glibc-and-dt-gnu-hash

mxey · 2025-12-11T17:31:06 1765474266

> Not that it is always trivial to avoid breaking backwards compatibility, but there are so many times that it would be.

In this case it was 2 functions with 1 line of code each. https://github.com/urllib3/urllib3/pull/3732/files

Spivak · 2025-12-11T19:30:46 1765481446

Wow. Why even remove it? It's just the thinnest wrapper around the dict and since the dict is now part of the public API these methods will work forever unmodified.

mxey · 2025-12-11T17:28:09 1765474089

It is wild to realize that this is the same author as https://entropicthoughts.com/you-want-technology-with-warts

baobun · 2025-12-11T20:38:30 1765485510

There is a new last line of TFA:

> In case the sarcasm isn’t clear, it’s better to leave the warts. But it is also worthwhile to recognise that in terms of effectiveness for driving system change, signage and warnings are on the bottom of the tier list. We should not be surprised when they don’t work.

Looking at comments I guess everyone whooshed.