• 2 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2023

help-circle


  • I believe for many companies, developers work on giant codebases with many hundred thousands or even millions of lines of code.

    With such large codebase you have no control over any system. Because control is split between groups of devs.

    If you want to refactor a single subsystem it would take coordination of all groups working on that part and will halt development, probably for months. But first you have to convince all the management people, that refactor is needed, that on itself could take eternity.

    So instead you patch it on your end and call it a day.






  • Ok, because of this post - I decided to bite the bullet and try wayland again. And it was much better experience this time:

    I’ve installed sway “pattern” on OpenSuse-Tumbleweed and:

    • Previous time I had some issues with lightdm not supporting sway, now - it just works.
    • I still use xdotool and i3-msg in my custom scratchpad script and yet everything is working.

    waybar absolutely supports clicking tray icons.

    I confused it with swaybar, that’s installed with sway by default and should be an i3bar-compatible. Waybar doesn’t seem to support i3bar protocol, but anyway, after I configured it - it’s like 95% there from what I want.

    • I had to force xcb platform for appimage of nekoray (qt VPN gui), because it’s complaining about missing wayland-egl plugin. But it’s a small problem with straightforward fix, so not that bad.

  • I could switch tomorrow if I could do my current setup:

    • Tiling Window manager (sway?)
    • simple status bar to output text from a script with clickable applet icons (waybar?)
    • the way to show/hide windows on a button press - I have a script that I use to quickly toggle 3 dropdown terminal windows

    Last time I tried Wayland in December, I had issues with waybar not supporting clicking tray applet icons. Also I’ve ported my dropdown terminals script to support sway - and it worked half the time, like, literally every second key press was ignored.

    On one hand I have X session that currently has no downsides for me, on other - wayland that has no upsides. Tell me, why would I switch?



  • Well, then you have to find another name for that kind of software and define it that way. I certainly would support such an effort, i.e. to make software available to everyone at no cost.

    There’s no need to come up with new terms or change the existing ones. Free software is inherently free in price. And you can’t enforce paying for software without the restrictions put in place (e.g. drm). Here’s a quote from https://www.gnu.org/philosophy/selling.en.html :

    With free software, users don’t have to pay the distribution fee in order to use the software. They can copy the program from a friend who has a copy, or with the help of a friend who has network access. Or several users can join together, split the price of one CD-ROM, then each in turn can install the software. A high CD-ROM price is not a major obstacle when the software is free.

    Free software can have a price, but paying it is optional.


  • I meant that free software is inherently can’t have a price. Even if you provide source code only to your users, they are free to share that source code for free.

    Thus there can’t be piracy because piracy of free software is inherently allowed.

    And if you try to prevent your users from sharing the source either legally or with drm - you add restrictions to software, making it less free for your users.

    The recent situation with RedHat provides good demonstration and example of this.


  • It’s free as in freedom, not as in free beer.

    But you can’t have one without the other. Putting a cost on software is adding a restriction, thus making it less free (as in freedom).

    Free software should be available to everyone, even to people who don’t have money to pay for it (poor third world countries, students, kids).

    I personally believe, that you should pay for software that helps you earn money. For everything else - it’s everyone’s own decision to donate or not, based on a financial situation, beliefs, political position and what not.


  • For one - the error handling. Every codebase is filled with messy, hard to type:

    if err != nil {
        ...
    }
    

    And it doesn’t even give you a stack trace to debug the problem when an error happens, apparently.

    Second reason - it lacks many features that are generally available in most other languages. Generics is the big one, but thankfully they added them in last half a year or so. In general Golang’s design principle is to implement only the required minimum.

    And probably most important - Go is owned by Google, aka the “all seeing eye of Sauron”. There was recently a big controversy with them proposing adding an on-by-default telemetry to the compiler. And with the recent trend of enshittification, I wouldn’t trust google or any other mega-corporation.


  • janAkali@lemmy.onetoLinux@lemmy.mlFlatpak can look daunting...
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    11 months ago

    I have all apps I use daily in the appimage format. Yesterday I decided to try btrfs for my root partition and did my annual Linux reinstall. All my apps were already there and ready for work from the start.
    I also have a usb flashdrive always on me with the same appimages. Just in case I’d wipe a hard drive by accident and wouldn’t have an internet connection or something like that (in case of emergencies). You can’t do this with flatpaks or snaps.








  • While most of the time, I remember my password, I know I could just snap and forget it right there at any point. Happened to me not once. And I’m in my 20s. Sometimes when I forget a password, I just start typing and muscle memory kicks in, sometimes it doesn’t. I guess our brains are not optimized to store long random strings of characters. You could use a long sentence as your master password or do as I do:

    Come up with a way to make up a long seemingly random password from a couple words. Then if/when you forget a password, just remember those words and reconstruct password from them.

    • Don’t use common dictionary words or anything from popular media, as it could be guessed by attackers.
    • You can write down algorithm on a piece of paper and keep it somewhere safe.
    • Words should be related but not directly:
      • two asteroid names - bad
      • asteroid name and it’s greek translation - bad
      • real city name and city name from a book - good
      • two words that both start with S and end with T - good
    • If you forget both words, you should be able to remember/look up at least one of them if you still remember how you came up with the word.