[-] Quackdoc@lemmy.world 1 points 1 day ago

*code blocks are broken and have a fairly degraded UI *accounts and settings are hidden behind a show accounts that's terrible to reach with one hand. *the new sidebar is also terrible to use with one hand *settings is also hidden behind show accounts.

these are the issues I remember off hand, I already deleted the app

[-] Quackdoc@lemmy.world 5 points 2 days ago

Try it at the other day. Not gonna lie, it seems like a total downgrade versus K9. I'll not be upgrading.

[-] Quackdoc@lemmy.world 43 points 3 weeks ago

This would be a great comment if this was America...

14
submitted 1 month ago by Quackdoc@lemmy.world to c/android@lemmy.world

While not seemingly relevant at first glance, turns out they are using Android under the hood Specifically, BlissOS 15 which is Android 12L.

[-] Quackdoc@lemmy.world 15 points 2 months ago* (last edited 2 months ago)

the blog post inside the linked blog post goes over some points. each point is copy and pasted more or less.

  • like for example the multiple times I've spent dozens of hours debugging a single issue only for it to turn out a small typo or a careless mistake that any language would catch at compile time, except for C
  • Memory safety issues arising from the absolute lack of any documentation whatsoever of wlroots have also been quite the annoyance
  • The development of a display server is very complicated, as they are very broad and complex pieces of software. Mixing a C library with 0 documentation is basically asking for trouble.
  • new wayland features that require changes in wlroots tend to take ages to get merged into wlroots, like for example tearing, where a basically ready MR took 9 months to merge
  • explicit sync still not being a thing, despite KDE and Gnome having implementations already (I believe it is now, but not at the time of the blog post)
[-] Quackdoc@lemmy.world 19 points 2 months ago

Why? Hyprland has been limited by wlroots multiple times in the past.

[-] Quackdoc@lemmy.world 35 points 2 months ago* (last edited 2 months ago)

Do we really need to be so constantly cringy about it? Yes, custom ROMs are great. I run one. Lots of other people run one. They're great. Don't get me wrong. But you have to realize most people simply don't care for one, Most vendors also don't really support their phones well under GSI, so things like camera and stuff like that hardly ever work properly.

In a lot of cases, it is quite a bit of work to get a custom rom flashed and have it working well. The technological skill gap between most people who will run an Android phone and even enthusiasts who will so much as think about installing a custom ROM is so massive that you may as well be a hacker to them.

[-] Quackdoc@lemmy.world 16 points 4 months ago

I tried Waydroid and it worked very well. The app ran supersmooth as if it was running natively.

thats because it was running natively

[-] Quackdoc@lemmy.world 28 points 5 months ago

we already have them. It's not hard to make a firearm, and the 3d printed weapons scene has taken off quite well. all of the good ones still need metal parts ofc, but they are pretty easy to get your hands on in many cases.

[-] Quackdoc@lemmy.world 18 points 5 months ago

not enough guns, needs a rifle and a shotgun at least.

[-] Quackdoc@lemmy.world 15 points 6 months ago

I will never not be upset at people who don't realize how ram works

[-] Quackdoc@lemmy.world 22 points 6 months ago* (last edited 6 months ago)

Not sure how long this will last, but here are some videos I took of it, try not to mind the crunch on the last one, I had to use qsv_vp9 for it since I was running out of time and space. Also don't mind the fist video's bad fps, I was compiling in the background and forgot.

Simultaneously installing apps: https://cdn.discordapp.com/attachments/719811866959806514/1217198163149197332/record.mp4?ex=66032720&is=65f0b220&hm=b1e495b579a5313cbaf0f3046ba78479f51dd44fa9f8ecf21929784c27fcbd66&

Phone aspect ratio: https://cdn.discordapp.com/attachments/719811866959806514/1217198532641951856/record.mp4?ex=66032778&is=65f0b278&hm=4c4031dc44a5432570605bfa202720c0613105cd0c8487954d5859e0ec52e3ce&

Plasma mobile on x86 tablet vs gnome software: https://cdn.discordapp.com/attachments/719811866959806514/1217287580916125818/tablet.webm?ex=66037a67&is=65f10567&hm=c4afb4d964b35e04f0a4b12d387a5110403ecf74d267747b5dc2738ff12166bd&

[-] Quackdoc@lemmy.world 17 points 8 months ago

The issue with flat packs is the more you use it, the higher the chance that you get less shared runtimes and the higher the chance of the duplication. And at some points it really does get to awfully ridiculous levels.

A while back, I had run everything I possibly could with Flatpak to the point I'd even make my own Flatpak to try and see how well it would work. Instead of using the AUR. And it worked great for the first little while. I'd installed all of my apps and it was fine, but as I kept using the system, kept installing new apps and not uninstalled the old ones, it really started to build up awfully quick, especially with older apps.

I feel like the usefulness of flatpaks is the inverse parabola, where it's extremely useful in the center use, but when you go to either side of it, it becomes less and less useful.

Apologies for any incoherentcy this was written with a speech 2 text.

view more: next ›

Quackdoc

joined 1 year ago