[-] lime@feddit.nu 8 points 1 day ago* (last edited 1 day ago)

i can chime in with some actual experience!

my current problems with KDE are

  • the greeter only accepts my password on the secondary monitor
  • the compositor shuts down whenever something uses the GPU even though the setting is off
  • my primary desktop randomly shunts itself to the right, plopping on top of the desktop on the secondary display and leaving a big black void on half my primary until plasmashell is restarted
  • my panels keep collapsing their content down to the width of a single pixel until i resize them
  • Wayland just crashloops and is completely unusable (no, i don't have an nvidia card)
  • i still can't get the acrylic transparency to work :(

and what's fun about this is, the issues are so intermittent and random that i never know what i'm going to get on a given day!

[-] lime@feddit.nu 16 points 1 day ago

no that's literally the description of the other axis...

[-] lime@feddit.nu 4 points 1 day ago

as i understand it, the money goes to the foundation, and it's the corporation that develops the browser. so it's probably not strictly forbidden, but it does imply that the money is not for browser development.

[-] lime@feddit.nu 2 points 1 day ago

good point, ruby is a good comparison. although, ruby is very different under the hood. it's magically dynamic in a completely different way, and it also never really got the penetration on the system level that python did.

none of this is to take away from the fact that python packaging is bad. i know how to work it because i've been programming in python for 14 years, but trying to teach people makes the problem obvious. and yet.

[-] lime@feddit.nu 29 points 2 days ago

it's when you dodge all the shots

[-] lime@feddit.nu 19 points 2 days ago

the Chilluminati podcast episode on him talks about how he had a really squeaky voice. like, imagine if mickey mouse could karate chop you.

also, he is still alive.

[-] lime@feddit.nu 7 points 2 days ago

in the health sector specifically, IT is a mess because you can't stop people from working or there will be deaths. one thing you should take away from this is that their jobs are important and it is crucial that they can do them. it is your job to support them; anything that stops them doing their job or makes it take longer, even once, is dangerous. improving infra for its own sake is not a good idea because it comes at the risk of peoples lives. the details don't matter in the face of that.

if this stresses you out, you can absolutely change jobs. i did.

if you think you can work within those parameters, and you think you can find ways to improve the system in-place while mitigating the risks, then you will be highly respected.

[-] lime@feddit.nu 12 points 2 days ago

hypothesis: the last reply is usually left there to stop hundreds of people replying that exact same thing below.

[-] lime@feddit.nu 41 points 2 days ago* (last edited 2 days ago)

mozilla takes donations, but they don't fund Firefox development with that money. that's usually what people have against it.

[-] lime@feddit.nu 3 points 2 days ago
[-] lime@feddit.nu 9 points 2 days ago* (last edited 2 days ago)

my dude, just seeing the text is too much effort.

[-] lime@feddit.nu 9 points 2 days ago* (last edited 2 days ago)

me, watching a friend play a game (that i play) for the first time

17
submitted 1 month ago* (last edited 1 month ago) by lime@feddit.nu to c/kde@lemmy.kde.social

I have two monitors, one 1440x3440 and one 1080x1920 to its right. Every boot, the desktop on my left monitor moves over and displays on top of the right one. Killing and restarting plasmashell moves it to where it should be, but i'd love to fix this without adding that to my .xsession. Thing is, i'm not versed enough in the KDE internals to know where this issue even stems from.

I'm running EndeavourOS with Plasma 6.1.5 on X11. I haven't tried wayland since Plasma 6 switched to it and then promptly flickered itself into a crash.

Edit: This machine runs the amdgpu-pro driver, and has done since before plasma 6 released. i didn't have this problem on plasma 5.

view more: next ›

lime

joined 2 months ago