I'm assuming you've already found it, but just in case you didn't: Framework has setup guides for Fedora, which presumably should make everything work as intended. Find your device on this page, then click "Fedora 39 Setup Guide" on the right-hand side: https://frame.work/linux
Long time since I used Ubuntu, remember updates breaking network twice… Peppermint OS, Debian(and devuan if you don’t like systemd) based. all the important bits (not arch level) but nothing more. Rolling, Runs on 1 GB ram. Haven’t distro hopped anymore since I found it.
I've been really happy with it; I've been using it for templating reports at work for months now. I've just started experimenting with using jinja to pretemplate my template lol.
I'll probably continue down that track to try and automate my workflow away so I can focus on less tedious things, but after you get used to the box encapsulation it becomes fairly easy to work with!
Without having tried typst myself, I would still recommend learning LaTeX, if you’re ever looking to publish in a scientific journal; most journals accept submissions in either Word (which in my mind is a very painful tool to use, especially when it comes to typesetting and equations) or LaTeX. They then typically convert the input to some internal format, but are probably unlikely to add support for new formats.
If you only ever intend to write documents for your own purposes, use whichever format you like the best; I personally use Emacs Org-mode and LaTeX export.
I want to use it, but if I’m going to commit to learning a new system for my work, I need to know that 1) it will remain open source (like LaTeX), 2) its going to remain maintained, 3) it has a robust package library, 4) it has to understand bibtex. I dont think typst has committed to the first, its not mature enough for 2 or 3, and I cannot for the life of me figure out how to automate translation between bibtex and their funky format.
Maybe add a 5) needs to be able to export to LaTeX. It might be nice and easy to write in typst, but you'll sooner or later hit the wall of "We accept submissions in Word and LaTeX only."
For a user: In Wayland programs are supposed to draw their own title bar. Java aplications and old applications must use a backwards compatibility layer that can cause flicker and bad font rendering. The terminology is different (compositor = window manager). Some niche new programs may only run on Wayland. Wayland hasn’t been adopted by BSD (AFAIK).
For a programners: Wayland has more modern, tidy code, but not all toolkits support it natively and few are easy. If you code exclusively for Wayland, a lot of users won’t use your program at the moment.
In Wayland programs are supposed to draw their own title bar
That’s incorrect. GNOME does it like this, Plasma doesn’t. KDE came up with a standard so a program can communicate this to the DE, GNOME slept on it. That’s why e.g. mpv doesn’t run well on GNOME.
Java aplications and old applications must use a backwards compatibility layer that can cause flicker and bad font rendering.
There have been efforts to provide better support for Java applications on the Wayland display server. For instance, the OpenJDK project has been making progress on implementing native “pure” Wayland toolkit integration not dependent upon XOrg/X11 or XWayland.
but not all toolkits support it natively and few are easy.
There have been significant developments in providing native support for Wayland in various toolkits. For example : Clutter, GLFW 3, SDL, GTK 3.20+, QT5+, EFL, & OpenJDK. Just to name a few.
While it is true that not all toolkits have full native support, ongoing work is/has largely shifted towards much better Wayland support.
Both are display servers which is software that allows programs to write to the screen. X is older and was created back in 1984 at MIT and Wayland is a much newer protocol that is designed to work better on newer (post 90’s) hardware.
The biggest difference is that Wayland basicly allows your desktop direct access to the screen and X has a server that runs and allows your desktop to connect to it. X was originally designed to run remotely as back in the day there was one big commuter that many people connected to.
If this is all very confusing you probably should just stick to your distros defaults. Most of the time you don’t need to care.
Wayland is a communication protocol that specifies the communication between a display server and its clients, designed to be a replacement for the X11 window system protocol and architecture.
I might be a little nitpicky here, but I feel it’s an important distinction to make as there is no single common Wayland server like Xorg is for X11.
A display server using the Wayland protocol is called a Wayland compositor, as it additionally performs the task of a compositing window manager.
Xorg on the other hand is basically one fat display server designed like a house of cards that everyone uses.
Wayland is a new implementation on how your system draws windows and components in your computer (I’m not sure if it’s responsible for the content) and it tries a different way to do it compared with xorg.
Xorg is the old implementation, and it has been patched to support most of the new features, and Wayland is trying to get the same features xorg has and some extras.
As a Linux user I have noted that sharing screen is more private in Wayland, also I think multi monitor refresh rate was a problem in xorg. One common issue with Wayland is the GPU compatibility, as far as I know Wayland runs better in AMD GPU I think is because of Mesa integration.
xorg is a old implementation of x11, which is basically abandon-ware right now. No one is adding feature to it, testing it, or fixing security vulnerabilities. It also lack some common-sense security feature: for example every program cam get every input (keyboard and cursor location) without root, so a key logger is trivial to implement in xorg.
Wayland is newer, with more features (reasonable multi-monitor support, one-to-one gestures, etc). But many application framework and hardware have poor support for it, because it is new. Notably, electron and nvidia are typically the worst offender, like everything on linux; but both has come a long way.
I have wayland on my laptop, since one-to-one gesture is a must for me, and I present quite often using that laptop. My desktop is on xorg, since I have a nvidia GPU and use quite a lot of electron app.
AMD GPU + KDE Plasma with Wayland finally gets me close enough to the smoothness of Windows, especially the per-display settings for fractional scaling and high refresh rate were sorely lacking on Linux. It’s not perfect yet (and neither is Windows’ implementation) but it improved the Linux desktop experience a ton!
Desktop Linux is in its never-ending process of replacing old displaying system with new one. The process is long and not really transparent, because the two displaying systems were designed in completely different times for different hardware and with different security concerns in mind, therefore the X11 clients (all the software that was ever made or ported to Linux) are very much incompatible with Wayland. For backwards compatibility there’s Xwayland, which provides full blown Xorg server running on top of Wayland compositor with all the things X11 app requires. Until now, Firefox, even though had its Wayland backend as WIP feature (possible to activate with environment variable MOZ_ENABLE_WAYLAND=1) it defaulted to Xwayland on Wayland sessions. It now uses native Wayland backend by default providing better efficiency, DPI scaling, touchpad gestures etc
Jesus fucking christ this is a hell of a project, Ill finish reading when I get home today.
Hats off to you for pulling it off. Why is it that every time I read something by a NixOS person I get the inpressiom that they are very smart but are completely mad.
Not sure if you're still following Luwx/Lightly, but there's a fork of it - boehs/Lightly (though for what I've seen the changes it has had have been imperceptible).
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.