• 8 Posts
  • 168 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle








  • I was about to start learning Perl in a proper way, but always decided against it. I just can’t find a good reason for myself to write Perl code. Unless you want to read or edit others Perl code, what is the reason to learn it? GNU+Bash and Python are often enough for me.

    So why learning and using Perl in modern age and day as a newcomer to the language? Look, I’m not negative here, just asking honest question. Because I am actually searching for good reasons to learn Perl.




  • uMatrix prevents me from loading this statcounter website. :-( Can’t lookup how they measure things. In the comments people assume the stats would be counted by just looking up the user agent, which is a naive approach. I don’t think agencies dedicated to stats are doing it this simple. They have way more possibilities to track and to look what browser you are using. The stats are more accurate than you probably think. They do not need to know the exact version of browser you are using, just which type and maybe what operating system you are on.

    If a script for Windows does not work on Linux and fails, then they know you are not on Windows in example.




    • trust: The biggest trust factor difference to me is, who manages the package and how it is installed. Both are not packaged by my distribution maintainers, therefore I have trust issues with a program that important. However both are available as Flatpak. So I would recommend to install it this way.
    • updates: Another big factor is how often these are updated, especially security patches. In example for any Firefox based browser, I would not want to wait longer than 1 day before the fork is on the same version as the mainline Firefox.

    I personally would prefer LibreWolf over Mullvad, because it is based off Firefox.


  • It’s not a big deal to anyone except you.

    Wrong, this is a big deal for the developers, for the users and for any maintainer of packages.

    And this wasn’t a big change or new feature so they decided to implement it. It’s pretty bold to assume this was a huge change.

    It is by definition a big change. And I defined it in my first reply. As you ignore all of this and waste my time, I will not read any further and block you now.

    The KDE team really should consider a 1 year bug hunting phase without bigger changes like the thing about desktop edit mode we discussed here. This is my suggestion.


  • Compared to what I am talking about it is a huge change. My suggestion is not to do this. How I know it? Because I said so. It is my suggestion. Can we stop arguing about semantics and definitions of words? That’s not the point of my suggestion.

    My suggestion is to not do such big changes for 1 year and only focus on bug fixes and small changes for the developer and for the user. That’s the point. The desktop edit change is a HUGE change with new logic. It’s incredible complex compared to what I am suggesting.



  • At the moment I am not using your project, but I think this has its place even with Flatpak available. Because archiving Flatpaks is not as easy as arachiving AppImages. In example there are programs (emulators) I use Flatpak for, but from time to time I also archive a version of the official AppImage.

    And sandboxing comes up as a point everytime people talk why Flatpak is superior to AppImages. So tackling that point is good effort to me.

    Edit: Think about renaming the project. It’s not very memorable and also the ai in the name suggests it has something to do with artificial intelligence.