Vik

thank you for sharing. love metrolist and the idea of having a desktop equivalent.

There’s also pear desktop but it’s sort of a web wrapper for the stock yt music experience, and likely has a comparable memory footprint to your situation having it as a pinned browser tab.

you should be able to create bootable flash drives with dd

Wayland is more secure than x11 by design and more concise in scope. Notably it supports contemporary display technologies like display independent scaling, VRR, colour space (HDR) and several others.

Wayland is made by the x11 people.

yes, absolutely, though I’ve seen it much more amongst other end users.

As I’ve mentioned, games will load your system differently from one another. Someone who claims their system is stable with their custom tunings in every game except for something new that they’ve recently installed does not have a stable system. this is a case my colleagues and I see over and over.

Extensively, across various compute and graphics generations. I presently do so even now, though I wouldn’t offer that to a user completely unfamiliar with the domain as some kind of silver bullet; it doesn’t sidestep package power limits.

I work in client gfx at an IHV; I am intimately familiar with system integrity routines, component stress testing and tuning, particularly with DIY systems. Nothing about what I’ve recommended is “a waste of time and electricity” when you’re privy to the breath of defects averted in the field after following proper guidance.

Don’t take your own experiences for granted, if this person was familiar with the concept, they wouldn’t need to ask.

that’s not how stress testing works. Different games will present different load to a given combination of hardware. Besides that, computers are used for many more tasks in addition to gaming. Careless re-tuning can lead to a lapse in system integrity in ways that aren’t immediately apparent, but damaging all the same.

undervolting is all well and good but warrants component stress testing versus regular PL targets.

may help to know your device models, but power limiting is generally what you’re after. Your hardware may determine the methods used.

I read a long time ago that Mozilla weren’t happy with the original proposals for webusb and webhid. I’m not sure if it was revisited since then.

sort of a shame because I have to keep something like ungoogled chromium installed to interact with certain peripherals using the Via web app and similar, or even the GrapheneOS installer.

Would love for them to revisit the spec and address the concerns they had with it for their own implementation.

Seems there are various ways to hack it in, at least https://github.com/ArcaneNibble/awawausb

I think that could work well. looking forward to more diversity in compute in the future! 😊

That’s fine, it’s an emerging ISA, as with any, it takes some time before perf and sw compatibility reach a good spot.

I think the key novelty to rv especially compared to x86_64 and arm is that there are no licencing restrictions: anyone is free to design and produce products based on that ISA, making more viable for vendors to more easily provide in-house silicon solutions. It’s already become fairly popular in lower power devices, like for IoT and wearables. My smart soldering iron uses a little 32 bit RISC V CPU and I wouldn’t be surprised if it’s found some use in automotive, particularly in China.

As we alluded to above, there are several designs available for more general use, and you may find that they handle your compute needs fairly well already, but they won’t be within striking distance of other ISAs if high performance is a requirement.

compat wise I think many packages are now available for rv specifically or as .noarch.

perf wise, I think we’re still a ways off, we’re not seeing rv SoCs at the same level of perf / efficiency as arm, and whilst that’s just a matter of time, I’m not sure you’ll have many compelling offerings even a couple years from now, though potentially in 2030?

you can check in with experiences using devices like the PineTab V or even the custom RV mainboard for the Framework 13. There are also several SoCs produced by SiFive on SBCs, some are card sized, some are mATX. These are primarily positioned as development devices, but they may give you some idea of what things are like right now

You’ve had me realise how long I’ve actually been using Linux for, though not quite at the ten year mark unless you count some very early endeavours with ubuntu.

fully agree with you on Debian as a rock solid server. my “don’t fuck with it, just work” client system for several years now has been fedora workstation, though I’ve only relatively recently switched all of my personal computing over to it (still have several windows installations for work-related testing).

Init managers for sure! Amongst file managers and DEs, firewalls, package managers, modern packaging systems and their sandbox/security systems, display servers (probably the funniest one), audio servers, filesystems.

Lots of stuff we should appreciate having as FOSS, especially the options we don’t choose.

Fully switching over for the last couple years has made this modularity feel especially apparent compared to commercial systems (when things aren’t always so seamlessly integrated) but I’m glad for it all; it’s really fucking cool to think about how dramatically you can change the experience of a Linux desktop OS.

the confounding tribalism behind its modularity. options are great, but they also bring out the absolute worst in many of us.

it’s not much of a problem until those options actually manage to fragment the desktop and server ecosystems, but the attitudes at play surely drive prospective newcomers away a bit.

Isn’t made by former team members of ableton as well?

nop. my overall desktop experience has improved substantially after I carved out my own niche of ‘creature comforts’.

feels lovely to have a system that works for you, rather than something that’s so adversarial.

yes

excellent find! hope it serves you well