[-] MantisWaffle@lemmy.world 1 points 2 months ago

Feel free to elaborate.

[-] MantisWaffle@lemmy.world 2 points 5 months ago

Interesting, that's my experience with anesthesia.

[-] MantisWaffle@lemmy.world 1 points 5 months ago

I thought it was "you're not the boss of me now".

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

https://m.youtube.com/watch?v=HFLW1853Abg&pp=ygUVdGlvbiBlbGVjdHJpYyBjb21wYW55 Show made songs for kids and taught spelling.

There was also a pbskids show with the same name https://www.pbslearningmedia.org/collection/the-electric-company/t/tec-full-episodes/

Which also had a tion song though I can't find the episode right now.

[-] MantisWaffle@lemmy.world 7 points 8 months ago

I disagree, Cargo is very simple and easy to use for developers. I agree, binaries are easier for end users. I'm surprised cargo run --release didn't work for you. What was the project and OS?

[-] MantisWaffle@lemmy.world 1 points 10 months ago* (last edited 10 months ago)

You cant say async is the fundamentally better model because threading is purposely crippled in the browser.

The conversation at hand is not "how do io in browser". Its "async is not inherently better than threads"

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

I assume by performance you mean CPU usage per io request. Each io call should require a switch to the kernel and back. When you do blocking io the switch back is delayed(switch to other threads while waiting), but not more taxing. How could it be possible for there to be a difference?

[-] MantisWaffle@lemmy.world 4 points 10 months ago

Probably not for ddos/security reasons. Would need to use something like nohasher to get noops.

[-] MantisWaffle@lemmy.world 2 points 1 year ago* (last edited 1 year ago)

I've had no problem for years.

Biggest issue I've had was forgetting I committed something on one device before committing on another. Then I had two branches where one had " conflict" in the name. I just deleted all conflict files and everything continued as normal. If your repo is never corrupted before syncing worst case you should be able to find and delete all conflict files.

Syncthing conflicts include the source of the conflict so you could just choose to delete all files whose conflict is from one device and leave everything from the other.

If you're worried you could just ignore your '.git' folder in syncthing since you're purposefully not committing during this. Then sync through git when you finally commit your changes on a device.

[-] MantisWaffle@lemmy.world 3 points 1 year ago

GrapheneOS has had better compatibility with sanboxed google services for a while now. Microg is worse.

[-] MantisWaffle@lemmy.world 3 points 1 year ago* (last edited 1 year ago)

Did you measure that empirically? Gsam indicates it only accounts around 1% of battery drain.

view more: next ›

MantisWaffle

joined 1 year ago