Explore >> Select a destination
|
You are here 
|
sgfault.com | ||
| | | | |
rugu.dev
|
|
| | | | | [AI summary] The user has transitioned to Arch Linux, finding it more efficient and customizable compared to other operating systems. They use a tiling window manager, dwm, and have customized their keyboard layout for both Turkish and English. They rely heavily on the terminal for all tasks, using st and bash, and prefer neovim for text editing. They utilize dvtm for managing terminal sessions and ranger for file management. The user also employs gitjournal for note-taking, pass for password management, and uses Brave with Vim keybindings. The overall experience has been challenging but rewarding, leading to increased productivity and a deeper understanding of their workflow. | |
| | | | |
blog.martin-graesslin.com
|
|
| | | | | [AI summary] Martin's blog posts cover various topics related to KDE development, including his decision to step down as a maintainer of KWin, the challenges of transitioning to Wayland, and discussions on benchmarks and user interface features. He also addresses user concerns about shadow effects in Plasma and the implications of not setting the QT_QPA_PLATFORM environment variable by default. | |
| | | | |
michaelneuper.com
|
|
| | | | | Introduction If you're a Linux user, you're probably familiar with the concept of window managers and desktop environments. These programs are responsible for managing the appearance and functionality of your desktop, providing the tools and features that you need to interact with your operating system. But what's the difference between a window manager and a desktop environment? And why might someone want to turn a window manager into a desktop environment? | |
| | | | |
kiljan.org
|
|
| | | Running Arch Linux RISC-V on a Milk-V Mars presents several challenges. Most notably is that the young operating system is not easy to start with. But just because it is a bit difficult does not mean it is impossible. | ||
