111–120 of 159 posts
Earlier quoted context omitted.
> Another reason was Amarok, an (the) mp3 player. It's dead now.
It got revived suddenly, there's going to be a new release soon.
I'm unimpressed.
This is to a bug that, according to their public communications, was fixed years ago. Except of course that it's still present. But other than that, it was fixed years ago.
It’s been a long time since I have used Kate. I see it is stealing design elements from VSCode just like JetBrains UIs decided to. That really disappoints me. I really don’t get the point of doing so. If I wanted to use VSCode, I’d use VSCode rather than the knock off. Why not have a distinct visual identity for crying out loud.
Kate was one of the main reasons I switched to Linux in 2004/2005. I had a lab in MySQL, and back then, the only option to develop in Windows was MySQL Workbench, which was as heavy as it got. Running an SQL statement was painfully slow, and iteration cycles were huge. In Linux, you would write your SQL in Kate, and run MySQL's cli in the embedded terminal. Once ready, you would click the button “pipe to terminal". I…
You forget, on windows, we had WAMP with phpmysql so we could run queries in our browser. Not being able to do them within an IDE until around 2001 with Dreamweaver and Microsoft InterDev… Kate is cool but it wasn’t the first to have this.
Kate was, beside Dolphin one of my earliest and most positively surprising discoveries on KDE. Kate fulfills for me the role that Np++ had back in the windows days. I use it when I want to work file based and not project- or directory based.
It hasn't been updated in a couple years but haven't run into any bugs in a year+ use.
Earlier quoted context omitted.
Amarok is preparing for another release. I wonder if it will come to mac.
Yeah, that's a surprising revival. I thought it died for good this time.
Earlier quoted context omitted.
Ah, this thought stopping argument again. X11 is garbage which nobody wants to maintain, let alone develop. It's a very archaic design which is patched via extensions to sorta support some modern concepts which negate the network transparency anyway. Both Wayland and systemd have a very wide developer consensus, because they finally provide a maintainable solution to their respective problems. The drama is constructe…
Old does not mean bad. Even a decade later Wayland struggles to provide basic features that were built in the X protocol.
Kate was one of the main reasons I switched to Linux in 2004/2005. I had a lab in MySQL, and back then, the only option to develop in Windows was MySQL Workbench, which was as heavy as it got. Running an SQL statement was painfully slow, and iteration cycles were huge. In Linux, you would write your SQL in Kate, and run MySQL's cli in the embedded terminal. Once ready, you would click the button “pipe to terminal". I…
Since I tried it pretty close to its initial release, I'm certain those problems were resolved. However, I developed work habits that didn't include it and so I still don't use it to this day.
Kate was one of the main reasons I switched to Linux in 2004/2005. I had a lab in MySQL, and back then, the only option to develop in Windows was MySQL Workbench, which was as heavy as it got. Running an SQL statement was painfully slow, and iteration cycles were huge. In Linux, you would write your SQL in Kate, and run MySQL's cli in the embedded terminal. Once ready, you would click the button “pipe to terminal". I…
> Another reason was Amarok, an (the) mp3 player. It's dead now.
Kate was one of the main reasons I switched to Linux in 2004/2005. I had a lab in MySQL, and back then, the only option to develop in Windows was MySQL Workbench, which was as heavy as it got. Running an SQL statement was painfully slow, and iteration cycles were huge. In Linux, you would write your SQL in Kate, and run MySQL's cli in the embedded terminal. Once ready, you would click the button “pipe to terminal". I…
Interesting. I think it was a couple of years earlier than that(?) when I tried using Kate, but it was so buggy and crashy as to be unusable. Since I tried it pretty close to its initial release, I'm certain those problems were resolved. However, I developed work habits that didn't include it and so I still don't use it to this day.
Earlier quoted context omitted.
KDE4 is a sad story. It ruined the reputation of KDE for a very long time. I loved KDE 3.5, but then came back to KDE only in 2021. It's mostly just a problem of communication. KDE 4.0 should not have been marked as stable and should not been used by distros. If they baked KDE4 for two more years and on the side maintained/developed 3.5, the transition might be much smoother.
While there were some bugs in early KDE 4, those were not the main problem. No amount of baking could have saved it. The main problem was caused by the completely different purposes of the new developers, who have removed all the outstanding customization features of KDE 3.5. For me, indeed KDE 3.5 has been the best graphic desktop that I have ever seen. Neither before, nor after and neither on Apple or Windows have…
I agree wholeheartedly with this. I miss KDE 3.5.