• 0 Posts
  • 25 Comments
Joined 2 years ago
cake
Cake day: January 26th, 2024

help-circle
  • Look, I get it. But I’m also burned out.

    Noone forces you to use krita.

    Krita’s devs specifically? No. I respect devs by default. I don’t doubt many of Krita’s devs love what they develop. I also use Krita. I don’t have it installed because I don’t need it.

    The problem that I keep running into is my (Plasma) defaults being changed for (some) reason. Krita usually gets the defsult for photos. Rhythmbox for audio and MPV for video. I prefer using Pix for photos and VLC for AV.

    Noone forces you to use krita.

    Plasma, kind of - does.

    99% of people do not want a photo editor to be their defsult app for opeing photos. Some artists? Sure. But me? No.

    Again, it’s nor a Krita thing specifically - Plasma fucks with my defaults. It’s a Plasma/KDE thing. Krita is just the unfortunate app to have become Plasma’s senseless-default victm.

    If it doesn’t fit your workflow or if you think developers are deliberately sabotaging your work

    Oh, Krita fits my workflow quite well. Personally am in the process of switxhing to it from GIMP. I know I wrote up a huge wall of mostly garbled text in a passionate rage, but reading just the first part of my rant should’ve made that clear.

    I use krita frequently and never met your bug so it’s not as recreatable as you think.

    Of course you didn’t. Because who in their right mind enters “0” as the target resolution? That’s right - on one! Except for me, apparently. It’s a stupid bug. One which doesn’t mean anything. It opens no attack surface. It doesn’t cause random crashes. It doesn’t interfere with anyone’s work.

    However, you clearly haven’t read my essay. Which is fine with me. It isn’t quality reading material by any sensible metric. But, were you to have read it and tried to recreate the bug, you probably would’ve succeeded.

    With that out of the way, my main point was how no - devs (especially KDE, and very transparently so) don’t value your feedback as much as one might think.

    Which is - understandable.

    As you said, many keep FOSS software alive in their free time for nothing other than the moral gratification. Which is much more than merely commendable. And please, do not try to tell me I don’t respect that when I do.

    Where would devs be if they only replied to stupid questions from new users? That’s right - in a tech support hub!

    Which is obviously a waste of their time. The fact they don’t do that isn’t anything negative.

    The problem, as always is - documentation. My little beef with KDE’s crash wizard is but one example of this deeply-rooted problem.

    As is seen in our (both mine and your) example, reading is hard. Writing - harder still. Were I able to read and fully comprehend the ill-fated link on the KDE wizard’s “fuck you” page, you probably wouldn’t be rading this. But alas, I am a human whose reading comprehension skills aren’t top-notch.

    Another, equally deeply rooted problem in FOSS is lack of general design thinking and logic. Am I calling KDE devs stupid? Of course not! But any UI (including the KDE crash wizard) should have a few eyes to assess it first. Then research on a batch of test users should be done. And then feedback from the general user population should be listened to. Is that a hard ask? Yes. Step 2 is expensive and as such out of reach of most FOSS projects, and not even Big Tech bothers with step 3.

    But am I wrong in calling the KDE modal annoying and badly designed (“stupid”) even, when it has already wasted my time in the same way on 15 occasions? Maybe not. I am angry and it may have been irrational. But I feel my perspective is at least understandable even if the wording isn’t.

    In the end, users can’t live without developers and developing user-facing applications makes little sense without users. I’m not in the Linux community because I don’t like FOSS, Linux or KDE. I’m percisely here to support them. However, sometimes issues arrise, and having a good community to help with fixing issues (because the devs can’t (obviously) handle all that load themselves) is good.

    Having a community where the answer to a simple, begginer question is basically “bother the devs, they have a Matrix”, “it’s probably your fault” isn’t an answer. It’s a fuck you. And once they find out they’ve been mislead (not even intentionally perhaps), they might go back to Big tech.

    Saying to me that I don’t support FOSS, that I don’t like it and that I can go back to Big Tech (when I haven’t been there for over 4 years now), is an even bigger one.

    I like FOSS. Saying I don’t respect them wben I truly do is an insult. I merely don’t understand some of their decisions. Probably due to a lack of context and knowledge, which is on me.

    But does giving a rant about, what are tiny problems in the running of a huge machine known as My Computer, spurred on by someone’s unhelpful advice, given in hopes of starting a discussion and the wholly implausible odds of the issue at hand given as an example being fixed due to it call flr the reply “Go to Big Tech, there’s clearly no room for you here”?

    I’d hope not.


  • Are you sure it’s not a you problem? Or isn’t it a you problem? Go read the docs.

    Have you contacted the devs? Reporting a bug would be helpful.

    Sorry to be so rude, but you really hit a nerve. It isn’t even your fault.

    Anyway, rant time:

    KDE and bug reports. They always come to you like "Hey, bug reports are so really importsnt to us! And we’ll guide you through it. Here’s our lovely oh-so-helpful wizard!

    Except it ain’t lovely. Nor helpful. The only thing it does is pop up whenever a KDE app has an aneurysm and asks you for a backtrace. And then… backtrace is declsred useless.

    Why even bother people with the stupid popup if in 90% of cases it’s declared as useless. Why not do the backtrace silently and then annoy the user only once you declare the bug “useful”.

    Last instance of this: I was using my KDE desktop. For some reason, Plasma seems to really hate me, because I need to fix default apps every few weeks. For some reason, jpegs and pngs open in Krita by default.

    So, wanting to close Krita, becuse I don’t need an entire editor to look at a photo, with tools taking up 25% of the screen, when it asked me about the import resolution, I pressed 0. Krita proceeded to crash and open the report bug dialog.

    Not having seen the KDE report wizard for quite some time, I felt inclined to go fill out the report. Got through the first few pages just fine. Then came the backtrace. Sure, do it. I’d like whoever debugs this not snooping through a data dump containing god knows what, but sure. Then it gets called useless. AFTER you’ve taken 30-ish seconds of my life on preliminary questions.

    Look, if you’re gonna ask people for input and discard said input if something unrelated happens, at least ask after the something unrelated decided it’s not gonna be yeeted away. No need for the “Oh, wait, we don’t really need this, it’ll take too much time to play detective” after the user already passed three screens of interrogation.

    Anyway, the point is:

    KDE clearly doesn’t care about bug reports. Because if they did, the guide on installing backtrace-enabled packages once the inevitable verdict of “useless” wouldn’t be a wiki page with the generaal message of “find backtrace-enabled packages, you buffoon” when you could point to them.

    Another problem with this is: when a bug happens without backtraceable packages, how is the user supposed to recreate it if they don’t know how?

    And besides, my bug is very recreateable. Open an image in Krita (preferably from Dolphin, after Plasma mangled the defaults, again and again). When prompted for some integer, enter “0”. Instead of a generic error message, see the entire app sink into oblivion.

    Anyway, if anyone feels like reporting the totally useless report with totally unrecreateable conditions, feel free. I won’t. Just too much work, for it to be discarded just like that by some wizard no one even thought through.

    And why would I contact the devs? Or rather, where could I do that? They’re worse than government agencies, for god’s sake. The right person or place just doesn’t exist. Wherever you go to or ask, it’s someone else’s responsibility or your fault. And the wizard, that true single point of contact - refuses any contact just as consistently.

    So tell people to call the devs. Tell them it’s their fault. Tell them to make a bug report. Say it just might help not just you, but someone else when all hell will freeze over before anything like that becomes even a remote possibility.

    Talk about adding insult to injury.


  • Paid luches are nice. But if I get the choice between $10.000 yearly more or paid lunches, obviously i’d go for the cash. It’s supposed to be a bonus (i.e. free), and not a way to cut corners and undermine your employees.

    Maybe it does do the company some good in terms of retention, but counting on “I’ll save $6k if I spend $4k on lunches per person on average by cutting pay for new hires” is not a good strategy. Same for ping pong tables, horseraces, pizza parties and whatever else.



  • It’s a Linux subsystem for Windows. As in, you run Windows and within it run Linux. Thus Linux is the sub-system, while Windows is the “overarching” system. Therefore, it’s Linux running as a subsystem on a Windows machine. Therefore, a Linux subsystem on/for Windows.

    <edit>

    That was just setting the two viewpoints equal.

    Now, to add why this one is more “correct”: when talking about Windows (or Linux or anything else fir that matter) subsystems, you don’t call the Windows file system the Windows subsystem for Files or the Windows subsystem for Networking or Linux subsystem for RNG - You call them the filesystem, the networking system or the RNG system. And since none of them get the “for host” suffix, it seems natural to assume it’s the guest system that’s the “sub” system, with the other one being the whole.

    </edit>


  • Fair. Although, I consider Microsoft’s market “Most laptops” since Apple kind of does its own thing and Chromebooks are ultra-low end laptops. Thus Microsoft gets ~95% of the market for themselves.

    Personally, I’d say that’s a clear case of monopoly since MS controls this entire segment of “non-Apple, non-ultra low power laptop, PCs”, but you’re right - there are other players. The thing is, they have relatively tiny niches in which they thrive and in fact pose no threat to the monopolist.

    But I now I see how you see it as an oligopoly, which is quite valid.








  • I"m with you on copyleft, but if I had any connection to the project and felt the need to add a reaction emoji, it’d probably be a “thumbs-down” as well.

    It’s not because I’m against the GPL, but because of the way the GitHub comment is written.

    It doesn’t even say “you should use the GPL”, it says “you MUST say GNU doesn’t agree with you”. I’m perplexed.

    Now, I respect the idea of GNU, but the way GNUers in general go about behaving themselves is perfect to alienate people, and this GitHub issue is a prime example. I don’t get it.

    If people don’t know about GNU, tell them. Nicely.

    If people have misconceptions about GNU, there’s nothing wrong with fixing them. Again, nicely.

    The problem is, whenever I encounter GNU and however much I agree with them on key issues (which is at about 90%, my main gripe with them being Freedom 0), they just have a knack to get me, someone who is with them on most issues, annoyed at them. I can clearly see how someone who isn’t as alligned with them as I am gets equally annoyed and avoids GPL and GNU like the plague just to fuck with 'em (while fucking over everyone, including themselves). Not to mention ones into the libertarian stream, since you yourself covered that pretty well.

    What the GitHub issue you linked that I keep coming back to shows is this GNU herd mentality of fucking over others unintentionally and in turn fucking over everyone. While they’re clearly better than the “libtards”, they still end up doing the same mistake.



  • Linux Mint is the obvious “newbie” choice, and not just because everyone says so.

    Now, I’m no Linux expert, but Mint is great for the huge amount of tutorials availiable. The catch is: most of them aren’t aimed at Mint itself, but Ubuntu or Debian, from which it “inherits” a lot. So, if you have a problem and can’t find a fix for Mint specifically, chances are one aimed at Ubuntu (or even Debian) will work flawlessly.

    Additionally, GenAI chatbots impress me with how helpful thay are. Just by asking them how to do stuff will teach you a lot.

    I highly recommend you save the info which seemed most useful somewhere for future reference. In my experience I had to do a few dozen things repeatedly and ended up remembering them. They’re mostly simple commands like apt install, apt update, apt upgrade, cd and my favourite <app_name &> which opens the app invoked without “hijacking” the terminal.

    As most in the Linux community say, some things are lightning-fast to do in the terminal once you know the proper incantation.

    As others said, the Mint install is incredibly simple, and much faster than the Windows one. You don’t need a guide, just reading the on-screen prompts and instructions will guide you through it. During the install I highly recommend checking the “Install proprietary drivers” box because depending on your exact hardware, some things (especially Nvidia) may not play well without it.

    You will be able to do almost everything without the terminal, although many tutorials do utilize it, so using it is pretty much inevitable at some point of your Linux journey.

    Now, some hearsay: I’ve heard that Windows doesn’t play nice with dual boot (although I’ve never experienced it fist hand), so you should back up your files just in case.

    But, before you do that: For starting, if you’ve got the time, I’d recommend getting an old machine to dip your toes into Linux on it first without fully committing. I’d recommend you do this even though you have the Steam Deck since there are some differences between SteamOS and Mint, so it wouldn’t hurt to try.



  • The thing with the Control panel (speaking as a former Windows user up until a year ago) was its consistency. Since the Aero era things have remained in more-or-less the same place. Sure, some things got added, some renamed and some deleted, but the basics I needed (mouse sensitivity, battery settings on the laptop, the Add/remove software page, search indexing, printers) has all stayed in more or less the same place.

    Then 10 happened. And sure, Settings was great for a lot of stuff. But when Settings didn’t have the option (or I lost my nerves trying to find it), Control Panel was the way to go. I’d find what I needed pretty much instantly, since was always one of the same 20-odd things I need.

    Even then, everything just seemed faster in Control panel. Was it more responsive? Were there less animations? Were more things crammed into one screen so less clicking and scrolling was involved? Is it just my imagination?

    Honestly, I don’t know.

    By the time I got used to the new Settings app, one of the big Windows 10 makeovers happened and jumbled up about 15% of Settings. Objectively not much, but just enough to irritate.

    And now with 11, they not only made Settings unrecognizable, they also cranked the spyware up to, well, 11. And there’s no Control Panel to default on when in doubt (or fuming with rage).

    All in all, while Control Panel wan’t what kept me on Windows, 11 losing it did ease the transition, since it meant having to learn a new way of doing things either way. Might as well make it a way that hopefully won’t change once a random design exec decides “this is ugly and it has to go”.

    Honestly, KDE Plasma’s Settings are where it’s at. It’s right between the functional and informstional density of Control panel and the simplicity, visual appeal and saner structure of Settings. Shame it uses Qt, which from what I hear, is god-awful as far as UI toolchains go.



  • About the Ribbon: Apparently M$ has a patent (or multiple ones on) it, so they ultimately have the last say on what is and isn’t allowed. They did make a licence availiable royalty-free, but I assume that that licence didn’t cover enough of what LibreOffice needed, so they probably struck a deal with M$ about having the option, just not as the default.

    I haven’t researched this all that much, so mostly speculation. Although the M$ having a patent part of someting so true. And that patent (apparently) explicitly states that use in directly competing software with M$'s is forbidden, at least for-profit.

    Idk, maybe it’s a case of patent restrictions, or LibreOffice being LibreOffice.

    Honestly, a really interesting rabbit-hole.