[-] klangcola@reddthat.com 2 points 1 year ago

I've been running Plasma on my Intel Skylake I5-6?00U with 8gb RAM since 2015 and its utterly fine, no sluggishness in plasma itself. It's still using X11 though, on an old Kubuntu LTS.

Plasma isn't THAT heavy that it should be expected to feel sluggish on that kind of hardware. And contrary to popular belief Plasma isn't actually that heavy of a DE in terms of resources.

OP might need to try different compositor backends? I remember years ago testing each before settling on whatever gave me smoothest performance (maybe OpenGL3?). Actually I'm not sure if this is even a setting anymore in modern Plasma, or in Wayland

[-] klangcola@reddthat.com 2 points 1 year ago

So it's not a showstopper for KDE Wayland default because the fix is outside KDEs control?

It doesn't really matter to end users though. So making the may-suddenly-loose-hours-of-work option the default seems unwise

[-] klangcola@reddthat.com 2 points 1 year ago

Yeah... This one actually is a showstopper. And I thought it was fixed, didn't realize it was fixed for QT apps only

[-] klangcola@reddthat.com 2 points 1 year ago

Thanks for the thorough explanation, Fedora atomic, os-tree and Universal blue is such a new and different way of thinking about the OS compared to the traditional desktop installs. It's also a lot of new jargon so thanks for taking the time to explain each component

[-] klangcola@reddthat.com 2 points 1 year ago

There's also Kate, the KDE Advanced Text Editor. It's available from the Windows store, and works amazingly well on Windows, fast snappy and (almost?) just as featurefull as on Linux. I use it side by side with Notepad++

[-] klangcola@reddthat.com 3 points 1 year ago

Thanks for sharing, Markor looks promising

Markor also has support for Zim Wiki, so I tried it out with some files from my Zim Desktop Wiki notebook, and it sortof works! Markor renders correctly, though I had some problems getting embedded images to work, because Markor didn't find the images using the same relative URLs as Zim Desktop Wiki uses.

[-] klangcola@reddthat.com 2 points 1 year ago

Hmm, yeah there's no mention of cloud sync, and it advertises using "androids native SQLite database" as storage backend, which I imagine means you can't use a third party sync app like FolderSync or Nextcloud app which works with files.

"This project showcases the Good implementation of Android with proper architecture design"

Is hiding away text notes in a database rather than plain text files really what's considered "proper architecture design" these days?

[-] klangcola@reddthat.com 3 points 1 year ago

Cool, Obsidian didn't even cross my mind, thanks for the suggestion.

For mobile, just reading and ticking of existing items covers the main use cases for me. And sometimes adding new items too. That's soo cool that the Sleek Dev added support for arbitrary extensions. I love when FOSS Apps become interoperable on the same dataset like that. Yay for data portability :D

Time to try out Obsidian then

[-] klangcola@reddthat.com 2 points 1 year ago

True, and so all honour to the creators for remaining FOSS, especially smaller projects spearheaded by a single dev

Altough usually when a shift like that happens in bigger projects there's a community fork, and the original project withers. Like Owncloud -> Nextcloud , OpenOffice -> LibreOffice, MySQL -> MariaDB

You could argue there's some degree enshitification through the Ubuntu snapification driven by Canonical. Although that's not so much about making Ubuntu deliberately worse, it's more moving Ubuntu forward in a way that aligns with Canonical's strategic goals. So its "paying the strategy tax" rather than direct enshitification.

For collaborative projects like Linux I believe every contributor would need to agree to any license change, which is practically impossible

[-] klangcola@reddthat.com 2 points 1 year ago
[-] klangcola@reddthat.com 3 points 1 year ago

Thanks for sharing, I have 3 hm90s I'm about to set up ( just waiting for RAM and SSDs ), these crashes sound super frustrating.

I was planning to run them detuned anyway to reduce the strain and temperature on the Power Supply, since its a non-standard USB-C which looks hard or impossible to replace if it breaks some years from now

[-] klangcola@reddthat.com 2 points 1 year ago

You should also know the reason mouth to mouth is "not recommended" is because people get frozen with fear of "doing it wrong" or grossed out by puke/blood and end up doing nothing. So this recommendation is in place to make sure first responders actually do start heart compressions which is the most important if the two. Hoping this is actually explained in the training

Pumping the heart should should still cause some air movement through an unobstructed airway, but not as much as mouth to mouth.

In my country they mentioned the UKs new recommendation, while still recommended mouth-to-mouth. But pumping is priority, do mouth to mouth if you can. And spend as little time as possible on mouth to mouth, get back to pumping asap. Also expect to break ribs when pumping... I really hope I never get to use my COR training

view more: ‹ prev next ›

klangcola

joined 2 years ago