• 11 Posts
  • 160 Comments
Joined 4 years ago
cake
Cake day: February 1st, 2023

help-circle



  • edinbruh@feddit.ittoLinux@lemmy.mlBan Windows at schools
    link
    fedilink
    English
    arrow-up
    134
    arrow-down
    1
    ·
    12 days ago

    I wouldn’t “ban Windows at school” as a whole but I would:

    • ban schools from installing windows in school computers
      • teachers and students can still use it on their own computers, if they want
    • ban teachers from requiring windows-only software
      • regardless of what you use at school, teachers would often require MS office or Adobe for homework, which would force students to use windows at home


  • This👆

    That’s why I referred to it as “plain”: it’s just the reader. And it is mostly made to replace the original reader software on eBook devices, but you can also use it on desktop if you want.

    The question is if you are looking for just a reader, or a library manager. But you can also mix the two, so use calibre fo manage the library and have it use koreader to open books






  • In principle integrated graphics are better. They share the same memory as the CPU, so games can just modify memory in place instead of doing a costly data transfer via pcie, this is one of the major pain points in emulators, games expect to just modify memory, while the emulator has to emulate this behaviour with limited bandwidth.

    The problem is that most computer games do not take advantage of this, and instead do pcie transfers even if they could simply not do that. Also PC APIs (DirectX, vulkan, etc) are not build around this ability, while console SDKs are.

    Plus, a console GPU is much bigger than usual integrated graphics. To put this into perspective, the major selling point of AMD’s me ai max etc etc CPU is the big integrated GPU… It’s still smaller than a ps5 GPU… It is more powerful because it’s newer, but it’s smaller, and the ps6 will likely have a bigger one.


  • And instead vscode supports SSH (without quotes), you can connect to an SSH host, and it will open files and folders on the host like it does locally. And if you open the integrated terminal it will run on the remote host. And it will forward the git login agent so you can commit or push with the credentials of your local machine. And it can forward ports from the remote.




  • no one cares if it’s the protocol or the implementation. it just works worse than x11 on modest hardware

    Actually, people that are not hell bent on using x11 do care… That is because the protocol is inherently more efficient than x11, and the compositor matters.

    So if you try to run kwin or mutter, there’s no doubt they are going to be more demanding than a plain xorg server (but not more than xorg+KDE or xorg+gnome). But if you try to use a compositor made for low hardware like labwc, it’s gonna run laps around xorg. And you can even use labwc on lxqt, so you get your familiar desktop environment but with a modern Wayland compositor.

    Just try it. Dig up an old intel atom netbook and see if you prefer using xorg or labwc


  • It’s there and it’s easy. Most people don’t use terminal text editors unless they are SSHing in a server, and they would only do that sporadically, so it makes no sense to become proficient in a complex text editor like vim or Emacs for that little use case.

    Sidenote: personally, I learned vim once, and used it extensively every day for two years. I stopped using it for one year and was back to square one. Now I use vscode for everything… Even when I’m using SSH, because vscode supports SSH