Like the other replier and GP, my Linux and Mac desktops run for months at a time without a restart. I only restart when there's a software update that demands it. I don't have much experience with modern Windows, but I expect that's the norm from a modern OS.

If you're running into runaway resource issues like this then you may want to spend a few minutes hunting them down and maybe replace the programs responsible. Daily restarts shouldn't be necessary.

Apparently not in Windows settings:

If the BIOS says it supports Modern Standby, Windows takes it at its word and completely disables the ability to enter S3 sleep (classic standby). There’s no official or documented option for disabling Modern Standby through Windows, which is incredibly annoying.

Side note: for a while, there was actually a registry setting you could change to disable Modern Standby on the Windows side. Unfortunately, Microsoft removed it, and to my knowledge, has never added it back.

I'm not a Windows user, so I can't confirm one way or the other, but toward the end of the end of the article the author gives vendor-specific instructions for disabling the S0 Low Power Idle capability from BIOS.

I had the same experience with News.

I use RSS very selectively, though. General news sites are too much of a firehose: instead of RSS I just picked a few favorite sources and check them occasionally – usually once in the morning/evening. I also read The Economist's briefs (requires a sub) to catch up on stuff I missed.

Always been very curious about Mimosian banquets, but I doubt I'd get the hang of antimatter chopsticks.

Perhaps I'm better off with the answer I know to be true: Old Cap'n Janeway's Finest Organic Suspension.

For anyone as confused as I was: yes, this is indeed a link post on lemmy.world pointing to an article on kbin.social hosted by kbin.projectsegfau.lt and ultimately linking to social.bbc.

The old Fedi switcharoo.

I like the mini but this table highlights its major disadvantage. I still find its battery ample for a typical day, there's just not a lot of headroom for degradation.

From the title I was hoping for an investigative piece on Apple's payment model and whether it treats classical musicians any better, but it's just a comparison to other streaming services padded with trademark New Yorker bloviation.

tl;dr: they don't like Apple's editorials, prefer Idagio's search results, and everything invented after the phonograph was a mistake.

Alex Russell is a good read on React. His position gives him a broad view of its impacts and has kept him from being sidelined. This Changelog podcast is a decent distillation of his criticisms – it was recorded earlier this year, a few days after his Market For Lemons blog post.

(Sorry for the late reply! I've been a bit swamped lately and away from kbin.)

"Good vibes only" seems to be embedded in the culture of web development today. Influential devs' Twitter accounts have strong Instagram vibes: constantly promoting and congratulating each other, never sharing substantive criticisms. Hustle hustle.

People with deep, valid criticisms of popular frameworks like React seem to be ostracized as cranks.

It's all very vapid and depressing.

Thanks for this. I skimmed the proposal doc itself and didn't quite understand the concern people have with it – most of the concerns that came to my own mind are already listed as non-goals. The first few lines of this comment express a realistic danger that's innate to what's actually being proposed.

It's funny that the author didn't think to try Music.app instead of doinking about in Finder. I just did this a couple of weeks ago with my own iPod Classic: Music supports iPod sync just fine. (Yes, still!)

"Casual rescue mission" is a fun phrase. It fits, though. The first bloke I "rescued" in the demo was snoozing like Gulliver when I found him.

Just tried the demo yesterday. The tutorial's integrated into the gameplay in a way that didn't feel obstructive to me. It's less like an old-school sandbox tutorial and more that the game makes it obvious what you have to do for the first mission. And it seems to focus on the new mechanics since the basic stuff is already made obvious by overlays showing the controls.

There will be people who have no capacity for nuance and see this as a boolean thing, and for them: the tutorial's not skippable, no. But for most people, it shouldn't be an issue.

Pikmin 4 may be worth a look, then. The time limit's been removed for this one.

It's surprising that Apple isn't listed (among those backing the scheme) given that the company designed the HomeKit standard with security and privacy as key objectives.

I think that's the conflict: Apple has its own certification programs. From Apple's perspective, a successful government-backed trademark would compete with Apple trademarks for consumer mindshare and the certification would add new overhead to Apple's own product launches.

Other brands backing this program have more to gain than lose from it, e.g. because their own certifications aren't as well marketed, or because it simplifies product screening, or sets up new hurdles for competitors. Apple's in a unique position where none of those benefits are relevant. It only sees the costs.

The one thing I don't like about its navigation mode is that it can't be used for anything else at the same time. If I start walking directions to a restaurant and then someone asks me what time it closes or if there's a bar nearby then I have to cancel the navigation or use a different app to look that up.

This got me to look up iFixit's guide to Switch battery replacement. It's better than some of my devices, but as soon as a replacement involves spludgers and adhesive it crosses a "yuck" line for me, going from something that looks kinda fun to sort of dreading that I'll break it.

For contrast, past Nintendo handhelds made this a doddle, even in the post-AA era: here's the New 3DS battery replacement guide. The DS Lite even had a little battery door.

Priced at $1,599, the ViewFinity S9 has the same price tag as the Studio Display from Apple, but Apple charges an additional $300 for Nano-texture matte glass and $400 extra for a tilt and height adjustable stand.

A lot of Apple users feel the Studio Display's overpriced, so it's interesting that Samsung isn't competing on price.

If I were deciding between the two, and it didn't come down to unique features like portrait mode, then I'd want to see them side by side in a brightly lit room. The regular (non nano-texture) Studio Display handles most reflections decently well, but if the ViewFinity does much better then I can see that being a plus for an office setting where you have lights or windows behind you. I'm sure the nano-texture does better yet, but it has some trade-offs and cleaning requirements that make me very reluctant to recommend it. (I don't like that the wording above suggests nano-texture is a regular matte glass. It's not. It's better in many ways, but it's not for everyone.)

I use offline maps a lot. The article mentions a major reason: traveling, especially abroad, with limited or no data. It also comes in handy when we drop out of cell service, which happens more often than I'd expect outside of major cities in the US. My favorite app for those use cases is Organic Maps, which lets me download maps by city, state, or country.

I use offline maps for hiking too, but it's such a different use case that I find I want an entirely different map type and UI – one that focuses less on roads and directions and instead surfaces tools for route-planning and managing tracks and waypoint markers. Gaia's long been my favorite app for that.

This later article makes it sound like the issue was with websites using UA sniffing:

For instance, after applying the RSR updates on an iOS device, the new user agent containing an "(a)" string is "Mozilla/5.0 (iPhone; CPU iPhone OS 16_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.5.2 (a) Mobile/15E148 Safari/604.1," which prevents websites from detecting it as a valid version of Safari, thus displaying browser not supported error messages.

I hope Apple's use of the Rapid Security Response system here was mostly an infrastructure test. I would be miffed to learn that a patch for some zero day was fumbled because Facebook didn't get the decades-old memo not to use UA sniffing for feature detection.