Better not, it would just get me even more pissed off at how crude and incompetent German traffic engineering is. Pretty sure some frustrated worker is making it worse on purpose - you don't reach certain peaks of crappiness accidentally, it takes _work_.
Can't speak to Germany, but one thing I like in the Netherlands is that if you approach an empty intersection the light will automatically turn green for you. Have never seen anything like that in North America.
And the roads themselves are good in NL (huge contrast when I moved to Montreal, where we'd have a metal mesh underneath bridges to catch falling concrete)
According to Claude, NL only has 5500-6000 signaled intersections and of those approximately 900-1450 are of the type you are suggesting (iVRI). The benefit is also higher in NL due to the density and amount of cyclists. iVRI is also not latency sensitive and so installation costs are low as signaling can traverse the regular cellular network.
In the US, we have many more lights due to the road layout (grid). There are more than 3200 signaled intersections in my county in California alone despite being 1/14th of the land area of the NL.
The robot also estimates that there are 300,000 signaled intersections in the US. We honestly don't know how many there are because they are all operated by different agencies.
For US arterial roads iVRI has limited benefit. So the focus in the US has been on V2X development which focuses more on crash avoidance and has much higher installation costs due to latency requirements. In the end there's a lot of low hanging fruit here in the US if signals could just be retimed.
NL has one procurement entity. In the US there is no single coordinating entity to standardize traffic lights. Each state standardizes its own lights and then each municipality handles its own procurement.
I don't know the numbers, but I live in NL and I can't recall the last time I encountered a traffic light that just runs on a timer; as far as I know just about all traffic lights have some awareness of traffic.
Lowering the number of traffic lights in and of itself is a good idea. Overpasses and (turbo)roundabouts, clever right of way, better road hierarchy; there are lots of alternatives that may provide better throughput and more safety for a given intersection.
The Netherlands as a country with 18M inhabitants is best compared to a big city with the surrounding metro area.
It happens in the US but is rare. Mostly it's a road servicing a well connected person or wealthy neighborhood that gets the dwell time reduced to nearly nothing.
There's an annoying one near me at the bottom of a hill where anyone approaching from the sidestreet will ruin the descent on bicycle, even if they were turning right (from a dedicated turn lane) and didn't need the light to change for them at all. Another is a former police station now used as a park facility. Cars entering the parking lot only need to barely brush over the sensor and the light changes instantly for no reason because they never reprogrammed the light when the police left.
> you don't reach certain peaks of crappiness accidentally, it takes _work_.
Have you really never seen what happens when something grows organically without global maintenance? Not saying that this is what happened in Germany, but "it takes work" sounds naive.
It doesn't take work to write a crappy codebase: all you have to do is add code without really caring about the overall architecture.
Or said differently, if you can fix the German traffic engineering, you should apply there because I'm sure they would be happy to have an easy and perfect solution.
What's your issue with traffic in Germany? I know it depends on the city/state, but it always seemed pretty okay to me (though I haven't been driving much in other countries, so I don't have that much experience with "better" systems)
From what I've seen about US traffic, there doesn't seem to be much to be envy of.
Most intersections are atrociously designed. Protected left turns everywhere, with their own lane and their own traffic light causing slowdowns and triggering also when nobody needs them.
Many pedestrian crossings could be moved 10m further from an intersection, allowing up to a couple of cars (wishing to turn right) to wait on the pedestrians without blocking all the people who were just going to proceed straight ahead. On the other hand, this problem would often not even occur if we hadn't wasted a lane for a protected left - there now would be a dedicated lane for those going right.
Right-on-red is legally permitted (there's a dedicated street sign for it) but almost never implemented. It's so frustrating.
An overwhelming majority of the traffic lights I encounter is completely non-adaptive. I wait an average of 40 seconds every morning at a specific one which is, in aggregate, causing entire human lifetimes of wasted time on a monthly if not weekly basis.
Zebra crossings are often outfitted with a pedestrian traffic light which is red (rather than off) by default. If the road is completely clear, you could just cross, but no, you must press, wait up to half a minute, and finally it turns to green for you. Now you also stopped a car or 2 which need to wait for your green to finish. If it defaulted to OFF, you could have crossed 20 seconds ago without interrupting anybody's life, and the traffic light would still still be available for elderly or disabled (or whomever wishes to press and wait, while not having it as a default).
I have an English/Italian bilingual keyboard set up as my default.
Every single f**n time I begin a sentence with "È" (Italian for "she/he/it is") - which is an extremely deliberate gesture - you have to keep the E tapped until the accents pop up - it will immediately correct it back to an unaccented "E". It's nuts.
There is a metric ton of intent behind my selecting, keeping tapped, waiting for the accents, picking one - it's so obviously NOT accidental, and this utterly cretinous piece of junk changes it .
Can't "autocorrect" be replaced to "autosuggest" instead like on android devices?
I have never been fan of autocorrection tools (especially as I am regularly writing in 4 different languages) regardless of the OS but definitely use autosuggestions to correct potential spelling errors.
Yes, the keyboard is pretty bad in various ways. I’m still surprised how many comments in this thread (and similar threads in the past) are mentioning the autocorrection, implying that they haven’t turned it off.
I have French / English and every time I start my sentence with "The" (obviously the start of an English sentence), it autocorrects as "Thé" (tea). There's veeeery few situations in French where a sentence can start with "Thé".
The raise is even worse if you look further back than 2021. Netflix was 7.99 for ages, while the "floor" in 2021 is 13.99. Against the original baseline, the new 19.99 price is not a +43% but a +150%.
Most importantly 13.99 already in 2021 bought LESS than 7.99 or 8.99 bought until a while before. Thanks to the fragmentation, the catalogue was way larger before, and as of 2022 ads were introduced to further insult the customer.
You go significantly deeper? You're aware that shortly past 50mt the partial pressure of oxygen causes neurotoxicity, leading to convulsions and death? Anything happening past those depths involves extremely expensive hardware, custom trimix breathing gases and most importantly a hell of a good reason to even bother doing it - that is NOT the environment for an Apple Watch.
Yes, I go significantly deeper. You seem to be a little confused about how oxygen toxicity works but rest assured that we're aware of it and use appropriate breathing gasses for the depth.
I understand that an Apple Watch Ultra can't be used for those dives, and that's fine — they don't need to support every possible niche use case. But competing smartwatches from Garmin and Suunto do handle deeper dives and the associated gas mixes. There's nothing stopping Apple from doing the same if they want to.
> You seem to be a little confused about how oxygen toxicity works
Thanks for the condescending tone. Am I?
At 1.4 bar of O2 partial pressure (therefore, with a 21% breathing gas mixture, at around 66m depth), oxygen toxicity causes convulsions and unconsciousness. If someone doesn't grab you and take you up, this likely results in death.
Btw I had to google the precise values and depths to be accurate, but I'm not talking out my ass. I'm a certified CMAS and AOW diver with 80ish logged dives. Hardly a veteran but this was in my certification course and it's a very real thing - enlighten my confused state with your better knowledge please.
You're talking out your ass and unclear on the basics. Obviously we're using standard gas mixes based on the depth profile, not compressed air. For the working portion of the dive we generally limit PPO2 to 1.2 atm but will go as high as 1.6 for portions of the deco. If you'd like to understand diving physiology instead of just repeating what you Googled then Bennett and Elliott is a good place to start.
A weekend? How about a full week at the absolute bare minimum, if not more.
3 days is a complete joke. Competitors have battery lives measured in weeks rather than days (a famous, and still 100% appropriate, quote by Garmin. Now 5 years old and counting, and the situation is still as ridiculously bad).
Seriously what is it even doing to justify going through the battery so fast? Are they just bad at programming?
I completely agree with you, I was just trying to avoid being attacked by a certain group. I assume it's the processor as it isn't designed specifically for battery life etc.
Which don't exist. BMW famously tried to blame Apple for trying to charge buyers an annual fee for Carplay and Apple _publicly_ called their shit out. They confirmed they don't charge anything - neither one-off nor recurring. Manufacturers may incur certification costs, there's nothing after that.
Just did a couple quick searches and nothing's changed since then AFAIK
According to their MFi page, there may be a royalty, as Apple says that information is covered by NDA. (including the authentication coprocessors required for CarPlay)
"What is the royalty associated with MFi accessories?
This information is only available under NDA. You will be able to review this information once your application for the MFi License has been approved."
I hate the banners and the ugliness too but they are designed precisely to do that, and adtech maneuvers to ensure the hate is directed at the wrong source - the lawmakers instead of the people doing all the spying.
GDPR 1.1 should address all that - no legitimate interest exclusion of any kind, ONE SINGLE CLICK to reject all, no witholding service at ANY degree unless consent is granted, a 3rd option (I offer to pay to not be tracked), and a mandatory disclaimer on the cookie banner saying in clear terms: "Tracking is spying. If we were not tracking you and invading your privacy, this banner would not be necessary at all". Maybe even revive the "do not track" header by mandating that websites react to it accordingly, obey it 100%, not even show a banner if the header already tells them what to do, and ask users if they want this set or not, without a default value which would give an excuse for complaint from the people spying on you.
I also read the post, and have handled multiple GPDR adjacent migrations in Asia.
The end result is still the same, even with GDPR 1.1, another interstitial barrier between the user and whatever site they are trying to reach imposed by a poorly planned attempt to protect user privacy while simultaneously enabling the predatory companies who violate said privacy to continue business as usual.
The cookie banner will remain on the vast majority of sites, and users will spam click past it as they have been trained to do.
This is a fantastic idea and I'd like to add my voice to the choir asking you for more information :) Don't let us rebuild everything from scratch if we don't have to
It's my impression that the killer robot industry has focused primarily on dog-shaped robots over human. Being bipedal gave us a lot of advantages, but "incredibly fast runner" isn't one of them.
Usain Bolt is incredibly fast for a human, but cheetahs are twice as fast still (and, presumably, can climb stairs too).
I do appreciate the engineering achievement on its own, but there seems to be an implied "and will replace humans" vibe here that doesn't make a lot of sense to me.
What's next: Waiting patiently, as the perfect sniper.
First hiking 10 miles into enemy territory. Then laying down in low-power mode, for 120 days. Finally waiting for "important enemy person" to pass by, and then using a weapon with super-human sensory skills + weaponry. Note - Does not need to be humanoid.
We need to start Waging Peace, as our ability to kill each other is outstripping our willingness to live peacefully together.
Yes, and if you have the PCIe lanes (say, an x16 lane - actually delivering 16 lanes! - to each GPU) it's also quite performant - it's called a tensor split in llama-server.
If your motherboard/cpu doesn't actually have those (few do outside some xeons, epycs and threadrippers) you can still do it - it's called a layer split and will work even with 1 lane per GPU. Each GPU will work at its maximum speed, but only 1 will be active at any given instant - imagine a relay race.
(Didn't mention which PCIe generation - obviously the higher the better. At v4 and up, even 8 lanes per GPU would be enough for a performant tensor 4-way split)
Edit:
If you have more than 1 user at a time, the GPU can actually all be working all the time, if there are enough parallel requests to serve. But you need enough KV cache for all the sessions you're running in parallel.
reply