HN user
I’m a fan of the whole Apple ecosystem but I have to say that there’s a pattern here. Apple does a decent job of keeping my data safe from others but a terrible job of keeping it intact. From music libraries with song titles that got switched to long integers to this (and I’m sure more that I’m not remembering atm) they need to do a better job here.
Sure security is important but integrity is too.
If are doing this to ease DI and mocking, just use a mocking library that supports function mocks:
Does this mean .svc.cluster.local for Kubernetes should migrate to .svc.cluster.internal?
5xx for internal errors (these should be avoided at all costs)
An anti pattern I’ve often seen has devs avoiding 5xx errors in bizarre ways. I would change the above to make to have monitoring in place to address 5xx errors. By all means, let your code throw a 500 if things go off the rails.
Hi HN,
The primary goal (lock-free mocks for Go) is right there in the title but after converting lots of code, I've found the biggest payoff has been from generating more accurate code. Gomock's recorder uses a lot of `interface{}` functions. Moqueries always uses the actual type from the interface or function type.
I've documented the internal structures used by the generated code here: https://github.com/myshkin5/moqueries/tree/main/docs/anatomy...
Let me know what you think.
Thanks! Dwayne
I've been working on a lock-free mock library for Go called Moqueries (https://github.com/myshkin5/moqueries). Having a lock inside of your mock can cover up subtle bugs. The tool mocks interfaces which is fairly common but it also will mock a function type.
Looks like it's been down for at least three hours at this point with zero updates! Starting a list of other service providers I should switch to!