• 5 Posts
  • 324 Comments
Joined 6 years ago
cake
Cake day: May 31st, 2020

help-circle


  • Ja, auf den Paradigmenwechsel warte ich auch noch. Also so langsam kapieren die Leute, dass lange Texte nicht automatisch geil sind, und auch dass man nicht überall irgendwelche nichtssagenden Bilder reinwerfen muss, nur weil man es kann.

    Aber letztens hat z.B. bei uns das Management so 'ne Mini-Lotterie gemacht und am Ende wurden 3 Personen ausgewählt. Diese 3 Personen mussten dann natürlich per KI-Video verkündet werden, weil das der neue, heiße Scheiß ist.
    Aber wenn man’s eben mal trocken betrachtet, dann hatte das ungefähr die selbe Energie wie so ein Standard-Template aus dem Windows Movie Maker, anfang der 2000er Jahre.

    Also nicht nur, dass das Video inhaltlich maximal unspektakulär war (eine Schriftrolle hat sich entfaltet und dann wurde ein Schriftzug darauf geschrieben), sondern es war auch so unfassbar unpersönlich.
    Die vorstellende Person hätte einfach live dreimal den Zufallsgenerator laufen lassen können und von mir aus noch bei jeder gewürfelten Person kurz etwas jubeln können, und es wäre tausendmal spannender und menschlicher gewesen.


  • Ah shit, here we go again.

    I almost expected someone to learn that just from me posting. 😅

    Basically, OpenOffice used to be organized by Sun Microsystems. Then Sun got bought by Oracle back in 2010.
    Oracle does not have a good reputation at all, so the OpenOffice devs from back then figured they’d need to take things into their own hands and set up The Document Foundation to organize further development. But the OpenOffice trademark was owned by Sun/Oracle, so they had to rename and get a new homepage and everything. The name they chose is LibreOffice: https://www.libreoffice.org/

    After the OpenOffice project was effectively dead, Oracle handed it and its trademark over to the Apache Foundation, where it’s seeing occasional bug fixes. But to my knowledge, they don’t even have the capacity to fix all the security problems.
    All the actual feature development happens over on the LibreOffice side.

    So, in practice, if you want OpenOffice, what you really want is LibreOffice.


  • Yeah, not great. You always hope that projects under a larger foundation, like GNOME, have a higher bus factor¹, but unless that foundation has dispensible income to pay someone, you’re ultimately still reliant on volunteers and not many people volunteer for maintenance.

    What the foundation can do, though, which is also really important, is to hand over the keys to a new maintainer, should you disappear over night.
    Like, yeah, forking is great, but some people will never learn of the fork. It happens about once a year that I find someone online who’s still using OpenOffice and that project has been practically dead since 2011.
    So, I do hope we can get more open-source projects under some sort of umbrella. No idea how to actually do that, though. I also have open-source projects where I would not even know where to start to get them under some organization…


  • The Rust compiler is more sophisticated than most compilers, so it can be slower at the same kind of tasks. But it also just does a different task here.

    One of the tradeoffs in Rust’s design is that libraries get compiled specifically for a concrete application. So, whereas in most programming languages, you just download pre-compiled libraries, in Rust, you actually download their source code and compile all of it on your machine.

    This isn’t relevant, if you get a pre-built binary. And it’s not particularly relevant during development either, because you get incremental compilation. But yeah, if someone wants to compile a Rust codebase from scratch, then they have to sit through a long build.








  • I’m on NixOS for my personal laptop, too. I just tried it and well, #!/bin/bash apparently does not work, but #!/bin/sh does.

    The file /bin/sh does also exist as a symlink for me:

    > ls -l /bin/sh
    lrwxrwxrwx 1 root root 73 14. Dez 19:50 /bin/sh -> /nix/store/35yc81pz0q5yba14lxhn5r3jx5yg6c3l-bash-interactive-5.3p3/bin/sh*
    

    Does that point into the bash package for you, too?


    Edit: And for #!/bin/bash, the output was:

    > ./test
    exec: Failed to execute process './test': The file specified the interpreter '/bin/bash', which is not an executable command.
    

  • Well, it won’t work for Kate, because Kate is implemented using the Qt framework, so will preferentially use the Qt theme on your system. You would have to try it on e.g. Inkscape, which uses the GTK framework. (I did just try it on Inkscape to confirm that.)

    We’re getting into the technical details of how these applications are implemented, so I can’t make this any less confusing.
    But basically, KDE generally uses Qt, but it also generates a GTK theme, so that Inkscape et al don’t look out of place.
    Applications not specifically developed for Linux are likely to refer to that GTK theme for their own theming, even if they aren’t implemented in GTK themselves. Firefox also does this, for example.

    UnityModManager seems to be implemented using neither Qt, nor GTK, but rather Microsoft’s .NET Framework. So, yeah, kind of no idea what it’s gonna do here.

    You could try telling KDE to generate a specific GTK theme and see if that does anything: (There’s a button in the top-right of the screenshot.)

    You may also want to see, if it’s maybe this issue: https://github.com/newman55/unity-mod-manager/issues/88



  • That is definitely not right. That sounds like you don’t have a shebang or it isn’t defined correctly. The shebang has to be the very first thing in the script, with no whitespace before it. It gets read out by the kernel, which very dumbly checks the first few bytes.

    And well, such a shebang should also work for Python or the like. If you copy the first script in this link into a file script.py, then run chmod +x script.py and finally run ./script.py, does that print Hello, World! ?





  • This might work: https://discuss.kde.org/t/change-color-or-theme-of-specific-window/1884/6

    I’m not familiar with Unity Mod Manager, so hard to say or give detailed instructions.

    If you happen to know how to run Unity Mod Manager from the terminal, the easiest way to check whether it will work, is by first running export GTK_THEME=Default and then running Unity Mod Manager in the same terminal.

    This export command sets an environment variable (GTK_THEME). In case Unity Mod Manager respects the GTK theme of your system, it will presumably respect that environment variable.

    From what I’ve quickly read up on Unity Mod Manager, it is implemented in C#, so I’m guessing it does not use GTK directly (but might still try to emulate its theme from the GTK theme) and well, it might behave weirdly under Linux in general…