For an application? Never. I’d still use it for something very small like a build script where the hassle of separate compile and run stages makes the whole thing a hassle to use. That might change now, though, since I think Node has gained the ability to execute Typescript directly.
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.
Typescript and JavaScript are different languages and the distinction is important, especially because the two are used in conjunction with each other.
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.
I think what he means is that AI is needed to keep making substantial improvements in graphic quality, and he phrased it badly. Your interpretation kind of presumes he’s not only lying, but that he thinks we’re all idiots. Given that he’s not running for office as a Republican, I think that’s a very flawed assumption.
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.
I didn’t think you realize just how much code is written in JavaScript these days.
Only long texts?
They had to break at least two at the same time.
And I’ve never shot anyone.
I see you’ve never taken a gun safety class. There are rules you’re supposed to follow to prevent exactly this kind of shit. Responsible gun owners are absolutely anal about following those rules. And they’re really simple rules. Here’s the version from gunpro.com:
The voice chat app?
I think you’re underestimating how resistant to charge old people can be.
I know a colorblind XX person. But he’s a trans man, so make of that what you will.
When you make drug use easier, there is less incentive for that person to want to get clean.
You seem to have some very naive ideas about drug abuse. Drug addicts always have problems that caused them to become drug addicts. For someone without underlying problems, getting clean is its own reward and requires no extra incentives. If you truly care about getting people off drugs, you have to fix the problems that caused them to become addicts in the first place, but that’s difficult and expensive so nobody wants to talk about it.
🤡
Everything in the video is considered acceptable in open source code today. If it wasn’t, it wouldn’t have been right there in the code for the person making the video to find it.
I’m old enough to remember when 4 of those 5 languages were the hot new thing. You’d have had me ignore them all and keep using C for everything. If I had done that I wouldn’t have even landed my first job.
Or against, depending on your cultural values.