• 1 Post
  • 65 Comments
Joined 3 years ago
cake
Cake day: June 2nd, 2023

help-circle

  • I use Debian BTW.

    I don’t really run around yelling about it. I mostly use derivatives like Mint, Raspberry PI OS (such a dumb rebranding) and armbian , but stock Debian goes on some servers since it just works. I’m not tuning anything nor looking for special packages. Unless there’s a driver issue (old Debian problem), it’ll be boring and work.

    Use what tools work for you.

    Huge thank you to the Debian devs. You’ve done me good tools for decades now.




  • That’s what I was taught at my first tech internship. It’s all they had on the UNIX system running the webserver in 1998.

    I did write some web pages the pulled live data from the backend. I had the pleasure of writing them in C. I got the data binding to some kind of CORBA system using extern variables that were bound at compile time. All of the html (no js or css yet) was hand built and generated from the C code.

    vi was the only editor on the system and there was no way to use arrow keys (the UNIX system didn’t have them on the keyboard at all).

    I also had the displeasure of building a backup system on a floppy where I had to write a bat script that could manually load a token ring driver, bind a SMB share, load Ghost backup software and backup the local hard drive at under 2mb (yay coax thicknet). The tool used to query and write through the hostname for the backup? Copycon. Fucking copycon in DOS. That showed me how a terrible (but working) tool could be to work with.

    Unless an editor can do reasonable vim emulation, I can’t take it seriously. You’re welcome to use it, but I won’t be able to get anything done in it quickly. The vi keys are too ground into my reflexes.


  • azimir@lemmy.mltoLinux@lemmy.mlsystemd(ont)
    link
    fedilink
    arrow-up
    43
    arrow-down
    8
    ·
    2 months ago

    Use what works for you.

    Develop what scratches your itch.

    Don’t tell OSS devs who are volunteering unpaid labor what they should do for you.

    If you want a solution that’s non-systemd go for it. If it doesn’t exist make it or pay someone to do so. Write from scratch or fork a project and get to work. That’s the way of the Bazaar.

    I’ll be in my unenlightened “things work for me good enough” Linux world using what works. Systemd is fine and rarely gives me problems. Actually, I’m not even sure I can remember any.

    Huge thank you’s to the devs who make this all possible. You rock!












  • I don’t know every detail of your use cases, but my offline go to is xournal++ (xournalpp).

    I use it for many of those actions. We moved to Germany and having a GUI pdf editor for signing, highlighting, redacting, pulling pages, etc has been invaluable.

    My wife also uses it for her class lectures. She does math, so she uses a tablet to write on her slides (pdfs) live in class to talk through the material. Then, she saves the lecture PDF to give to students with the notes.


  • Highlight->Middle paste has been my friend for decades now. Using it from SunOS in the 90-s to now has been a great feature. It’s the quickest way to copy and paste while I’m working fast with text or data entry.

    I love having both clipboards be functional. The latest rounds of tools that have stopped being as compatible with it has been no end of problems in my workflow. I’ll copy with the keyboard, highlight some text and then paste both clipboards somewhere else.

    No, using the keyboard here isn’t as fast, don’t bother making that argument, especially since ctrl-c means different things in different places on Unix style systems. Left hand stays home row while the right is forced to leave for the mouse since it’s a GUI.

    I’ve had to deal with many tools that don’t respect keyboard cut/paste as well. Add in that some tools like putty or git bash on windows have ctrl-ins for paste?

    Panning in CAD/design is usually click and hold middle or even a two button system (freecad), so trying to take a middle click for that isn’t buying uniformity.

    The copy/paste world is already fractured enough. Keep the highlight/middle click working so we can go fast. I might be a dinosaur, but I’m a fast dinosaur.



  • The biggest limitation on the older models is RAM. There’s other issues with network contention (the Ethernet is actually a USB device on the board), raw CPU (especially gen 1 boards), but really it’s all about the RAM.

    I use these kinds of boards for more hardware/embedded kinds of situations. No GUI Linux machines will easily run in 200-400MB of RAM before you start spinning up additional services or tools.

    If you’re really RAM blocked you can use a more stripped down Linux install or even hop to BSD and run real lean on resources for the OS. All of these options can still run most network services or simple build/dev kinds of support systems. They could be message queue servers, run GPIO-driven hardware systems, be sensor platforms, run DNS/DHCP/PiHole kinds of systems, be a speaker driver endpoint for a larger system, bong a clock sound every hour, or whatever. That’s just what I could come up with while typing on the fly. If you start adding hardware to the IO ports it just goes nuts what even the older boards are capable of.