Ready to be published? LXer is read by around 350,000 individuals each month, and is an excellent place for you to publish your ideas, thoughts, reviews, complaints, etc. Do you have something to say to the Linux community?
Disclaimer: The opinions expressed in this article are the writer’s own and don’t necessarily reflect those of Linux User & Developer magazine or Imagine Publishing Ltd. As the developer of an independent Linux file and desktop manager, one gains a multifaceted perspective on everything from GUI issues and the general user experience, continuing through UI toolkit APIs and theming, down to low-level kernel APIs for device and file system support, and their incumbent issues. Yet I find I’m not the only one walking these moodily lit, disparate corridors. In tracking down assorted breakages and malfunctions in my own software, I have been surprised to repeatedly encounter the same developer footprints spread across many of these areas. It turns out that these developers, and developer teams, have often been directly responsible not only for the breakage I’m investigating, but for issues affecting a large swathe of Linux users and developers.
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help