The article phrases this weirdly, but they are talking about the 40,000 Starlink terminals in Ukraine that Eutelsat is trying to match, not about LEO satellites.
What I miss in this article are some references to some of the great research on Starlink performance and characteristics that has come out in the past ~2 years. [1] and [2] come to mind. They also go into much more detail on the 15s interval, quote [1]:
> Interestingly, we observe that the Starlink OWD (one-way delay) often noticeably shifts at interval points that occur at 15 s increments. Further investigation reveals the cause to be the Starlink reconfiguration interval, which, as reported in FCC filings [71], is the time-step at which the satellite paths are reallocated to the users.
AFAIK it is not the dish itself that does the tracking but a central orchestration.
100% what I came here to say. My film camera restricts me from checking each photo instantly, keeps other people from checking each photo ("Show me! Do I look good in that? Take another one") or from sharing online.
As an added bonus, I get to relive my trip a few weeks later when I get my films back from the lab.
I have to add that I don't think any of my films were ever destroyed by an airport scanner.
>I have to add that I don't think any of my films were ever destroyed by an airport scanner.
That is a bit of a myth these days. Modern airport hand luggage scanners are safe up to ISO 800 or so. And from my experience airport staff is very willing to hand-check high ISO film (did an intercontinental trip with T-Max 3200 once and had no issue getting it hand-checked in 4 different countries - it probably helped that I separated out only the 3200 film and got all others scanned regularly)
I hear there's new CT machines which may cause issues, but apparently the staff is well aware of this and they should be labeled.
I like high grain images, but I also wonder if it's kind of a fad?
The ability of modern digital cameras to shoot essentially unlimited photos might not be without its drawbacks, but being able to shoot low grain images practically in the dark is pretty cool.
One caveat here is serialization. Writing your (or another package's) enum to a database will get you in trouble if you ever want to add another value in the middle. Sure, you can be careful and should document this, but who knows
Not only that, but the person sending you the serialized object might be looking for trouble. Sending you an enum value that is outside the legal range might help an attacker get into your system.
I'm not sure if its DDG, but the tech company Pipedream should consider rebranding or improving their SEO. A quick Internet search did not yield the results I expected...
I remember this coming up in a blog post by the creator of Shellcheck a while back [0] and being discussed here [1].
One reason given is this:
> Assuming the OSS projects aren't a conflict of interest
Apple is so secretive even internally that you can never guarantee whatever you're working on in your free time does not conflict what someone at Apple is working on secretly.
I also had everything working fine but performance is really bad when you go through rosetta.
For example, discord client is still x86 and while it works without any issues, the heaviness is noticeable.
Also, .NET 5 does not have an arm build (.NET 6 does but it is still in beta). The entire toolchain works but compiling a binary can be 3-4 times slower on the emulated one.
Things work without any issues though. They are just slow.
I was running the main ruby on rails app I work on via Rosetta since the first M1 MacBooks came out. The performance hit was there for sure, but not huge. Running local tests or seeding my database ranged to "about the same" to 10-20% slower than my 10 core iMac Pro, which is still a pretty fast machine.
Since I've upgraded the app to support Arm natively, almost everything runs faster on the m1 13" macbook compared to my 10 core iMac, with the exception of long running tasks that will use all the cores you can throw at them.
There have been some font rendering issues in Ultimaker Cura (which is written in Python) that ran as x86 on M1. These have been resolved in the Python library.
