michaelrose

joined 1 year ago
[–] [email protected] 28 points 10 months ago

If you don't know install a distro and use what comes with it by default and only worry about digging into the plumbing if something doesn't work for you.

Ideally you let your distro worry about plumbing.

I think Mint is nice if you don't need bleeding edge stuff. You can use Cinnamon which runs x11 but will eventually support Wayland.

I've heard good things about suse which has a rolling release option and supports gnome and KDE under Wayland.

Arch of course is a thing if you don't mind a manual transmission as it were.

Personally I might pick Mint to get started.

[–] [email protected] 4 points 10 months ago (2 children)

A few reasons. It's received wisdom that AMD are the good guys because in the Intel / AMD slog they are the underdogs fighting the good fight and bringing good affordable products to all vs intel who has historically behaved in a sleazy underhanded and anti-competitive fashion and when they bought ATi they moved ATi from a maker of shitty proprietary poorly supported pieces of shit to an open source friendly maker of acceptable GPUS.

Since Nvidia is the bad guy in that fight it would be handy if Nvidia was also badly supported buggy, inferior. The fact that Nvidia is actually more stable, well supported, and generally better is somewhat a fly in the ointment.

It's especially humorous when its coming from users of a permanent beta distro like arch where the kernel update process is that the new kernel is pushed extremely quickly after release. Expert arch users realize that means they are their own QA as far as out of tree modules. Actually stable distros express what is known to work as dependencies such that you trivially get something that is known to work when you press go. They also don't run the kernel release that was cut this morning.

Meanwhile users of arch derived distros, who may or may not claim to be running arch while believing their distro is ubuntu with faster updates yell that nvidia is broken when 6.3 doesn't work the day it was cut with nvidia using a driver that doesn't claim to support 6.3. The fact that this dependency is known but not encoded into arch packages isn't an Nvidia problem.

Even Manjaro a distro run by folks who once told their users to set their clocks back because they forgot to renew their SSL Cert figured out they can avoid almost as much trouble as smart people can avoid by actually reading by just being lazy and not pulling changes instantly.

[–] [email protected] 6 points 10 months ago (8 children)

You have a bunch of duplicated stuff because flatpak is a piece of shit. With traditional packaging apps supporting your platform would get exactly one choice. Support the fucking version of nvidia that everyone else gets to or fuck off. In all likelihood all your shit would work work with the most recent release but because they have the option to be lazy fucks and make you download Nvidia 7 times this is your life now. Also if dkms takes appreciable time you either need to stop running Linux on a toaster or delete some of the 17 kernels you are hoarding for some reason. You need like 2 the one that you know works and the new one you just installed.

[–] [email protected] 4 points 10 months ago

Nearly 1 in 5 drivers or about 42 million people in the US can drive a stick. You have confused your peer group with everyone. Used manual cars are cheaper precisely because they are less in demand and cheaper to maintain to boot. Purportedly quality of automatic varies a lot which older cheaper cars being pretty shit. Remember when people are picking a car not everyone is picking from new mid tier new vehicles or last years models.

[–] [email protected] 16 points 10 months ago

In the meantime, please always use Autopilot and FSD Beta as intended, which means with your hands on your steering wheels and your eyes on the road.

This isn't how people work if you aren't driving then your reactions will on average be substantially slower than if you were attending to the task directly and you have no reason to expect the sudden death wish. If you have to babysit it with your hands on the wheel poised to avert death at any moment it is fact much worse than nothing.

[–] [email protected] -1 points 10 months ago (1 children)

It is literally how Wayland is scaling your shit you just don't know how anything works.

[–] [email protected] 1 points 10 months ago

It's painful because the developers took 14 years to produce something semi usable while ignoring incredibly common use cases and features for approximately the first 10 -12 years of development

[–] [email protected] 0 points 10 months ago* (last edited 10 months ago) (3 children)

I just passed scale to xrandr after computing the proper scale and then used the nvidia-settings gui to write current configuration to xorg.conf its not incredibly hard basically all you are doing is scaling lower DPI items up to the same resolution as your highest dpi item and letting it scale down the correct physical size. For instance if you have 27' monitors that are 4K and 1080p you just scale the 1080 ones by 2 if you have a 4k 27 and a 1080 24" its closer to 1.75. The correct ratio can be found with your favorite calculator app.

You can set this scaling directly in nvidia-settings come to think of it where you set viewport in and viewport out.

[–] [email protected] 1 points 10 months ago

This is literally the exact bad attitude of your average Wayland proponent. The thing which has worked for 20 years doesn't work you just hallucinated it along with all the show stopper bugs you encountered when you tried to switch to Wayland.

[–] [email protected] 0 points 10 months ago (7 children)

This already works on X and indeed has worked longer than Wayland has existed.

[–] [email protected] 0 points 10 months ago (7 children)

The biggest Sin by far of Wayland is making users think about the graphics stack. Does this feature or this app support Wayland or X? Does this Compositor support this GPU? Does this particular environment support this mixture of displays with this DPI? Do I need to set a particular env variable or change a setting to force this app to start in Wayland mode because under X11 its scaled funky. What works in each environment? What doesn't work between environments?

Well before you reach the end of this flow chart you have lost virtually all of your users. This transition has single-handedly set the Linux desktop back by 20 years in terms of supporting more users whose level of interest in configuration is limited to clicking a control next to their monitor and making things bigger or smaller.

A saner design would have handled scaling correctly from the start and would have had a permissive mode which just made everything from the users perspective work while progressively adding a correct UI to provide features like global hotkeys, screen sharing, only to those apps users had authorized like android. If it wasn't a such a clusterfuck to use it would have had orders of magnitude more users much earlier in the development phase and perhaps attracted more development interest as well.

[–] [email protected] 2 points 10 months ago

Exactly the situation described. It's possible to fix that process but too many entrenched interests render this impossible

view more: ‹ prev next ›