_d3Xt3r_
Joined 3 years ago
Joined 3 years ago
1. I no longer watch Netflix, but AFAIA, 1080p/4k is still a no go, as that requires proprietary DRM which isn't present in Linux/Linux browsers (Widevine L1 and PlayReady). But you can still watch Netflix in "SD", if you're okay with that. Not sure about fandom services, but if they don't use DRM it should be fine, for instance, YouTube 4K plays without any issues, and so do other sites like Piped/Invidious etc.
2. Sleep/wakeup works fine on AMD, MacBook style. I also use an M1 MBA, so when I say that the resume speeds are identical, I mean it. The default sleep mode btw is suspend-to-idle, which resumes instantly compared to the old method (S3/suspend-to-RAM).
3. By "sane" did you mean S3? If so, at least on AMD laptops and Linux, you can pass `mem_sleep_default=deep` to the kernel and it'll use S3 mode instead of s2idle. However, a couple of things: at least on my setup, s2idle drains very little battery and doesn't cause your backpack to heat up. But if you're still concerned about battery drain over longer periods of time, you could enable the suspend-then-hibernate option, which will cause your laptop to automatically hibernate after it's been in standby for a while (exact timeout period is configurable). So IMO, there's no need to use S3/deep standby.
But how does that compare exactly, performance wise, against Bitlocker and LUKS? (assuming similar strength encryption algorithms are selected)
Also, trying to convince devs to port games to Linux was never going to work - a more practical approach would've been to use/develop Wine instead. In fact, Valve had released Proton a whole year before Stadia went live, so if Google wanted to, they could've worked with Valve and combined their efforts to make Linux gaming better. Even if they chose not to approach Valve directly, they could've still used Wine and still benefited from Valve's upstream contributions (and vice versa). But instead they made the insane decision to try and convince devlopers to port their games to a niche platform Google which could kill off at any time... It's like they deliberately set the whole thing up to fail, then came up with excuses as to why it didn't work. Like Project Ara.
Like you, I dislike much of the modern web frameworks and all the bloat and unnecessary complexities that come with it. I roughly tuned out of this stuff when JQuery became mainstream and everyone and everything started using it, and I couldn't be bothered to keep up any more, nor did I feel inclined to invest my time in such a bloated framework. I did come back to webdev every now and then for casual projects, but every time I did, the world moved from one fad framework to the other, which made me dislike this messy ecosystem even more.
In particular, one environment/toolset that I really disliked was Node.js. Every time I did anything with Node, it always turned into pulling down a gazillion dependencies, and eventually down the line, that led to stuff breaking because some random dependency of a dependency was no longer compatible a with newer version of node or something. It basically put me off modern webdev for good, to the extent that I web back to using plain ol' php for the backend, and since then I've been exploring using pure HTML5+CSS3 without any Javascript for the frontend, but I've been seeing limitations like not being able to do stuff like real-time form validation etc.
Which brings me to your example:
# install dependencies
npm install
May I enquire why you're using npm here? Exactly what dependences are you pulling down? I thought the whole point of Nue was to avoid bloat like Node.js and dependency hell? Isn't Nue supposed to be a self-contained library/ecosystem?Can I use Nue without touching any Node stuff at all?
Two cool things that TLP does is allow you to set battery charge thresholds for better battery longevity (I limit mine to 80%), the other being automatically changing the energy performance preference (EPP) in the amd-pstate driver, so if you're on battery you could get it to automatically switch to power saving or balanced powersaving etc. I get an 8-10 hr battery life even with the 80% cap capacity, with several MS webapps running in Edge (Wayland), including Teams and Outlook, VS codium and Firefox running in the background.