For a Seiko, I'll also recommend https://www.theseikologist.com/. As his name suggests, he specializes in Seikos and has a large stock of vintage Seiko parts which are hard to source. Though, it's still not cheap. I have a broken Seiko chronograph from the 70s and he quoted $500 to just do the watch equivalent of a tune up. He can't give a better estimate without opening it up, which is understandable.
If it isn't a hardship, I do recommend fixing your dad's watch. Sentimental pieces are always special.
Have you had issues with the .jhw TLD on Apple devices? I have my own DNS for my homelab with CoreDNS with house.hill as my domain. My house is on a hill. But .hill is not a TLD, and both my macbook and iphone stopped resolving it quite a while ago.
Think of uv more as like npm or other thing like that. The new Python pyproject.toml is similar package.json. It defines the project description, list of dependencies, and other hooks. Uv is a package/project tool using pyproject.toml. It is easy to manage dependencies, build and publish to PyPi, add hooks to run tests, linters, or whatever, again much like package.json. It also manages the virtualenv automatically, though you can manage it yourself.
Equating a frustrating anti-pattern of websites with medical equipment failure is extremely disingenuous. An infusion pump failure can harm a person, and according to the article, has seriously injured at least on person. Hijacking the back button isn't going to physically harm someone.
Streams (FP in java) is slower than for loops for a couple reasons. A big one is java doesn't natively support real closures or lambdas. It does have syntax for them, but that is just syntactic sugar for an class with a single method under the hood. So streams end up doing lot of object allocation and garbage for the fake closures.
Also, streams operate on objects, so they have to be on the heap. You can't use them with primitives on the stack. Though with autoboxing, the JVM may play some tricks with a list of Integer objects really being primitives on the stack, but I would never count on it.
As for SIMD, Java isn't going to parallelize anything automatically. You need to tell it you run the steam in parallel which will split it into threads. Java doesn't have lightweight threads like coroutines.
I know lightweight threads are on the roadmap and maybe available in Java 21 or newer. I know real closures have been considered, but I don't if it's gone anywhere. It's hard to do a quick search because we got "closures" in Java 8 so theres a lot of noise.
And as a caveat, I am most familiar with Java 17 (and older). I expect we'll look at moving to Java 21 (current LTS) next year.
I believe the LLV line was only suppose to be in service for 20 years, but the government gonna government and not find a replacement till it's almost too late. So yes it was a lot of scrounging and probably a lot of USPS mechanics needing to be creative, but the LLV lasted twice as long as it was designed for. I expect this same conversation will happen again in another 40 years.
> Four variants of the NGDV are expected to be in fleet use: both gasoline-powered and battery-electric, in either front wheel drive or all wheel drive.
So I expect the front hood is for the gas powered engine for those variants. Further down, it talks about only 10% will be EV at the start due to cost. Also, this is in partnership with Ford so the ICE power train is the from the Ford Transit van.
All the Jetbrains IDEs have their own custom linter. It's pretty good, but my complaint has always been the inability to use it in CI/CD and to generate reports. The way I read this, they pulled their custom linter out of the IDEs and made it a standalone tool that can be added to CI/CD, which is great.
If it isn't a hardship, I do recommend fixing your dad's watch. Sentimental pieces are always special.