That's absurd. There are regulations on standby power.
https://dl.dell.com/manuals/all-products/esuprt_electronics_...
>Power Consumption
>0.2 W (Off Mode)
>0.3 W (Standby Mode)
Doesn't seem to be an isolated case:
https://www.dell.com/community/en/conversations/monitors/up3...
>UP3216Q, drawing 23 watts in Standby? (2019).
I guess a takeaway from OP is to measure your actual standby power draw.
http://monitorinsider.com/displayport/dp_pin20_controversy.h...
https://www.dell.com/support/kbdoc/en-us/000132935/the-20th-...
Interesting to know, but I just use a hot key to attempt reconfiguration if something goes wrong. Works for me even if it’s not a sign Linux is ready for non-technical users.
Using hot keys is nice, but hot keys (intentionally) don’t work while my screen is locked. I contemplated mapping an xrandr call onto a smart button (Shelly Button 1, essentially triggering an HTTP request), but in the end grobi has the same effect and is even more convenient than having to press buttons.
No, just normal Microsoft prioritizing features over fixing bugs. I have a "shit_win_bugs" bookmarks folder which is growing in size every 1-2 months.
That was the point GP was trying to make (a bit snarkily and sarcastically) in response to the argument that Linux is not suitable for nontechnical users.
I think that this is the bulk of the argument here.
I think it can, because even if there is an issue on Windows, it's likely still going to be much easier to resolve than on Linux, e.g. no editing files, no command prompt, etc.
yes, bribery and lobby. Remember where Gates went to Munich to "convince" the city council that Microsoft Windows is better than Limux ?
Linux is out of the running entirely except for people that need nothing more than a browser and media player.
MacOS has a kooky paradigm that people get used to, but isn't as intuitive as the classic launcher menu and task bar approach.
Windows had a ton of issues, and not particularly user friendly error messages for a while, but since XP it's been the leader in usability.
Of course with 11 they are really doing all they can to throw all that away...
See kanshi, which has a similar rule matching approach.
But one day a young engineer asked if I could hear my circuit when the load changed.
I could not. I have become what I hated. The cycle continues.
sigh
And that's for X11, which was built in a 70s model while Wayland leisurely moves forward
Then it should show up as single display.
It's also how Apple XDR display presents itself to MacOS (two DisplayPort 1.4 tunnels over USB4, tiled layout in DisplayID).
I suspect it's possible that it doesn't have a valid tiled geometry block, but that's something that was already handled right when first 4k displays landed, so...
For most situations you do not need to do anything difficult to plug any number of monitors to a Linux computer with a modern, full-featured distro, other than arranging them. Mac does a better job of remembering your setup and adapting to a monitor disappearing, but it's not that much better.
I'm still not sure I understand why the author needed this tool, may be because they have more than one computer plugged into the same monitor?
Debateable. But it sure started with huge step backwards. On X11 all relevant functions are at least standardized within the xrandr protocol. On Wayland you don't even have that. So it really depends on the compositor if it works or not where each is doing its own thing which is just crazy. I prefer the 70s standardization model of "mechanism, not policy".
mostly. With first releases of Win 10, it was more than challenging.
> older ways of doing graphics were killed by it due to technical merit.
The issue here is that a server/client architecture complicates things a lot when it's all the same machine and the security model is different