• 30 Posts
  • 867 Comments
Joined 5 months ago
cake
Cake day: January 9th, 2026

help-circle





  • There are multiple different logic how new windows are placed and the existing one re-ordered (or not re-ordered). Some have a logic that make look it random, if you don’t know whats going on. Sometimes these behavior can be configured, or even choose from many “layouts” (these behavior and logic are often called layouts) that suits your needs. I actually use different layouts and switch between them depending on what I need. Below is a bit description of different ways how these layouts could function:

    A predictable layout is the one that cuts the view in half, uses the first window opened up on the left, and then just tiles the right side, while adding new windows on the right bottom side only. This can be configured in a way that every new open window will replace the right big view, and push all other window one below to the left bottom stack in example. Another predictable one is that it cuts the view in 4 parts, left-top to right-bottom. And if all are filled and you open more windows, then the others are cut in half again when needed. Or if you want, use a spiral, that looks random at first and in my opinion was never useful anyway. And there are more ways how a layout logic could function. Not knowing how looks sometimes random.


  • To be clear, I understand the appeal of Fish and its reason to exist. It’s just I convinced myself that the standard shell should be POSIX compatible (had used ZSH for years too, before trying out Fish). And frankly, I am good enough in Bash for daily use and for scripting, that I can use it. Every time I look at Fish (to almost try it again), I’m jelious about some of the syntax and trap cleanups and features. Maybe one day I change my mind. I actually have plans to install Fish again and see how it goes.

    Nushell is really an interesting one. This is how I imagine a modern shell should be like. But the reality is, that all the Linux tools and commandline are not based on this concept. That’s why I never got into. And Xonsh, well I write Python too, and not sure how confusing that would be… I just brought up these shells to make a point about Fish being different and that I categorize it like those.


  • I agree with you that Fish is in language design choices and the default features. There is no denying in that and is the reason why I used Fish as my main interpreter for weeks. But that would not change the fact that I read and write scripts, either for me, to share or to help others, let alone the legacy stuff. Bash is the standard.

    So scripts would stay in Bash for me, and only the interactive interpreter was Fish. And that was a problem for me. Because Fish and Bash are similar, but they are different enough that I got always confused which way was to do and write scripts. Especially because Bash had some quirks (yes its bad, not denying it), and Fish didn’t have them. I thought that I would get used to, but it was always confusing. I rather have a language that is completely different, not similar but different.

    So, if I was using a different language that is no longer compatible with POSIX or Bash, then why would I use Fish instead any other language? Why not Xonsh (Python) or Nushell in example? Because that’s the category I am looking Fish at, not to replace Bash.


  • Its different now, and I mean it. I used Krohnkite in Plasma 5 when it worked well, but later it started to be buggy. Its a fork from the original BTW and the main thing that is worked on at https://codeberg.org/anametologin/Krohnkite . I think reason it was buggy is, caused by Wayland or when transitioning to Plasma 6, forgot. Then I switched to Polonium (kwin script) and it worked but wasn’t great. But Polonium started to be buggy too,… then Krohnkite was reworked, even the Kwin developers made adjustments so that Krohnkite works well.

    I am using it again since Plasma 6 launch period and it works well. Krohnkite is not buggy and it even got some cool features, where you can dock any window to the side or top or bottom side in a smaller area, that will not interfere with the other windows for tiling in example. So all in all, if you think about using it, then I can highly recommend Krohnkite.


  • KDE, but only with an extension called kröhnkite for auto tiling. To me a manual stacked window management system is almost unusable. As someone who used tiling window managers for years and lots of KDE based applications, and as KDE was one of the first who worked well in Wayland, I thought to give it a shot. I like it and since then (years by now) stayed on KDE.

    For reference, I used Gnome 2 on Ubuntu, made the switch to Unity desktop, then Gnome 3 (and I think Gnome 4 too?, don’t remember). Then started experimenting with Regolith, auto tiling for Gnome, and tried out real tiling window managers, until I landed on qtile. Then experimented with Xfce, before finally making the switch to KDE (because of Wayland). Rest is history.






  • Python is designed as an easy language. Yet it is a fundemental important language in the IT, backbone of many Linux operating systems and servers. One could even say… a serious language.

    I personally wouldn’t care if a language is called “easy” or not. You should also look at what it is capable at its peak and where it is used most often, if it works for you. Pick the language that you think fits you the best. I wouldn’t call Zig as an easy language to get into, its still low level language.