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.
I spent a couple weeks planning a LFS install about 20 years ago. I then didn't have time to look at it all for about year, so I never went through with it. But I still learned a lot just documenting all steps and preparing with the worse case of not having decent internet if something went wrong.
I saw it years ago at the Printing Museum of Tokyo[1]. I think it was an original and part of their permanent collection, but I could be wrong. I know it was a woodblock print and they had a couple of with just a couple colors to show the process of printing with multiple blocks, each with different colors.
I don't see it listed on their website, but I didn't look too hard.
There's several options depending on how simple to
If you want it as a reference that gets thrown around, you could do a simple saddle stitch. This is commonly used for zines. But this doesn't work well if there are over 30* or so pages as it gets too thick. https://youtu.be/PncuvEajyWI
If you want it looking a little bit better with a hard cover, check out this link. It is still the same basic saddle stitch, but then adds a cover and a lot of finishing work. https://youtu.be/BfW0OiAFLkU
If it's longer than 30 or so pages, you will probably need multiple signatures. A signature is basically 30 pages stitched together and then the signatures are stitched together. There are a ton of options at this point. You could even get into the non-stitched bindings that just use glue, like a drum leaf. I recommend the videos at https://www.youtube.com/@DASBookbinding for a lot of options.
If you want something beautiful and you don't want to make it yourself, I'd recommend finding a local book artist who can make it for you. Or one online. Call you local art centers and ask around.
* The actual number is dependent on the the paper, the method, the tools available, etc. But 30 isn't a bad average.
My first job out college was at PTC first in tech support for Windchill and then as a dev for Windchill. Windchill is PTC's PLM/VCS for CAD files. I never really touched CAD. I launched PROe a handful of times, but mainly to test some integration into Windchill.
Over the course of 3 years there, I saw maybe 6 or so companies bought by PTC and nothing ever really done with them. Probably the most successful was FlexPLM which for some reason was built on Windchill to offer PLM type software for the apparel industry. It only survived because PTC ignored it.
PTC is a company full of too much bureaucracy and managers all trying to push features over completeness.
I think the biggest missing piece is find a local art store. Local indie places are amazing, but even a chain like Dick Blick is great. Even a craft store can work, but make that your last option. The benefit is that the employees are usually artists as well and can answer questions. Its great to ask "is this $100 thing really better than this $15 dollar thing?"
> It's a sort of rationalist's advice in that it seeks to match a consensus bell curve. Much of it is good advice but there are lots of exceptions that ought to be tweaked through subjective practice.
My wife is an artist, and by the law of association, I have I many artist friends. I would say that starting out, the good advice that matches the bell curve is great for getting started. Learn the basics before you break the rules. That way you know you are breaking the rules and why.
> It’s sometimes said this Alpine stuff is a premature optimization, but in most cases it’s not even an optimization.
Not always. If you have thousands of containers running, the network cost* for changing the base image is massive because each instance needs possibly all new layers, not just the last layer or 2. Having a smaller base image is very practical at this point.
* And for network cost, there is both the literal cost with egress from dockerhub, or another registry, but also the load on your network infra.
I use to work at a place that included parking in rfid activated ramp. I always wanted to clone my badge into something sewn into the wrist of my motorcycle jacket so I didn't have to fumble for my badge while entering and leaving the ramp. In a watch would be perfect.
I've heard that Ghost of Tsushima does this well with the direction of the wind. But I don't have a PS4/5 to play.
I've also heard about of platformers giving a couple pixels after walking off a platform to jump, like Celeste. It is very small thing to give better feel to the controls and make up lack of precise timing.
> Video games are a great example of simplified, intuitive interfaces which are often the polar opposite of calm.
Video games are interesting in terms of usability. I thought a lot about this the past couple years after a UX course. A lot of UX principles are about making things easier, like large clickable areas, not moving clickable areas, contrasting colors, proving plenty of time to react or undo, and making things obvious and as easy as possible. But in a game, many of those principles are flipped. In a shooter, the enemies are smaller and move. They may be difficult to see. Solutions are not always obvious, especially if they are extras or hidden power ups.
But at the same time, a lot of the UX principles are very important. An enemy about to attack should telegraph that attack so you have time to react. Menus should be very clear and obvious. Inventory management should not be a chore, the map and HUD should be easy to use.
If it isn't a hardship, I do recommend fixing your dad's watch. Sentimental pieces are always special.