varikin
You can almost think of the LTS releases as a major release and the non-LTS as a minor release, so really this could be 25.2. The current Java release schedule is to maintain a consistent and predictable release cadence instead of pushing big new features every 6 months.
If it isn't a hardship, I do recommend fixing your dad's watch. Sentimental pieces are always special.
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.
> 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.
I don't see it listed on their website, but I didn't look too hard.
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.
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.
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.
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'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 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.
https://www.ifixit.com/News/8448/apple-audio-adapter-teardow...
https://www.kenrockwell.com/apple/lightning-adapter-audio-qu...
Of course, once a lawsuit was underway, many backups were placed under legal hold and no longer pruned old versions.
I've been using 1Password for my personal accounts for probably close to 10 years and have been happy with it. There are some things I feel are clunky, but I've never felt like I was being tricked or deceived by the company.
edit: I seem to lost the ability to reply to your other statements.
Is he actually trying to make himself a better person? Other people have listed where he has made several statements over the years since 2006 that show that he hasn't changed what he thinks. Just because he was a pioneer in programming and created the idea of free software does not give him free pass the rest of his life.