[-] anzo@programming.dev 2 points 2 months ago

Handbrake software supports many. Perhaps AV1?

[-] anzo@programming.dev 2 points 2 months ago* (last edited 2 months ago)

I don't know which codec should be used to rip but you can pick whatever is in use by the latest and popular uploaders at whichever public tracker you decide on to use for those swarms

[-] anzo@programming.dev 2 points 3 months ago

Endless OS had everything bundled

[-] anzo@programming.dev 2 points 3 months ago

In the past I used it together with KTimeTracker. It's a solution, of the many available... Sadly, none was really optimal IMHO

[-] anzo@programming.dev 2 points 3 months ago

I don't know that software at all, but regarding Linux, we can have anything at any level once you give the admin access, a.k.a. "root" (e.g. binary files that are "attached" to the kernel for a purpose, like making a piece of hardware work.) so... Yes, probably it's on a similarly low level.

[-] anzo@programming.dev 2 points 3 months ago

I'm still struggling to find the info here. I love those comments that clarify click bait or obscure titles so that I don't need to click. Anyway, in this case I just assume it's about Rubik's and I don't care about this. But kudos on building a stopwatch, I guess :P

[-] anzo@programming.dev 2 points 3 months ago

And check their device compatibility list. Also, you'll need plenty of RAM.

[-] anzo@programming.dev 2 points 3 months ago

I am yet to go search about that Quart framework, this is the first time I heard of it. Yet, I am sure this is all about scalability. If you have an app with too many concurrent users, like an e-commerce for a huge brand, then it does make a significant difference to use async. Meanwhile, most projects deal with 20 concurrent users at peak time and see no performance difference, just the cost of having to debug a sophisticated tooling. So, I'd recommend to follow simpler principles. Of course, the curiosity is there and trying out cool new stuff is fun. Oh, one more thing 1 worker can serve N concurrent users easily, it's not 1:1 in practice. Depends on the code and what you're app offers. Say for example you offer generation of PDF report, if you have 100 concurrent users at peak time, but even then only 5 ask for such a report for downloading, you can get away with 2 workers on a VM with just 1 cpu easily.

[-] anzo@programming.dev 2 points 3 months ago

There will be a new sticky soon, for the upcoming week. Allow me to suggest you to ask again there for visibility. Please provide some details, what's broken? E.g. "context menu doesn't open"

[-] anzo@programming.dev 2 points 3 months ago* (last edited 3 months ago)

Install Lineage, Graphite, or some distro from xda-devs. Have fun!

[-] anzo@programming.dev 2 points 3 months ago

Sell the iPhone, get Android. Best lifehack ever.

[-] anzo@programming.dev 2 points 1 year ago

I only discovered local-first recently. Indeed, with only 1 node doing self-hosting of any app there seems to be no difference, but that's a narrow view. The local-first apps are a new concept, using new data structures (e.g. CRDTs), you can read more in a non-technical 'manifesto' here: https://www.inkandswitch.com/local-first/ this is indeed a highly cited article within the movement.

view more: ‹ prev next ›

anzo

joined 1 year ago
MODERATOR OF