just an english enby living through the end times…

Formerly of:

  • 71 Posts
  • 264 Comments
Joined 2 years ago
cake
Cake day: January 28th, 2024

help-circle


  • WebKit (e.g. GNOME Web, vimb, surf) is always there, and Servo is coming on leaps and bounds.

    Also, for your consideration, there are:

    • w3m (text-based, but supports displaying images with sixel, kitty, or framebuffer)
    • Links2 (surprisingly usable)
    • Dillo (better engine, but less features)
    • NetSurf (better again, but you can’t use a custom search engine and the JS engine doesn’t seem to work)
    • Chawan (text-based, but actually supports modern HTML and CSS; can display images using sixel or kitty; also supports gemini[1])
    • Ladybird (bad dev, good product)
    • Stargate & Duckling (HTTP to Gemini[1:1] proxies, so you can browse the web with Lagrange)
    • Pale Moon & Basilisk (based on a fork of Gecko; still use XUL; may be a bit less secure, but disable JS and you might be alright)

    Of course Librewolf, Waterfox, Tor Browser, ans Mullvad Browser are doing their best to resist the bullshit.



    1. The network protocol; not the LLM. ↩︎ ↩︎






    • OS:
      • Arch Linux or OpenBSD, depending in how I feel
    • Editor:
      • Micro on Linux
      • mg(1) on OpenBSD
    • Plug-ins:
      • Micro has support for a few linters, which is all I really need
      • mg(1), meanwhile, doesn’t even have syntax highlighting
    • Terminal:
      • Kitty on Linux
      • XTerm on OpenBSD
    • Shell:
      • Zsh on Linux
      • ksh on OpenBSD
    • Version Control:
      • Git is the only realistic option (though Mercurial and Fossil are nice)
    • Code Hosting:
      • Usually Codeberg
      • I also have sourcehut
      • My Formula Student team uses GitLab
      • My university and another society use GitHub 🤮

    I usually licence my work under GPL if it’s a large project, or Beerware if it’s something smaller (or if it’s for internal use in one of my societies).

    Any coursework I do, however, gets licenced under BSD-3-clause. For this, GPL would be too restrictive and Beerware would be too informal, and BSD-3-clause is a nice middle-ground (as far as I’m concerned).