What are you calling “the linux community”?

Linux is the primary OS supported on all of the major cloud platforms and has effectively replaced nearly all commercial Unix systems in new deployments.

We’re well past “small”.

I downvoted not because of any AI concern but because it’s clearly a crappy personal project. Nobody should use this.

Fine, pivot to complaining about the pace of development instead.

My dude that was my point - you misunderstood it for complaining about the one exact example I gave. An example you seem to think is just unsolvable by the Wayland team despite having been addressed by “everyone else”. That example isn’t even so important. It’s a minor but expected feature that seemingly breaks the brilliant architecture of Wayland.

I’m sure everyone who has been successfully using Wayland for years is going to see your vague hints of what’s wrong with it and the Wayland devs will go back to working on X.

Well - I can’t. Pop_OS KDE doesn’t work on Nvidia in Wayland mode. Because nobody though to involve Nvidia in the discussions and just assumed they would change everything for 0.01% of their users. Well done Wayland team. 🤷

You either make global window position the sole responsibility of the compositor or you expose control to applications and get an unmanageable mess, which you can’t fix.

rofl

That’s hilariously stupid. Like every window management system other than Wayland is just an unmanageable mess because they allow this?

Do you have an issue that actually requires this or do you just have an issue with how a certain compositor handles window placement?

You’re arguing a particular problem and solutions to it rather than acknowledging the category of problem and the greater issue it shows. That it’s taken 20 years for the team to maybe kinda consider implementing basic functionality that is provided by every windowing system not named Wayland is f’ing ridiculous. And it’s not the only feature that has taken ages without being addressed. It’s a project team problem. Their ivory tower design didn’t address the real world usage and they lack the flexibility to deviate from their design.

You mean the way X handled window positioning

I mean the way literally every other display handles it other than Wayland which “knows better than I do” apparently. “You don’t want that - I know you don’t” is so pandering.

Windows allows it. MacOS allows it. Wayland is pure and perfect.

if you can’t actually name anything then I’ll just assume you’re being contrarian.

I did - in my very first post. I won’t repeat it here because I don’t care. There are lots. But hey - you got your individual monitor scaling so… I guess fuck everything else yeah?

Flip a friggin coin.

Maybe I misunderstood - The “NixOS (bare metal)” seemed to imply to me that the containers were not bare-metal by omission. If not then my complaint is retracted.

I’ll die on this hill.

Containers run on “bare metal” in the same way that other processes on your system run.

All in all the hate towards wayland just does more harm than good and people limited on complaining and hating maybe should consider ways of actually improving it.

This is bullshit. I have no duty to be loyal to any project. Wayland in particular has been so mismanaged it’s still fighting for dominance after decades and still can’t reproduce the functionality we had in the '90s. All that effort could have been put into refactoring and updating X11 instead.

Maybe what you call “basic functionality” isn’t as “basic” to implement in code.

Everyone else has literally done it. Even X11.

Wayland because it works for a majority (but not all) and still doesn’t have some basic functionality despite having been in development for near 20 years (eg custom window placement).

It may eventually be good, but it is taking a goddamn lifetime to do it. Completely mismanaged imo.

You’d like to think so…

https://app.opencve.io/cve/?product=coreutils&vendor=gnu

Latest cve is a heap overflow.

It’s pointless and stupid is what it is.

It’s the way that word has been used for over 20 years.

I’ve been wrestling with this issue myself recently.

There can be both performance and other issues with a db whose data files are on nfs. That said I’ve done this for years without any real problem. No db corruption so far - but it’s a possibility and I’ve probably been lucky. I have good backups just in case.

Like you I also don’t want to maintain a “pet” database on my file server. I want to spin up databases in kubernetes pods and not use local pod storage.

I’ve been investigating using iSCSI instead. It’s “block level” rather than “file level” and performs better with a database. Also none of the locking issues mentioned. It’s a recommended way to do remote storage for a db.

The downside is that it’s less resilient to the file server becoming unavailable.

Might be worth investigating for you as well - I’ll be performing some poc tests to figure out how much of a pain it may be (I don’t want to need to fsck a bunch of targets after a file server reboot).

My biggest customizations are all of the software I install and use to do things with the computer.

Wait… So if Linux doesn’t have the api (sorry, the “signal” 🙄) how will sites that require it respond? What does it mean to be “exempt” - every user is considered to be an adult?

An alternative to complete cloning (which gets out of date fast) would be to manage systems with ansible.(or puppet, or chef).

You can script configurations, package installs, users, etc. And it also allows for hardware/architecture specifics when needed (e.g. drivers for the different platforms).

You would then just install a base os and run your playbook. No need to store gigs of data and easier to update the base os to newer versions. You could even mix

You can also push out changes without needing to snapshot a new image and re-install it everywhere.

does it still work for software development?

… Why wouldn’t it? Like you could do other things but not write code?