In Melbourne, Australia, a long time ago, they embedded weight sensors in the road for a lot of intersections, so they can react dynamically to traffic conditions.
I live in Berlin, which doesn't have such sensors and it's always frustrating waiting for lights to change when there's no traffic.
Are you sure they're using weight sensors? AFAIK wire loops seem much more useful, plus they have the advantage of also picking up bikes and other lightweight traffic more accurately.
I can also tell you that even in a country with sensors all over the place, I do sometimes end up waiting on an intersection with no traffic. I assume it's some kind of public transportation/emergency vehicle priority system activating, or maybe it's an attempt to calm traffic downstream where loads of traffic has piled up already so intersections don't get blocked.
Either way, adding sensors doesn't necessarily make traffic lights immune to unnecessary waiting times.
From what I've heard, they don't always use the sensors; sometimes they're on a fixed schedule during the day and on request only overnight. Or they might be a fixed schedule always; a classmate at uni did a project around modelling traffic flow and found an intersection or two that turned out to be configured differently from how the council expected; probably a setting that was changed once and never revisited.
I've seen this happen as well, but on different time slots. I think some of it is intentional (the algorithm designed to regulate busy intersections across an entire main road probably doesn't work well when there are only a few people on the road). The ones that operate on a timer all day every day seem to be bugged out, though.
OTOH, I don't understand by the big cloud platforms don't support caching, or at least make it easy. Azure pulling container dependencies on every build just feels rude.
I.e Docker terms of service restrict distribution in this way?
Is there any technical restraints?
I.e Docker specify no-cache
I expect Docker don't want their images cached and would want you to use their service and transform you in to a paying subscriber through limitations on free tier.
My feeling is the way the naming scheme was defined (and subsequent issues around modifying the default registry), docker wanted to try to lock people into using docker hub over allowing public mirrors to be set up easily. This failed, so they've needed to pivot somewhat to reduce their load.
These platforms do cache quite a bit. It's just that there is a very high volume of traffic and a lot of it does update pretty frequently (or has to check for updates)
Seconding, though it does require some setup at least for self-hosted. Gitlab also has a full container registry built in, so it's not difficult to pull the image you want, push it to gitlab, and reference that going forward.
Yeah I don't get why I have to setup caching myself for this kind of thing. Like wouldn't it be more efficient to do it lower down in their infra anyway?
As someone mentioned, GitHub has something to prevent this, but it's unclear (or at least undocumented) what.
We at Depot [0] work around this by guaranteeing that a new runner brought online has a unique public IP address. Thus avoiding the need to login to Docker to pull anything.
Subsequently, we also do the same unique public IP address for our Docker image build product as well. Which helps with doing image builds where you're pulling from base images, etc.
I'm curious about this regarding GCP as well. I have a few Cloud Run Containers set up pulling their image directly from Docker Hub, then injecting my single config file from a Secrets-Manager-backed volume mount. That way I don't have to maintain my own package in GCP's Package Registry when the upstream project only publishes to Docker Hub
I opened this on Twitter using the in app browser on iOS 16.4, after I closed the browser, it continued to play the music whenever I bring twitter to the foreground!
Yes. A good error message should include an instruction to the user. Even the error reason is optional. An error code with nothing else is the bare minimum for an error to be worth a message in my opinion. Otherwise it’s just as useless as the software becoming unresponsive.
The infuriating thing about it is that it WAS you (as in it was something you did that you could fix) and it was NOT "us". Those are the worst type of error messages, where they dissuade you from finding the cause.
"It's not you, it's me" is a clichéd phrase when breaking up with someone [0]. It's often not genuine, and even when it is, it's still a degrading situation for the receiving party. "It's not you, it's us" can be taken as a quip on that. It's unnecessarily cute at best.
Using Java code for things that are this performance critical doesn't feel like a good idea. It will work of course, but it will probably GC a lot, and while modern JVMs do JIT, the code they generate can't be as optimal as something that has manual SIMD optimizations.
Honestly, you'd benefit more from idiomatic bindings rather than a pure Java implementation. There are quite a few high quality Java libraries that wrap C/C++ code but maintain a nearly 1:1 API, which is what ends up making them difficult to work with. OpenCV is a good example of this.
This triggers the question: why is the app not available worldwide in the first place? And why should every country develop their own? Since Apple and Google are already providing an "Exposure Notification system", shouldn't such an app be distributed natively (i.e. not through a geo-blocked app store), like the Phone or Compass apps? I understand this would mean the app should be developed, or at least released, by Apple and Google directly. But since they're already helping out with the notification system, we're halfway there. I also understand there are lots of legal and regulatory implications for having a worldwide app, but I feel like we're past this point already.
Sorry if I'm sounding naive, but people are going to start traveling again, so limiting a tracing app to a country's borders seems arbitrarily inefficient to say the least.
The hard part isn't building the app, the hard part is integrating with the health administrations in every country. In Germany alone, there are nearly 400 county health administration offices to interface with.
It's not a single app. Apple and Google provided common APIs, but there isn't an Apple/Google "app".
There are lots of different legal requirements, and the app points towards the local testing regime for example which is different in every country.
The Apple and Google roadmap already discusses that future items include more interoperability to enable international travel, it's just not a v1 feature.
I think the problem is that there is no single definition for many things around this app. Each country has a different definition of what constitutes contact for example.
This is actually a problem. I’m in Sweden, but as it’s really hard to transfer my Apple account from the UK (especially with a family account) I’ve never bothered. So am I going to not have access to Sweden’s contract tracing app if one is built?
I have gotten a visa and worked in other countries with less effort than trying to move app store. I just don't get it.
I now live in Finland, with a Finnish address and bank card and everything and I still can't get the damn thing to change. I refuse to accept that it is a technical impossibility to have a UK bank app and a Finnish one (for example) on the same phone.
My experience here is similar and not resolved after several years. My phone now now happily installs US apps (after starting in the UK) _except_ that it will not update the Google Fi app, but my watch with the same account complains every 15 minutes about being in the wrong store with no way to resolve it.
I do have apps from both stores installed on my phone now (after a lot of trial and error), but believe there is a special place in hell _anyway_ for companies providing services like delivery who do not add their apps to stores globally (looking at you, Doordash). Do they think a tourist or business traveller never wants to order lunch to their hotel?
A general rule of software is that any bug that a US-based developer or QA tester wouldn't easily be able to trigger can remain present for a very, very long time.
I live in Berlin, which doesn't have such sensors and it's always frustrating waiting for lights to change when there's no traffic.