[1]: https://tailscale.com/kb/1193/tailscale-ssh/#ensure-tailscal...
1,735 karma · joined January 31, 2013
[1]: https://tailscale.com/kb/1193/tailscale-ssh/#ensure-tailscal...
As we expand the types our generic code can handle, we have to refine the semantics it relies on. For a long time, Base.length(::AbstractArray) could mean “the largest one-based index of the array”, but then we started using the same code that handles regular Arrays for OffsetArrays and this interpretation was no longer valid. I guess the alternative would have been to leave length(::OffsetArray) unimplemented and block the valid use of OffsetArrays for all generic code that understands Base.length as “the number of values”.
It can still be difficult to tell what a function like Base.length should mean if I implement it for my types. For example, should it return the number of local values or the global length for an array that is distributed between multiple processes (e.g. in an MPI program)? Perhaps some generic code will use it to allocate a buffer for intermediate values, in which case it should be the local length. Or some generic code computes an average by dividing the (global) sum by the global length.
It seems impossible to come up with a precise definition of all the semantics your generic code assumes a priori, so we can either restrict our usage of generics to a small number of concrete types that were considered when the code was written, or we have to accept that we occasionally run into these sorts of issues while we refine the semantics.
Anecdotally, it has been my experience that packages that have been made to work in many generic contexts (such as the ODE packages) are likely to work flawlessly with my custom types, while packages that have seen less such effort (e.g. iterative solvers) are more likely to cause issues. This makes me hopeful that it is possible to converge towards very general generic implementations.
It is also worth mentioning that it is very possible to use Julia without ambitious use of cross-package generic functionality, and use it “merely” as a better Fortran or Matlab.
I find this is an important concept to keep in mind when designing systems and products. When you reach a certain complexity, most cases are edge cases and designing only for the “typical” case serves almost nobody.
https://nixos.org/manual/nixos/stable/release-notes.html#sec...
[1]: https://www.darktable.org/2021/07/darktable-360-released/ [2]: https://www.darktable.org/2021/07/darktable-3-6/
One issue I’ve run into is that it’s not always that easy to get the style of the SVG images right, especially when it comes to sizing & placement. Did you find a good way to e.g. ensure that inline equations have the correct baseline alignment? Or a good method to ensure that equation sizes always match the font size of the paragraph they’re in?
From what I understand, it’s really a trade-off between waiting for proper data about the efficacy you’re most interested in, or starting to vaccinate people as soon as you have efficacy data for an endpoint that’s still meaningful but easier to reach. Having much fewer symptomatic cases is already a pretty good result, and I think it was expected that the protection would also extend to severe cases.
[1]: https://www.nejm.org/doi/suppl/10.1056/NEJMoa2034577/suppl_f...
I imagine it’s possible to set up a ground-based network, but you would need a high density to cover large surfaces (you want to see at least four stations from every position). I also imagine that it would be difficult to get accurate vertical positions if the stations are all in the same horizontal plane.
[1]: https://en.wikipedia.org/wiki/Real-time_kinematic_positionin...
Looks like the website should soon be updated as well.
Another option that can work is to send a bill for the owed amount and if they fail to respond start the process of debt collection (Betreibung). It’s a pain and doesn’t work well for people who actually cannot pay, but for regular businesses where you’re stuck somewhere in their bureaucracy it’s a way to force them to respond to your claims that’s a bit less involved than straight-out suing them.
It might be hard to argue without suing, but legally there are provisions that if the AGB contain “surprising” terms, you have to be made specifically aware of them or they are invalid. There is currently a high-stakes case building because of this: Some of the epidemics insurances for restaurants had a provision that “pandemics” are excluded and won’t pay out for COVID-19, now restaurants are suing.
https://www.srf.ch/news/schweiz/epidemie-versicherer-kein-ge...
https://www.infomaniak.com/en/support/faq/2144/blocked-order