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/)D
Posts
8
Comments
318
Joined
3 yr. ago

  • It’s a school?? Who are the shareholders?

    The fact that a school has to be pulling this kind of stuff…

  • Outside of programming circles I’ve been surprised how little people know what != means.

  • I would do a cool S.

     
        
    
       ^
      / \
     /   \
    /     \
    |  |  |
    |  |  |
    \  \  /
     \  \/
     /\  \
    /  \  \
    |  |  |
    |  |  |
    \     /
     \   /
      \ /
       v
    
      
  • No problem! Actually, System76 is currently working on rewriting the COSMIC desktop in Rust (or really, just writing a new DE in Rust). It’s a pretty ambitious project that should hopefully get released some time this year. I wouldn’t be surprised if the lead redox dev was working on it too: low-level Rust knowledge is exactly what they need.

  • Perhaps not all 24 million people will cash out? IDK.

  • It’s surprisingly possible (and easy) too… a little bit of tinkering with X11’s compositor API would probably do the trick.

    IDK about Wayland tho :/

  • LMDE and PopOS are my consistent recommendations to newcomers. If one doesn’t work, the other will.

  • I love how simple and small scale splitting an atom sounds. Then you get to doing it…

  • Well, think microkernels as the bare minimum. They give you just enough to write your own OS on top of that: only the bare essentials run in kernel space, whilst everything else runs in user space and has to communicate with the kernel. Compare this to a monolithic kernel, like the Linux kernel: here, the whole operating system is run in kernel space, which means that data doesn’t need to be moved between user and kernel space: this makes the OS faster, but at the cost of modularity. Redox doesn’t use the Linux kernel, it uses its own microkernel written in Rust.

    Edit: A good example would be driver. In a microkernel, these run separately from the kernel and interact with it when needed. In a monolithic kernel, these drivers would be included in the kernel itself. They both have their pros and cons: if you’re interested, feel free to look it up.

  • I just realized that’s a nose and not a tear…

  • Hey, me too! Only really use them for the occasional hobby project, just went with what my dad went with.

  • Not your fault if you did have a strong password but your data was leaked through the sharing anyways…

  • That’s fair. I started with what everyone was using at the time, which just so happened to be Neovim. I’m also too lazy to switch/try anything else.

    Plus, I’m not sure if Neovim simply extends Vim functionality. I know it’s a fork, but the codebase has changed so much I’m pretty sure many newer features of Vim need to be manually added to Neovim. Inlay hints in the middle of lines is already implemented in Vim: as for Neovim, it’s not here yet (well, it’s coming in 0.10, but I don’t use nightly so I don’t have it)

  • I mean, I’d just bind vim to nvim. If you still want vim accessible, bind it to something else. I don’t really see any downsides to Neovim: it’s decently backwards compatible, enough to use most old plugins, with the advantages of Lua config and a much wider repository of plugins.

  • You are a nerd with too much time

  • Simply poetry.

  • So…Mastodon…with ads?