Xorg metaport extremely bloated with linux crap

[covacat]

If you make a while(1) { } tight-loop in a web browser, you will see it crashes the page / browser tab. This is because execution is not returning back to the browser event pump (i.e its main loop). Javascript in browsers is ironically not multi-threaded.

thats true for windows apps too. (main thread) (they won't crash but the system will mark them 'Not responding')

 

[kpedersen]

thats true for windows apps too. (main thread) (they won't crash but the system will mark them 'Not responding')

Indeed, without spawning a long lived thread, its the same with Android too (needs to return to the Java runtime). Not sure about NativeActivity. I believe you get to control the loop.

On Windows I belive you can post to the main message pump yourself inside your own loop to prevent the app from going unresponsive.

 

[mer]

Instead they will select(), poll() for a waiting event to process.

I learned a long time ago, this "design pattern" is one of the strongest for async events in userspace. It can take a little bit to fully understand how and when you need to do things in the data structures, but once it clicks, it's easy. If things are multithreaded one has to pay attention to where data lives, but one should pay attention to details.

 

[covacat]

just update the pointer to a hourglass and do your stuff. letting the user clicking random shit when the program is busy is worse
or display a progress bar that works like this

https://twitter.com/x/status/1224958334991654912

View: https://x.com/i/status/1224958334991654912

 

[astyle]

KDE has a few animations that can be displayed in lieu of a loading bar, and Apple / Google have that stuff, too. Just googling at random, I found some funny ones:

🐌🐌 UI Progress Bars to make you enjoy the wait 😅

UI Inspiration

blog.prototypr.io

 

[michal244]

The x11/xorg port is EXTREMELY bloated. It offers to install so much Linux-crap like Wayland and glibc. I can't belive the default port for X11 offers to install shitty GNU/Linsux bloat. This gives people an awful first impression of BSD in my opinion. I just installed xorg-server, xterm, xdm, twm, and xclock instead. Even xorg-minimal still installs GNU software. I think the handbook should provide that as an example of a really minimal Xorg installation, just so people can see what a fresh Xorg install should be.

I can't wait when bsdsucks supports Wayland and other Linux tech natively. Fanboys like you give awful impressions of bsd users.

 

[Crivens]

I can't wait when bsdsucks supports Wayland and other Linux tech natively. Fanboys like you give awful impressions of bsd users.

Someone may need asbestos underwear.

The whole point of Linux is to have a niche to do the own thing. Same goes for FreeBSD.

 

[sidetone]

I can't wait when bsdsucks...

That says a lot.

when bsdsucks supports Wayland and other Linux tech natively.

I hope they do.

The way Xorg is isn't optimal. Not everyone understands that. Some have a different opinion. Source code upstream repositories which the majority is under permissive licenses shouldn't have bits like glibc, bc it contradicts and overtakes the rest of the licenses which are permissive, which requires manually extracting these more restrictive and overbearing parts out. One is free to use glibc outside of the repository, as intended. Also, users use either Wayland or X, so only one should be installed, when one is chosen. Having parts of both, which aren't needed, is adding unnecessary weight to an already large install.

Hopefully, people understand how NetBSD's X implementation which uses BSD make is superior in a few ways to traditional Xorg.

I need to stop there.

 

[scottro]

Not sure what they're waiting for, Wayland and X are already pretty well supported--and from what I see on the forums, not doing horribly with Xlibre either, for those who want it.