unique_hemp

@unique_hemp@discuss.tchncs.de

This profile is from a federated server and may be incomplete. View on remote instance

unique_hemp ,

Native games need to add client side decorations to be usable on Wayland Gnome. Currently most games just run in XWayland.

unique_hemp ,

I've seen enough blurry software on Windows to know this is not quite true 😅

unique_hemp ,

The way I see it, GTK is really a framework for building cross-platform GUI apps. Then handling display server compatibility makes perfect sense to me.

If this was meant to be a dig at Wayland, I'm pretty sure GTK also needs explicit and direct support for X11, Windows and MacOS. It just already exists.

unique_hemp ,

I'm pretty sure Louis is just another recipient of FUTO's funding, not "the" other partner to this dude.

unique_hemp ,

The flipside of this is that you as the BDFL are not in any way entitled to community contributions. If they decide to not like your furry board, they are free to fork the project, but splitting the development efforts could very well kill both projects, so sometimes it is better for the project to listen to the community.

Explicit sync Wayland protocol has finally been merged! ( gitlab.freedesktop.org )

Since nvidia drivers do not properly implement implicit sync, this protocol not existing is the root cause of flickering with nvidia graphics on Wayland. This MR being merged means that Wayland might finally be usable with nvidia graphics with the next driver release....

unique_hemp OP ,

Well, this is the root cause of this specific issue if you treat nvidia's part of the stack as some barely changable black box (which is what it is right now). It's not that I disagree open source drivers would be better, I just already own an nvidia GPU :/

unique_hemp OP ,

Nouveau should have already been fine, this should fix the proprietary driver's issues. AFAIK this is a core issue of the proprietary driver, so should affect all cards.

I tried Wayland on my 16xx series GPU, Electron apps were only annoying, but games were unplayable. The desktop itself and Wayland native apps worked fine, though.

unique_hemp OP ,

Yes, for that to change we have to wait for the NVK based driver - nova.

unique_hemp OP ,

Yes, but that's bound to be merged quickly, the protocol itself was the main holdup from what I understand.

unique_hemp OP ,

Plasma 6 X11, 550 proprietary driver.

unique_hemp OP ,

Desktop 1660S

unique_hemp OP ,

Maybe if your games are Wayland native or you're still running the 535 driver? I saw fbdev=1 as a workaround, but that made things very jello-y.

unique_hemp OP ,

I saw a comment from an nvidia dev somewhere that XWayland support is enough to resolve the flickering, but compositor support is needed for best performance.

unique_hemp ,

Yeah, still gonna be a couple of months, but that is the last signifficant issue for me, fingers crossed.

unique_hemp ,

Except the hard part was already done - the directions are calculated on the server anyway, so only the UI needed to be coded up.

unique_hemp ,

Your last sentence is the only valid complication, all the other issues exist just the same on phones and Google has already solved them in their existing apps.

unique_hemp ,

SELinux is a pain on Arch, it actually working nicely could be viewed as Fedora's killer feature.

https://wiki.archlinux.org/title/SELinux

unique_hemp ,

No, because this is common terminology that has no reason to be messed with, even if it is technically unclear.

unique_hemp ,

Music streaming is also much cheaper to run than video, so they can offer more reasonable pricing.

AMD GPUs are cursed for me

Each time I try AMD graphics, something is fucked for me. Back with fglrx, fglrx just sucked, so I used Nvidia. Then I had an AMD right around when they finally had opensource drivers, but it was still buggy as hell. So I went with Nvidia again (first a GTX 790, then a GTX 1060). In the meantime I had a new work notebook where I...

unique_hemp ,

Yeah, until this thread I was convinced I should stay away from nvidia GPUs when building a new PC with Linux in mind, but I'm not so sure anymore.

The 6.7 kernel has been released ( lwn.net )

Some of the headline features in this release are: the removal of support for the Itanium architecture, the first part of the futex2 API, futex support in io_uring, the BPF exceptions mechanism, the bcachefs filesystem, the TCP authentication option, the kernel samepage merging smart scan mode, and networking support for the...

unique_hemp ,

I have run nextcloud:latest on Docker for the last 2 years and have had 0 problems. Maybe upgrading all the time works better than by releases.

unique_hemp ,

Not quite - you get a perpetual license for the version that was released a year before you cancelled your subscription. And for most languages this is not really practical anyway, as they get relatively frequent updates that require IDE updates, so you will just stay subscribed.

This was a fairly low business risk, high PR value move by JetBrains.

unique_hemp ,

It was built on yearly releases of software instead, also known as yearly subscriptions.

unique_hemp ,

Except using software without updates nowadays is a very bad idea because of the Internet and security being a real concern.

unique_hemp ,

Just a bigger update, should be fine. AFAIK they did not do any major overhaul from a regular user’s perspective, but there are some pretty big changes under the hood. If you use a distro with regular releases, this will probably be included in the next one.

unique_hemp ,

Right, but that’s nothing compared to Gnome 2->3 or KDE 3->4.

unique_hemp ,

The decision to adopt Chromium style versions was an interesting one for sure…

unique_hemp ,

Depends on the ecosystem around the language - there are tools that just plain don’t work or work poorly on Windows.

Alternatively you could try developing a .NET Framework v4 app on Linux, if the OS doesn’t matter (no, mono is not equivalent).

unique_hemp ,

Sure, but it’s nicer that I would stop using my phone because it’s not worth repairing anymore rather than because it’s not supported.

Why is Debian the way it is? ( blog.liw.fi )

Debian is a large, complex operating system, and a huge open source project. It’s thirty years old now. To many people, some of its aspects are weird. Most such things have a good reason, but it can be hard to find out what it is. This is an attempt to answer some such questions, without being a detailed history of the...

unique_hemp ,

Those are the same type of people that moved from twitter to bluesky.

unique_hemp ,

I mean, you probably already have electron compiled, no?

unique_hemp ,

Nope, the article says that what is and is not a grapheme cluster changes between unicode versions each year :)

unique_hemp ,

Import from OpenAPI, yes. Super useful if you use Swagger and it starts lagging :)

unique_hemp ,

Webpack takes 10 minutes to build the release bundle in a project at work…

How important is the option for dynamic linking (vs static linking) in the modern day?

There was a time where this debate was bigger. It seems the world has shifted towards architectures and tooling that does not allow dynamic linking or makes it harder. This compromise makes it easier for the maintainers of the tools / languages, but does take away choice from the user / developer. But maybe that’s not...

unique_hemp ,

Except with dynamic linking there is essentially an infinite amount of integration testing to do. Libraries change behaviour even when they shouldn’t and cause bugs all the time, so testing everything packaged together once is overall much less work.

unique_hemp ,

More control? If you’re speaking from the app developer’s perspective, dynamic linking very much gives you less control of what is actually executed in the end.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • All magazines