majewsky
Joined 10 years ago
Joined 10 years ago
Source: https://mstdn.social/@jschauma/117513596272504904 https://mastodon.social/@glyph/117509558825919922
If only we could come up with a way to manage memory automatically. Alas, one can only dream.
???
We do. "Class war" is just the succinct phrasing for "people who earn money through capital returns have vastly different incentives than people who earn money from their labor, and they also have the means to turn those interests into political leverage".
"Emergency" is not the same as "emergency services".
And then upstream adds new fields where the zero value is different from the previous behavior, causing users to silently drift away from the intended behavior. I had this happen to me with a type from std, and had to add a specific test to guard against it with future std upgrades: https://github.com/sapcc/go-bits/pull/309/changes#diff-f5721...
Which a lot of libraries are doing because they wrote an http.Transport{...} literal in an earlier version, and then std added new fields to the type in a way that silently breaks existing users. The zero value should have matched the previous default behavior.
Case in point: https://github.com/prometheus/client_golang/pull/1885/change...
We had the same in our own library, and now have a testcase checking if our own custom instantiation of http.Transport matches http.DefaultTransport, so that the tests scream loudly when upstream pulls this shit again: https://github.com/sapcc/go-bits/pull/309/changes
https://xyrillian.de (podcasts and blog) https://github.com/majewsky Mastodon: https://digitalcourage.social/@xyrill
What I say is often colored by my work experience, but opinions are always my own and not those of my employer.