sudotstar

Only thing I can think of is that it hides from your friends if you've played the game an extreme amount of time immediately after purchasing it, though if you exit the 10 day period with close to 240 hours in the game that's gonna show that off anyways.

I was aesthetically a fan of the Fossil watches, and was using a Fossil Sport (1st gen) for quite a while. Unfortunately the layers of proprietary-Fossil required software/watchfaces on top of the layers of proprietary-Google WearOS hampered the software experience a tiny bit, and the frankly poor hardware quality marred the experience significantly. My charging band coil in the watch completely dislodged itself (it appeared to be held in with glue), rendering the watch unusable.

Fossil's customer support was excellent, replacing the device fully when this happened, though that was when that model was still on store shelves. I recently inquired about getting a replacement battery and was told I can just trade it in for 50% off a current-gen model, which while being far more generous an offer than I expected, still leaves me hesitant to upgrade to another device that suffers from the same problems and is in danger of being outright discontinued.

At this point I don't really need/want a WearOS device specifically, and would actually prefer something that's less tied to Google's whims, the hardware OEM's whims, and whatever the interplay is between those two companies. I've been eyeing more hobby-oriented projects like bangle.js or the PineTime smartwatch, but the fact that I'm even looking in that space shows that it's become a device I would get for tinkering, not one I strictly "need".

Thank you for your review, I think this is enough information for me to hold off on this game, potentially until a non-Switch release or some other updates.

I am a huge fan of the original DQM series. DQM2 (released as Dragon Warrior Monsters 2 in the West on GBC) is a game that I put in a lot of time into as a kid, and is a game I still regard today as one of the best experiences I have ever had in a monster catching game, or even most JRPGs in general. The balance between the game's minimal-but-still-present story, the immense amount of post-game content (seemingly infinite randomly-generated worlds to explore and find new monsters in), as well as the incredibly in-depth monster breeding trees is, for me, the exact perfect balance I want out of a game and few others have really scratched that itch as well as DQM2 (mainline Dragon Quest IX is probably the closest I've gotten). While a lot of those mechanics, particularly the "randomly generated content" as well as the "deep" monster breeding trees, don't really hold up to modern scrutiny and are put to shame by what hardware more powerful than the Game Boy is capable of, I haven't yet found a more modern game that provides a better version of that specific experience.

The newer Dragon Quest Monsters games (I've played through Joker 1, and tried the definitive versions of Joker 2 and 3) haven't really done it for me, and a big reason is just how "clunky" the games felt to play compared to the original. I was hoping this game going back to the "mainline" branding would also signify a return to DQM2's seemingly infinite content, but that does not appear to be the case, and the atrocious performance of the game on Switch would probably just leave me reaching back for my GBC and DQM2 again.

On my Thinkpad 2in1, the behavior your desire is what I get. I'm on Fedora KDE (Kinoite) which pre-installs Maliit by default though, I'm not sure if it comes with some additional configuration.

In this case it's referring to the fact that the OS is built upon the same containerization technology used on cloud platforms such as Kubernetes. As a marketing tool it's a bit buzzwordy, but it's not about running the core OS components outside of the physical machine here.

I'm curious to hear about yours and others' experiences with containerizing Java applications in such environments. I used to work in a place that traditionally had such restrictions on JDK versions, but after the internal IT environment moved towards running applications within containers, either on Kubernetes or on public cloud platforms' container runtimes, that restriction became unnecessary since the application would be shipped to production alongside its compatible JDK.

While there were still restrictions on exactly what JDK you could run for other reasons, such as security/stability, common developer experience, etc, it at least allowed teams to immediately adopt the newest LTS release (17 at the time I left) with little restriction.

I'd probably pick something esoteric and then just stop programming, tbh. I enjoy being a polyglot programmer, and learning many languages and learning from many ecosystems is incredibly interesting to me, far more than hyper-specializing in a single language would be.

Even if the performance is only mediocre, the gameplay will hold up. The game uses a fresh new combat system that merges action combat with turn-based gameplay, the likes of which I haven't really seen in any other game including past Trails entries, and it's absolutely a great time.

For the original PS4 release, Falcom released a fairly comprehensive demo that allowed you to play through the entire first chapter of the game, and carry over your save to the full release. They've also done something similar with Ys X which released on Switch day 1, so hopefully the Switch version gets a similar demo for both the Japanese and Western releases so you can try-before-you-buy.

I'm interested to see how the game performs on Switch. I played the Japanese PS4 version which was rough at launch but improved with post-release patches. I expect there are going to be some necessary cutbacks (no 60FPS, lowered render resolution, reduced visual effects, the standard fare) but that shouldn't impact the quality of the game experience at all, it's a wonderful entry and a great starting point for newcomers in a long-running series that rarely ever has those great starting points.

I think logistics management issues are a classic example of "first world problems" in Factorio, but it did feel like a pain in the butt to manually manage personal trash slots, similar logistics requests across multiple similar objects, and whatnot.

I didn't know I needed a solution to that problem, and I didn't expect it to be specifically in this format, but I really like what I see. I especially think the named groups will go a long way in e.g. a multiplayer Factorio session where some people but not everyone is into setting up complex logistics systems, allowing everyone else to at least understand and use the system and its benefits even if setting things up is left to the experts.

It's unfortunate, but it's understandable if effort needs to be focused on a single good UI widget ecosystem fully under Mozilla's control, rather than living by the whims of the three major desktop UI toolkits they have to support, as well as the hundreds of thousands of web pages that are exclusively designed and tested against Chrome which already has been using non-native widgets across desktop platforms for a very long time. I'm not in the web dev space anymore, but I'd constantly see sites built that were incredibly dependent on the exact pixel sizes of widgets as they would render in Chrome, and would visually fall apart on Firefox, or with other zoom/text size settings.

UI design across Windows, macOS, and Linux GNOME/KDE have converged enough that it's probably good-enough if Firefox continues down the path of just theming their own widgets with the OS/user's color scheme where applicable, and calling it a day.