I quickly wrote a script that uses kdialog from KDE to input text in a box, then writes both files to a temporary file, compares with diff and outputs the difference in a text box again. At the end it deletes the temporary files (if they are not deleted, they will be removed automatically with next system boot anyway). It's a quick and dirty script.
I am on EndeavourOS since 2 years or so, after I stopped using Manjaro (and then before that I stopped using Ubuntu). I am personally not searching for a distribution right now, it was just a question to see what others would prefer. And I love EndeavourOS so far, its a great distribution.
For Manjaro, it remains to be seen how the restructure will workout. They will become a non profit organization. The previous leadership (phil) was one of the reasons why I stopped using Manjaro a while ago, maybe 2 years by now. Just looked into the link a bit and... it's worse than I thought.
Ubuntu has its own problems, but I think if the core infrastructure and leadership cannot be trusted, then no other decision on the project matters. So my personal vote would go for Ubuntu and against Manjaro, if I were to decide which of them to use.
I don't notice any difference regarding this topic. And I used Kitty and Alacritty before too, for months or years in combined usage. And I am someone who does a lot stuff in terminal, including programming Rust, write lots of scripts and use a terminal filemanager from time to time. Konsole is not noticeably slower than Kitty, it is measurably and marginally slower than Kitty on specific hardware and tasks, but not in my experience. I only speak for myself and my experience.
I used a few terminal apps in the past. My current one is "Konsole" from the KDE project. It is quiet feature rich, has support for tabs and color schemes. It even supports split views, where multiple "terminals" are in one window and stay together. What I also find useful is, it has a right mouseclick menu option to open current directory in my file manager.
But it does not have a builtin functionality to "hide". For KDE there is an extension (called Kwin Scripts) to turn any terminal app you want to into a quake or yakuake like drop down: Quakified Terminal But that is for KDE only off course. Edit: I just learned this Quakified Terminal addon is quite new and got its first release version 4 hours ago as of writing. Lol. That's a coincidence.
Sure (myself neither). I just don't understand why he replies that to me, as if it is an argument to make a point for or against my reply. And seeing that some people downvoted me confuses me even more. I just said I don't understand why he replied to me. Why would anyone downvote without explaining?? What is the reason people got it the wrong way? Really I'm just confused.
I say as long as Ai exist, real programmers will always have a job and are not replaceable. YOLO Vibelords are replaceable, but only real programmers have the skill to go through the shit. That's the most secure job ever if you ask me.
The comparison does not hold up, because for watching films it does not matter on what medium it is. But for applications it has huge implications for maintaining versions, updates, creating packages with or without runtimes and dependencies and a repository and so on, that work differently on operating systems and so on. This goes way beyond just the user choosing the format.
How much is this vibe coded or is the Ai tool Claude just used to assist with code completion and helping in a few topics? Their acknowledgment is as follows and not very clear:
Acknowledgement: AI (mostly Claude) was used in the development of this software. That being said I always test before releasing code.
It is written in Python for Linux and Power Shell for Windows, with almost 3k lines each. I would feel much safe if it used a strongly typed and strict language as Rust, as it would be able to catch some basic errors more easily by design. Which is crucial in context of wiping data, downloading ISOs and installing an operating system. I couldn't trust this project at the moment. But at least it is open source, so that anyone can look into it.
Ah I see, thanks for the link. I don't think the case I talked about is the same case as Rubber duck debugging. It's not to read aloud (maybe in front of another programmer or audience). It's more like, if your students or end user read the documentation and still have some questions left at the end. And ask you the questions about stuff they did not understand.
I would want to avoid
echoand just write to output file directly.