You'd build an array (see e.g. VLA mentioned in the article or SKA), and it is much easier to combine the data from an array if everything isn't flying around and so there are varying distances between the antennae.
Not for radio telescopes, but how is the current state of optical interference? Would it help if we didn't have to use adaptive optics to compensate for atmospheric turbulence (and have subtly different images at the different telescopes)?
No, it very much does. If you want to join two network segments such that on one side all devices are on 10.1.X.X and the other all devices are 10.2.X.X, you'd use a mapping between 10.1.a.b and 10.2.a.b
The general context here is about NATting to the public internet at large, not between particular segments. And the parent of my comment was talking specifically about NAPT, which is different from the non-port-based NAT that you're talking about.
Send packets to the device? A NAT is in it's most basic form a mapping from one IP/port set to another IP/port set describable by some function "f" and its inverse "g". The common home user case has the firewall detect a flow from inside the network and modify "f" and "g" to allow this flow. Without the firewall, and assuming you want your devices to talk to the internet in some way, the NAT would forward (with modifications) traffic based on "f" and "g" to all your devices.
It also has weird definitions. Is nix a virtual environment? Is homebrew a virtual environment? Why is a sandbox different to a container? Type-1 vs Type-2 hypervisors are quite different, and there's no discussion about processes vs threads.
I think there's a fair amount of variability in experiences. I switched to AMD after getting fed up with multiple Nvidia cards having odd issues (though I'd use Nvidia if I were doing ML work). Mac hardware as a general rule has always been at least decent (if not good or better), but Mac software has generally been going downhill, so if for whatever reason Mac OSX/MacOS was not appropriate, it's easier to set up what you need on a non-Apple machine (of sufficient quality) than install a different OS on the Mac.
There are those that have well defined extension points (e.g. TeX, rst), and those that are ad-hoc, of which the best example is markdown. TeX, via packages and wrappers, can do practically anything. rst has directives (blocks) and interpreted text (inline) which can also effectively do anything (along with substitution references which are more macro-like). Specific "interpreters" (for lack of a better term) which you link to naturally have specific features by default (and some are more extensible than others e.g. pandoc which when writing out LaTeX lets you embed LaTeX in the markdown, so "markdown" in this case is turing complete).
I think if you define "better" as having well-defined extensibility to enable multiple implementations (i.e. not ad-hoc things pandoc lets you do), then rst (which can be transformed into XML as per https://docutils.sourceforge.io/docs/ref/doctree.html) would be "better" than markdown.
That's not exactly encouraging... My biggest gripe with typst is the various design choices which make writing maths much harder than LaTeX (and given many of the issues with LaTeX usability come from having to use poorly maintained legacy packages, not having basic functionality in the core of the replacement seems naive at best).
Steam exists, and provides features desired by both users and developers.
I'm not sure getting software directly from developers is less likely to break than getting it through a store. The store may do QA to ensure that broken apps cannot be uploaded, developers may vanish and hence absent someone else being able to maintain it the app will eventually break, and how are security issues handled?
reply