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.
grow a plant, hug your dog, lift heavy, eat healthy, be a nerd, play a game and help each other out
- 3 Posts
- 426 Comments
Joined 3 years ago
Cake day: June 12th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
5·7 days agoKind of similar to https://send.vis.ee/ which was forked from Firefox Send, though the public instance is limited to 2.5 GiB transfers.
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.
Hey, no problem.
Yes - the depicted side buttons channel into just one of the rear-side pinouts, and even then I think each side can support many more than just two inputs. I believe there are a few examples on the site and repository, but those resources still need to be built out some more.
I’d recommend reaching out to the designer directly. He’s pretty active in his discord server, though if you’d prefer not to use discord I’d be happy to ask on your behalf if you have a concise idea of what you’d like to do.
This looks really nice. Thanks for sharing
That’s not weird at all 😊 and yeah it only started shipping a couple months ago.
You should be able to achieve any number of input combinations with the breakout boards. The designer sent me loads of extras and I should really put them to use 😅
Hell, I’m planning on using the same base board to make a wireless macro pad later on. Unfortunately the community is on discord but you can hop in and see what other people have been making.
Check out the moddo mouse if you want a wireless, modular, open source gaming mouse, so long as you’re either comfortable with ultra lightweight fingertip style shells or 3D printing your own
I also have a ploopy mouse but I really dislike the scroll wheel design. I need to fix that somehow
19·2 months agoit’s great to see Alexander right in the phoronix comments for that article! 😅
top lad. brave guy
2·3 months agoappreciate you 😊
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
appreciate the info, will pass this on
Harry (from the github thread) hasn’t been able to repro on Ubuntu so far
I’m curious if you’ve been using
--usecase=graphicson install?
it’s not as convenient but there are several client apps using the wormhole protocol. They generally require devices to be on the same network but you can tether outside of that scenario.
I’m quite fond of LocalSend.