So let me get this straight, you want other people to work on a project that you yourself think is a hassle to maintain for free while also expecting the same level of professionalism of a 9to5 job?
Honestly, a colour picker is the last piece of software you should be translating names for. Even everyday colour names don’t have a direct translation. The line between “blue” and “green” is very slightly different than the line between “bleu” and “vert”, and the same goes for any other two languages. If you’re serious about your colour picker accuracy and you want to localize to another language, it would actually be more correct to have a completely different set of colour values, rather than trying to translate them. (Though “Liquid Nyquil” may be perceived the same across languages. I haven’t seen any studies on that one)
I don’t know about this specific program, but pretty much every other time I’ve seen something like this it’s been treated as another language and is a way for developers to test that that feature actually works.
iirc sudo has a bunch of quotes to spit out when an incorrect password is typed. Gentoo exposes that feature with the offensive USE flag.
Argh, why tho?
Like, I get that it is sometimes fun to throw some humor and things like that, but it is just too much trouble. It looks unprofessional and makes translation more of a pain than it needs to be. And that isn’t even opening the can of worms that insults actually are
Often times, projects like this aren’t necessarily going for “professional” - its something the developer has made for themselves and is just being nice to share it and the source to the world.
Also, sometimes that sort of thing is directly related to making sure translations do actually work. While I doubt that was the case here, I remember seeing RedHat Linux for a while had a specific language option that changed the phrasing quite a bit (I believe it was in relation to how one of the devs on the team commonly spoke) and it was done to make sure that translations were working.
IIRC It was added because too many people had been hacking together such a feature in their configurations, more often than not compromising their security. They added the option to reduce the amount of damage such a stupid much-asked-for feature deals.
P.S.: Honestly, I have used the feature before. While it’s usually funny, it can be brutal from time to time.
Is it wireless? If so, and the controller supports it, try using it in wired mode. Sounds pointless, but have had issues with wireless controllers that worked fine when connected via USB.
Bringing back memories of my own. Mandrake in 2004 was a but before my time, but I’m sure I’ve still got my Ubuntu discs I downloaded at the local library and burned myself almost a decade after this Mandrake disk.
Sadly, this is going to be preaching to the choir. Wayland has its faults but if it truly was an inferior approach compared to X then someone would’ve forked X or spawned a totally new project. Turns out it takes time, money, and developer power that simply isn’t coming into X or any competing standard. Wayland is “good enough” to be the next standard and that’s how it’ll be for the foreseeable future.
If a BSD fan really thinks X is pivotal to BSD’s future, then maybe BSD will need to consider forking it and fixing it, but I’m sure the real solution will just be supporting Wayland on BSD too.
For most of its 15 year history implementations have been woefully and obviously insufficient. Nobody forked X because nobody needed to. Its feature complete and has been for a long time and there was nothing wrong with using X while Wayland implementations see progressive improvement.
Not only is nobody forking X but many people are building Wayland compositors.
Listening to the detractors, you get the impression that Wayland is a failure and / or that X may still be the better choice.
Then you realize the only people still working on X are paid by enterprise distros with long-term support obligations. All the toolkit people have moved to Wayland. The major desktop environments have shifted to Wayland. All the “new” window managers are for Wayland.
Wayland is already supported on BSD ( FreeBSD at least ).
The actual developers have spoken and Wayland has won.
i’ve been using sonobus lately and it’s been pretty good, I had latency issues when I tested the android app a long time ago, ill have to test it again
Arch wiki is the reason I started using Arch. After fixing an install from something I found there for like the 10th time I thought “Why not give it a try”
A crash in the window manager takes down all running applications: Yes, because the compositor IS the server, window manager AND compositor at the same time.
FreeBSD’s Wayland support is through a Linux compatibility library. The major Wayland implementations are Linux only and there’s no way around it other than implementing Linux libraries like FreeBSD did.
That something entirely different than the protocol being biased towards Linux. It's like complaining that TCP/IP is biased towards Linux because the Linux kernel's networking module can't be used in BSD kernels.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.