mittorn

u/mittorn@masturbated.one
3 posts · 139 comments

Recent posts

Recent comments

@toothbrush @Tanoh
>xwayland-satellite
does not implement anything, just glues xwayland to session
phoenix and yserver might be good Xwayland alternative, not Xorg/xf86, because Xorg is mostly about DDX drivers and it's only way to use 2d acceleration on old hardware (which is deprecated, but still might be useful)

@RustyNova @MyNameIsRichard
>On nix os, blender doesn’t want to render anything after waking from sleep (may be a blender issue.)

seems to be cuda issue. On my machine cuda sometimes refusing to work after sleep, requiring some 'node restart'
Might be fixed by disabling modeset (nvidia-drm modeset=0), or by blocking display server from using nvidia drm node (if display output does not use nvidia)

@MonkderVierte @tjhrulz
Hm? Removed pulse, installed pipewire-pulse, run pipewire && wireplumber && pipewire-pulse as user and got no available sound devices.Why? Because wireplumber's bullshit crashed after forking to daemon somewhere in camera support code (but i do not have cameras!).
With reference pipewire-media-session everything worked, but everybody forcing unstable and bloaty wireplumber, making old configuration not supported...
Yes, maybe it's not pipewire fault, just it's modular architecture, but it makes me unhappy with it, so i still using jack. And i sure, there should be separate provider processes for camera and audio devices

on Preference · c/linuxmemes · 1 pts · 221d

@possiblylinux127 @Skullgrid protocol itself is mostly OK. Yes, it have many limitations, but it covers much more desktop needs than wayland/mir/surfaceflinger/etc.
But implementation is really broken.
For example, the way how some extensions override vtable is terrible: overriding functions usually should restore base function in vtable before calling it and and restore back after. Breaking this would break call chain and override function will never be called again.
I think, this is a reason why devs switched to wayland. Nobody want to reimplement x11 from scratch, but exisiting implementation is borked

@hdsrob
>That’s basically Avalonia UI.
no, avalonia cannot help you run existing applications. Also. Avalonia is a crap, taking minutes to parse xml crap on poor hardware
Yes, there are many implementaion of WPF-like UI, but no implementation of existing Windows UI.
mono's winforms allows you run existing winforms apps without single line change or even without recompiling (just replace related System.Windows.* assembies)

@DacoTaco Yes, it's Microsoft decided to kill classic win32 widgets and any XAML support in Mono, forcing new WinRT platform and not providing any GUI support in netcore. It's sad that nobody made some crossplatform WPF implementation for modern dotnet, Maui is not incompatible with existing source code, IIRC