Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)C
Posts
45
Comments
244
Joined
4 yr. ago

West Asia - Communist - international politics - anti-imperialism - software development - Math, science, chemistry, history, sociology, and a lot more.

  • The terminal world has Ctrl+C and Ctrl+(many other characters) already reserved for other things before they ever became standard for copy paste. For for this reason, Ctrl+Shift+(C for copy, V for paste) are used.

  • Why would one be discouraged by the fact that people have options and opinions on them? That's the part I'm not buying. I don't disagree that people do in fact disagree and argue. I don't know if I'd call it fighting. People being unreasonably aggressive about it are rare.

    I for one am glad that people argue. It helps me explore different options without going through the effort of trying every single one myself.

  • Doesn't feel like that to me. I'll need to see evidence that that is the main reason. It could be but I just don't see it.

  • Xorg is a display server for Linux ecosystem. Every ecosystem has a display server. It is what makes it possible for you to have graphical applications with movable windows that can talk to each other, or have a mouse cursor that can click on things.

    Wayland is a replacement for Xorg because Xorg is old and its developers said an alternative is needed. Wayland has differences that I won't discuss here, but I'll be happy to do so if you ask.

    Hyprland is a wayland compositor. A compositor is basically an implementation of wayland (there are many) and gives you a windowing system that you can run graphical applications through. It is usually a lot more minimal than having a full graphical desktop like KDE or Gnome.

    Hyprland belongs to a class of comositors called "tiling", which forces windows to be in a tiling formation. In other words, windows do not overlap or stack on top of each other. Hyprland stands out in having a lot of eye candy and visual effects.

    I use CLI for moving files, etc. After you use it for a while, you find out it can be more efficient, faster, and more pleasant to work with.

  • I have a feeling this is a joke. Either way I'm not following sorry 😭

  • A symlink works more closely to the first way you described it. The software opening a symlink has to actually follow it. It's possible for a software to not follow the symlink (either intentionally or not).

    So your sync software has to actually be able to follow symlinks. I'm not familiar with how gdrive and similar solutions work, but I know this is possible with something like rsync

  • I didn't look much into void, but when I did, gentoo's repository is much larger and there are many packages that I'd call obscure that happen to be in the main repos.

    The situations I've had to reach to guru are rare. I bet that gentoo has more obscure stuff in its main repo, though I don't have the numbers to prove it.

  • Any examples other than ocaml? From my understanding, ocaml's type strength may only be found in a couple other languages. Haskell, scala, and maybe Rust. Any others?

  • GURU is source only

    Is void different? Does it have a user repository that provides binaries directly?

    My familiarity is with AUR, which does not provide the binaries directly. I suppose you can write a PKGBUILD that only installs a binary, but you could do the same with ebuild.

    On binary support, I imagine you're right. Binary support in gentoo is new. I imagine it will only get better.

  • You already said it, but even if you want mostly binaries, gentoo is becoming a distribution that can do that. So I don't think this is something that sets them apart.

    Plus, gentoo handles compilations so well, it is almost as simple as binary package managers.

  • The author would likely really enjoy gentoo. Imo it has all those benefits and a little more, plus its more popular.

  • I won't remember everything, but one very important things comes to mind:

    in Typescript, it is very difficult to assert on a type (let me know if you're not familiar with what I mean by this and I can explain further). In OCaml, this is trivial using pattern matching.

    Why would you need that? The idea of a type system is it doesn't let you apply a function on a structure without the structure being of the right type. But the lack of type assertion in TS makes people follow hacky workarounds, which defeat the purpose of type system.

    There are a couple of other things, like immutable types by default, automatic tail call optimization, functors enabling higher kinded types, etc.

    Also in ocaml, you don't have to annotate any types on any variable or parameter, and you'll still get full type protection.

  • Move account to another unethical, profit driven bank or?

    Y'all still believe in the illusion of choice / opt-out in capitalism.

  • The only valid argument against typescript is that it is too similar to vanilla JavaScript. It does not go far enough. We need type systems like Ocaml's.

    I suppose you can also complain about needing a build step, but I find this silly. There are so many tools that make this easy or automatic.

  • I have two arguments: first, it's not true that the OSI coined the term. But more importantly, it isn't even important if it was true. What matters is the context in which the open source movement emerged, and how people who use the term think of it.

    The open source / free software movement was born in universities who primarily wanted to erase the barriers on collaboration between them, and wanted to follow an open model. They grew frustrated of the proprietary and opaque model of software written by major corporations. They could not use it. So they decided to write their own free software and combine their efforts to not rely on corporate or proprietary software.

    Back then, corporations were uninterested in open source. In fact they were hostile to it and wanted it to die. The issue that we deal with today of corporations leeching on open source did not exist, so the fact that the movement did not specifically fight this does not mean they're okay with it. The corporate hostility took a different form and that's what they combatted.

    On OSI coining the term, the OSI themselves claim it was coined by Christine Peterson. They do not claim that they founded the term, nor that the founder had an affiliation with them: https://opensource.org/history

  • What did the original kernel not support?

  • with strong copyleft licenses, businesses must give back, namely when expanding the program

    A user is required to make the source open only if they create a derivative work of the copyleft licensed work, and only if said work was distributed to users. And if I remember correctly, it is only required to open the source to the users it was distributed to.

    They do not have to do any profit sharing or donation. They are not even required to make the code open source if they merely use this program, or they interface with it. They are not required to do anything if they only use it internally.

  • no, thats also the open source definition

    Correction: the definition of open source by a specific organization, the OSI.

    I don't remember voting or appointing the OSI as our legitimate representative. But you know who did? Corporations like Amazon, Google, Bloomberg, and many of them: https://opensource.org/sponsors

    I do not subscribe to a definition from such an organization, just because it has open source in the name.