jchw

67 ms·

751.
by jchw 1y ago
No. This is an actual real issue. For example, if I'm using KDE on a TV, which by the way I am (with Bazzite to be exact, works great) then I want to set the scale factor in KDE higher because I'm going to be standing further away
752.
by jchw 1y ago
The issue is that if you want DPI virtualization, and all of the desktops do want that, you need to be able to translate all of the coordinate spaces everywhere. If you try to integrate this into X11, you run into a myriad of different prob
753.
by jchw 1y ago
While that is a solution for this specific issue, it doesn't solve everything. It's better to both have proper layout and proper proportional fonts at the same time.
754.
by jchw 1y ago
Using vector pipelines isn't new, of course: Windows has been doing DPI-independent rendering since almost the beginning with GDI. The actual issue with GDI's scaling is all about text: for something to be "scalable" it
755.
by jchw 1y ago
> It's silly that people keep complaining about this. It's a very minor effect, and one that can be solved in principle only by moving to pure vector rendering for everything. If you have DPI virtualization, a very sufficient s
756.
by jchw 1y ago
Sigh. And now that it's been long enough, everyone will conveniently forget all of the reasons why this wound up being insufficient, and think that all of the desktop environment and toolkit developers are simply stupid. (Importantly,
757.
by jchw 1y ago
That doesn't sound any different than it is for any other programming language, but many people prefer automatic formatting anyways.
758.
by jchw 1y ago
Just to be completely clear I'm not suggesting the BeOS APIs are insufficient to implement robust screen reader support, just that Windows XP actually did implement it, from the ground up, and integrated it into Win32. I would love i
759.
by jchw 1y ago
Okay. But in practice you do still need basic keyboard control and screen reader support. If Windows XP didn't have robust support for that I suspect it would be a very different story, but it did. Edit: Of all the comments to disagree
760.
by jchw 1y ago
Now this looks interesting. I am not familiar with the BeOS APIs, but the UI design is very pleasing. One thing I don't see mentioned anywhere including the plans is accessibility though. Not having basic accessibility support would be
761.
by jchw 1y ago
Including GCP and AWS, even: you need to open support requests to gain access to the larger instance types (and to raise the quotas.)
762.
by jchw 1y ago
Well really, what people actually want, by my estimation, is a machine that works and to not have to adjust their workflows. These are both very sensible things that everyone understands. The stuff about "UNIX philosophy" and co
763.
by jchw 1y ago
When I said that, I meant applications and UI toolkits are not dropping X11 support. Non-LTS OSes will definitely be dropping X11 support pretty soon, since yes, KDE and GNOME are both throwing in the towel. To me the timeline seems about r
764.
by jchw 1y ago
> This is the core issue, it seems. The Wayland transition is kinda like if Volkswagen said "we're now going to stop making cars, and focus entirely on making the best gearbox possible". Well what are people that just want
765.
by jchw 1y ago
Interesting specs. Looks like it's based on the RK3588S. In terms of CPU grunt that's a fairly good upgrade over the RK3399S used in the Pinephone Pro, ~3x more performance in single core according to Passmark[1]. For the GPU in t
766.
by jchw 1y ago
> Everything from your list except HDR worked in X11 years before it started to work in Wayland compositors. Maybe not perfect, but better than any Wayland compositor could do the same until only a year or two ago. - X11 has no DPI virtu
767.
by jchw 1y ago
> I love having to detect at runtime the compositor I'm using (and its version) and have bespoke code paths to work around their various bugs and omissions. > Definitely a recipe for reliable, usable, maintainable software. Hones
768.
by jchw 1y ago
The quick answer is that Wayland, while it has certain design provisions for privacy and security, doesn't really enforce anything on its own, it's just a set of protocols that applications can use to talk to a display server. The
769.
by jchw 1y ago
That seems like a solved problem though. LTS distros will drop X11 when the Wayland session is viable for most people, which is very nearly true, but ultimately not. When it does happen, it really shouldn't come as a sudden surprise.
770.
by jchw 1y ago
> They changed it so that everyone who previously just wrote a window manager now had to write an entire display server. Not entirely true. Now if you want to share the "display server" bits you can plug in a library like wlr
771.
by jchw 1y ago
The obvious right choice if you're on an LTS OS where Wayland isn't in a good enough shape is to continue using X11 sessions. Very few things are dropping support for X11 right now, and on an LTS OS you presumably would be insulat
772.
by jchw 1y ago
Some of them are not really "open" issues, which is blatantly obvious if you try to drag a tab in Chrome in KDE or GNOME: The dockable widget use case is covered by xdg-toplevel-drag[1], has been implemented by multiple libraries
773.
by jchw 1y ago
Many of these limitations are in fact not Wayland issues and just limitations in KiCad (and probably more generally, wxWidgets) under native Wayland. For example, you can definitely do draggable widgets that dock and undock using xdg-topl
774.
by jchw 1y ago
They've been able to execute well for Ryzen, EPYC, and Radeon in the data center. I don't really think there's any reason to believe they can't or even wouldn't be able to do ROCm on client cards, but up until recen
775.
by jchw 1y ago
I still find their delay with properly investing in ROCm on client to be rather shocking, but in fairness they did finally announce that they would be supporting client cards on day 1[1]. Of course, AMD has to keep the promise for it to mat
776.
by jchw 1y ago
I see this sort of argument a lot, but I think it's too oversimplified, there's definitely a category difference between the kinds of automation we were doing before the recent generative AI boom and that we are now doing with gen
777.
by jchw 1y ago
Actually it can be trivial as long as you can require the user to re-type the current password when entering a new password; check hash first, then check edit distance with the entered "current password" (and, of course, promptl
778.
by jchw 1y ago
Possibly a sort of CYA gesture, kinda like how original Stable Diffusion had a content filter IIRC. Could also just be to prevent people from accidentally getting peanut butter in the toothpaste WRT training data, too.
779.
by jchw 1y ago
> My problem is solely with the Nix community. The amount of jargon-loving and argumentative "you shouldn't attempt what you are attempting in the first place" or "you are holding it wrong" gaslighting is really
780.
by jchw 1y ago
Yeah. I've done this a few times with plain old hydrogen peroxide. However, I also really do wonder if the hydrogen peroxide is even needed... it seems to help, but it's unclear. It's frustrating how unscientific retrobrighti

More ›