More like a quarter.

People on the other side don’t deserve a mnemonic.

Made me feel like I was crazy the first time I installed pedals on a bike.

My cat used to go in my bathroom and yowl until I went in and got him. Now he has progressed to just yowling in any room with no people in it.

Then use C or C++ if you really need performance.

And that’s where I stopped. I’m a real working programmer who’s done tons of work in C++, so I know firsthand that it absolutely sucks compared to Rust. Go back to Typescript if you hate Rust so much.

Wait until you hear about rent.

Strange, I’ve never found a use for a lightning cable.

Vulture capitalists.

You’ll be sorry when they’re gone!

Ok, but have they fixed the UI scaling on high-DPI displays?

Ok, but have they fixed the UI scaling in high-DPI displays?

But think of the illiterate people! /s

The minimum age anyone can do any of these things:

• Pay taxes
• Hold a job
• Get married
• Sign a contract
• Join the military

I think that’s currently something like 12 in the US, which is a huge problem.

Why are you still using Windows? Switch to Linux!

I think a better solution would be to add a method called something like ulock that does a combined lock and unwrap.

My concern with lock+unwrap is only partly because of convenience; I also didn’t like it because I think it’s a bad idea to get people used to casually calling unwrap, because it tends to hide inadequate error handing.

Now that I think about it, I don’t like how unwrap can signal either “I know this can’t fail”, “the possible error states are too rare to care about” or “I can’t be bothered with real error handing right now”. In one or two of those cases you want to leave it in my production code, and in the last you want to audit all instances and replace them with proper error handing. Using the same function for all three cases makes that difficult.

try_lock already exists; it’s called lock. I just want a more convenient name and I want the name of the new method to be lock, but that ship has sailed.

Looks like the author missed my main complaint about Rust mutexes, which is that the lock method returns a Result. There should be a try_unlock method for when someone actually wants to handle the rather obscure failure case, and the name lock should be used for a method that panics on failure but returns a value that doesn’t need to be unwrapped first. I see the current arrangement as being about as sensible as having array subscripting return a Result to handle the case of a failed bounds check.

The newer version is: https://w3c.github.io/openscreenprotocol/

I used to be on that team at Google and when I left they were working on an open source implementation of it.

Miracast is a separate, older protocol from what Chromecast uses.

Brain-Dead Teen, Only Capable Of Rolling Eyes And Texting, To Be Euthanized